# CVE-2026-40150: PraisonAIAgents has SSRF and Local File Read via Unvalidated URLs in web_crawl Tool

> Attackers can force the AI agent to fetch internal resources or local files via unvalidated URLs in the web_crawl tool, leading to data exposure.

- **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:** 9 Apr 2026
- **Updated:** 14 Apr 2026
- **Also known as:** GHSA-8f4v-xfm9-3244, PYSEC-2026-2945

## What is CVE-2026-40150?

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

### Official description

PraisonAIAgents is a multi-agent teams system. Prior to 1.5.128, the web_crawl() function in praisonaiagents/tools/web_crawl_tools.py accepts arbitrary URLs from AI agents with zero validation. No scheme allowlisting, hostname/IP blocklisting, or private network checks are applied before fetching. This allows an attacker (or prompt injection in crawled content) to force the agent to fetch cloud metadata endpoints, internal services, or local files via file:// URLs. This vulnerability is fixed in 1.5.128.

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

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `praisonaiagents` | PyPI | All versions | 1.5.128 |
| `praisonaiagents` | PyPI | All versions | 1.5.128 |
| `praisonaiagents` | PyPI | All versions | 1.5.128 |

Products: Praison Praisonaiagents.

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

Upgrade praisonaiagents to 1.5.128 or later.

## Is CVE-2026-40150 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-40150 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-40150 and fix it if it is affected.

What it is: CVE-2026-40150 is a high-severity server-side request forgery vulnerability in MervinPraison PraisonAIAgents, published on 9 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-40150 exists.

Affected packages and fixed versions:
- praisonaiagents (PyPI): affected all versions; fixed in 1.5.128
- praisonaiagents (PyPI): affected all versions; fixed in 1.5.128
- praisonaiagents (PyPI): affected all versions; 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-40150/ (Markdown: https://insights.sbomify.com/CVE-2026-40150/index.md)
```

## Sources

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

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