# CVE-2026-55524: PraisonAI: SSRF in web_crawl tool via redirect-following and DNS rebinding (validate-then-fetch gap)

> Attackers can bypass SSRF protections in PraisonAI's web_crawl tool to access internal network resources or cloud metadata via redirects or DNS rebinding.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:L/A: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-vg6p-v9vm-6fgj, PYSEC-2026-3904

## What is CVE-2026-55524?

CVE-2026-55524 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 prior to 1.6.58, the web_crawl tool performs its SSRF check only on the initially supplied URL, allowing the protection to be bypassed so the tool connects to attacker-chosen internal destinations. The check resolves the hostname once with socket.gethostbyname and rejects private/loopback/link-local results, but then passes the URL to a fetcher using httpx.Client(follow_redirects=True) (or urllib.request.urlopen when httpx is absent, which also follows redirects) that re-resolves the hostname at connect time with no further validation. This validate-here/fetch-there gap is exploitable through both HTTP redirects and DNS rebinding. If an attacker can influence URLs passed to web_crawl(), directly or through an agent/tool workflow, they can cause the PraisonAI host to fetch loopback, private-network, or cloud metadata endpoints reachable from that host, with the response body returned in the web_crawl() result. This issue has been fixed in version 1.6.58.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

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

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


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

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

Upgrade praisonaiagents to 1.6.58 or later.

## Is CVE-2026-55524 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-55524 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-55524 exists.

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

## Sources

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

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