CVE-2026-34936
Server-Side Request Forgery in PraisonAI passthrough Functions
Publication date: 2026-04-03
Last updated on: 2026-04-14
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| praison | praisonai | to 4.5.90 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-918 | The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The vulnerability exists in PraisonAI versions prior to 4.5.90, specifically in the passthrough() and apassthrough() functions. These functions accept a caller-controlled api_base parameter, which is concatenated with an endpoint and passed directly to httpx.Client.request() when a certain error occurs. There is no validation of the URL scheme, no filtering of private IP addresses, and no domain allowlist applied. This means an attacker can make requests to any host reachable from the server, potentially abusing the system to access unauthorized network resources.
How can this vulnerability impact me? :
This vulnerability can allow an attacker with limited privileges to make arbitrary HTTP requests from the server to any reachable host. Because there is no restriction on the destination, it could be used to access internal or private network resources that are normally inaccessible, potentially leading to information disclosure or unauthorized network interactions. The CVSS score of 7.7 indicates a high severity impact on confidentiality.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability has been patched in PraisonAI version 4.5.90. The immediate step to mitigate this vulnerability is to upgrade PraisonAI to version 4.5.90 or later.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows an attacker to make arbitrary HTTP requests from the server to any host reachable from it, due to lack of URL scheme validation, private IP filtering, or domain allowlisting.
This could potentially lead to unauthorized data access or data exfiltration, which may impact compliance with standards and regulations such as GDPR or HIPAA that require protection of sensitive data and prevention of unauthorized access.
However, the provided information does not explicitly describe the direct impact on compliance with these standards.