# CVE-2026-55523: PraisonAI has a`web_crawl` SSRF protection bypass via unchecked redirect targets

> Attackers can bypass SSRF protections in PraisonAI by using redirects to access internal network resources or cloud metadata endpoints.

- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Aug 2026
- **Updated:** 6 Aug 2026
- **Also known as:** GHSA-8hjw-25cg-g52h, PYSEC-2026-3900

## What is CVE-2026-55523?

CVE-2026-55523 is a high-severity server-side request forgery vulnerability in MervinPraison PraisonAI, published on 5 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PraisonAI is a multi-agent teams system. In versions 1.5.128 through 1.6.57, the praisonaiagents.tools.web_crawl_tools.web_crawl() function is vulnerable to server-side request forgery. While it validates the initially supplied URL and blocks direct loopback and private destinations, its default httpx fallback uses httpx.Client(follow_redirects=True) and does not revalidate intermediate or final redirect targets. An attacker who can influence a URL passed to web_crawl(), directly or through an agent or tool workflow, can supply an attacker-controlled public URL that passes the initial host check and then redirects to loopback, private-network, or cloud metadata endpoints reachable from the host, with the redirected response body returned in the web_crawl() result. This constitutes an incomplete fix and patch bypass for the previously disclosed web_crawl SSRF class (GHSA-qq9r-63f6-v542 / CVE-2026-40160 and GHSA-8f4v-xfm9-3244), since the guard validates only the requested URL and not the destination actually fetched after redirection. This issue has been fixed in version 1.6.58.

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

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

3 open source packages ship an affected version, including praisonaiagents.


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

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

Upgrade praisonaiagents to 1.6.58 or later.

## Is CVE-2026-55523 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-55523 is a high-severity server-side request forgery vulnerability in MervinPraison PraisonAI, published on 5 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55523 exists.

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

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

## Sources

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

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