# CVE-2026-40160: PraisonAIAgents has SSRF via unvalidated URL in `web_crawl` httpx fallback

> Attackers can force AI agents to crawl internal URLs, exposing cloud metadata and internal services via unvalidated httpx requests.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:N/VA:N/SC:H/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 10 Apr 2026
- **Updated:** 13 Apr 2026
- **Also known as:** GHSA-qq9r-63f6-v542, PYSEC-2026-2951

## What is CVE-2026-40160?

CVE-2026-40160 is a high-severity server-side request forgery vulnerability in MervinPraison PraisonAIAgents, published on 10 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

PraisonAIAgents is a multi-agent teams system. Prior to 1.5.128, web_crawl's httpx fallback path passes user-supplied URLs directly to httpx.AsyncClient.get() with follow_redirects=True and no host validation. An LLM agent tricked into crawling an internal URL can reach cloud metadata endpoints (169.254.169.254), internal services, and localhost. The response content is returned to the agent and may appear in output visible to the attacker. This fallback is the default crawl path on a fresh PraisonAI installation (no Tavily key, no Crawl4AI installed). This vulnerability is fixed in 1.5.128.

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

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `praisonaiagents` | PyPI | From 0.13.23 | 1.5.128 |
| `praisonaiagents` | PyPI | From 0.13.23 | 1.5.128 |
| `praisonaiagents` | PyPI | From 0.13.23 | 1.5.128 |

Products: Praison Praisonaiagents.

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

Upgrade praisonaiagents to 1.5.128 or later.

## Is CVE-2026-40160 being exploited?

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

## Other vulnerabilities in MervinPraison PraisonAIAgents

- [CVE-2026-34938](https://insights.sbomify.com/CVE-2026-34938/): PraisonAI: Python Sandbox Escape via str Subclass startswith() Override in execute_code (critical 10.0)
- [CVE-2026-40111](https://insights.sbomify.com/CVE-2026-40111/): PraisonAIAgents has an OS Command Injection via shell=True in Memory Hooks Executor (memory/hooks.py) (critical 9.3)
- [CVE-2026-34954](https://insights.sbomify.com/CVE-2026-34954/): PraisonAI: SSRF in FileTools.download_file() via Unvalidated URL (high 8.6)
- [CVE-2026-34937](https://insights.sbomify.com/CVE-2026-34937/): PraisonAI: Shell Injection in run_python() via Unescaped $() Substitution (high 7.8)
- [CVE-2026-44335](https://insights.sbomify.com/CVE-2026-44335/): SSRF bypass in PraisonAI (high 7.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-40160 is a high-severity server-side request forgery vulnerability in MervinPraison PraisonAIAgents, published on 10 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-40160 exists.

Affected packages and fixed versions:
- praisonaiagents (PyPI): affected from 0.13.23; fixed in 1.5.128
- praisonaiagents (PyPI): affected from 0.13.23; fixed in 1.5.128
- praisonaiagents (PyPI): affected from 0.13.23; fixed in 1.5.128

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-40160/ (Markdown: https://insights.sbomify.com/CVE-2026-40160/index.md)
```

## Sources

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

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