# CVE-2026-34936: PraisonAI: SSRF via Unvalidated api_base in passthrough() Fallback

> Attackers can exploit unvalidated API base URLs in PraisonAI to perform Server-Side Request Forgery, accessing internal network resources.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Apr 2026
- **Updated:** 6 Apr 2026
- **Also known as:** GHSA-x6m9-gxvr-7jpv, PYSEC-2026-2924

## What is CVE-2026-34936?

CVE-2026-34936 is a high-severity server-side request forgery vulnerability in MervinPraison PraisonAI, published on 3 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

PraisonAI is a multi-agent teams system. Prior to version 4.5.90, 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. This issue has been patched in version 4.5.90.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-34936?

3 open source packages ship an affected version, including praisonai. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `praisonai` | PyPI | All versions | 4.5.90 |
| `praisonai` | PyPI | All versions | 4.5.90 |
| `praisonai` | PyPI | All versions | 4.5.90 |

Products: Praison Praisonai.

## How do I fix CVE-2026-34936?

Upgrade praisonai to 4.5.90 or later.

## Is CVE-2026-34936 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34936 exists.

## Other vulnerabilities in MervinPraison PraisonAI

- [CVE-2026-39888](https://insights.sbomify.com/CVE-2026-39888/): PraisonAIAgents has a sandbox escape via exception frame traversal in `execute_code` (subprocess mode) (critical 10.0)
- [CVE-2026-41497](https://insights.sbomify.com/CVE-2026-41497/): Incomplete fix for CVE-2026-34935: Command Injection in MervinPraison/PraisonAI (critical 9.8)
- [CVE-2026-40288](https://insights.sbomify.com/CVE-2026-40288/): PraisonAI: Critical RCE via `type: job` workflow YAML (critical 9.8)
- [CVE-2026-39890](https://insights.sbomify.com/CVE-2026-39890/): PraisonAI Affected by Remote Code Execution via YAML Deserialization in Agent Definition Loading (critical 9.8)
- [CVE-2026-34934](https://insights.sbomify.com/CVE-2026-34934/): PraisonAI: Second-Order SQL Injection in `get_all_user_threads` (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-34936 and fix it if it is affected.

What it is: CVE-2026-34936 is a high-severity server-side request forgery vulnerability in MervinPraison PraisonAI, published on 3 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34936 exists.

Affected packages and fixed versions:
- praisonai (PyPI): affected all versions; fixed in 4.5.90
- praisonai (PyPI): affected all versions; fixed in 4.5.90
- praisonai (PyPI): affected all versions; fixed in 4.5.90

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-34936/ (Markdown: https://insights.sbomify.com/CVE-2026-34936/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-34936
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-34936
- OSV: https://osv.dev/vulnerability/CVE-2026-34936

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-34936/
Summaries are generated and may contain mistakes; the official description above is the record.