# CVE-2026-55526: PraisonAI: SSRF protection bypass in `spider_tools._host_is_blocked()` via DNS-resolved hostnames (`127.0.0.1.nip.io`)


- **Severity:** High 8.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 25 Aug 2026
- **Updated:** 25 Aug 2026
- **Also known as:** GHSA-x44h-65qv-cw74, PYSEC-2026-3905

## What is CVE-2026-55526?

CVE-2026-55526 is a high-severity vulnerability in MervinPraison PraisonAI, published on 25 Aug 2026. 

### Official description

PraisonAI is a multi-agent teams system. Prior to praisonaiagents 1.6.58, spider_tools._host_is_blocked() does not resolve ordinary hostnames before scrape_page fetches them. A hostname such as 127.0.0.1.nip.io passes validation and resolves to loopback, permitting internal HTTP access. The fix uses socket.getaddrinfo and fails closed on DNS errors. This issue is fixed in version 1.6.58.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-350 (Reliance on Reverse DNS Resolution for a Security-Critical Action)

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

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-55526?

Upgrade praisonaiagents to 1.6.58 or later.

## Is CVE-2026-55526 being exploited?

There is no known exploitation of CVE-2026-55526 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-55526 is a high-severity vulnerability in MervinPraison PraisonAI, published on 25 Aug 2026. 
Exploitation: There is no known exploitation of CVE-2026-55526 in the wild and no public exploit code.

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

## Sources

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

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