# CVE-2026-57112: PraisonAI ToolsMCPServer legacy SSE transport accepts attacker Host/Origin and exposes registered tools

> Attackers can bypass authentication on legacy SSE endpoints to enumerate and invoke AI tools with server privileges via DNS rebinding.

- **Severity:** High 8.3 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H`)
- **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:** 15 Sep 2026
- **Updated:** 16 Sep 2026
- **Also known as:** GHSA-vmf9-xx9w-86wx, PYSEC-2026-3521, PYSEC-2026-3534

## What is CVE-2026-57112?

CVE-2026-57112 is a high-severity missing authorization vulnerability in MervinPraison PraisonAI, published on 15 Sep 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

PraisonAI is a multi-agent teams system. From praisonaiagents 0.6.0 until 1.6.59 and PraisonAI 3.10.0 until 4.6.59, ToolsMCPServer.run_sse() in src/praisonai-agents/praisonaiagents/mcp/mcp_server.py mounts SseServerTransport on the legacy /sse and /messages/ endpoints without default Host, Origin, or authentication enforcement. A malicious website can use DNS rebinding against a reachable local or internal SSE server, supply attacker-controlled Host and Origin headers, enumerate registered tools, and invoke them with the server user's privileges. The Streamable HTTP transport rejects the same hostile Origin, which isolates the flaw to the legacy SSE wrapper. An initial remediation was released in praisonaiagents 1.6.59 and PraisonAI 4.6.59.

Weakness: CWE-862 (Missing Authorization), CWE-346 (Origin Validation Error), CWE-306 (Missing Authentication for Critical Functionality)

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

6 open source packages ship an affected version, including praisonai and praisonaiagents.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `praisonai` | PyPI | From 3.10.0 | 4.6.59 |
| `praisonai` | PyPI | From 3.10.0 | 4.6.59 |
| `praisonai` | PyPI | From 3.10.0 | 4.6.59 |
| `praisonaiagents` | PyPI | From 0.6.0 | 1.6.59 |
| `praisonaiagents` | PyPI | From 0.6.0 | 1.6.59 |
| `praisonaiagents` | PyPI | From 0.6.0 | 1.6.59 |

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

Upgrade praisonai to 4.6.59 or later.

## Is CVE-2026-57112 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-57112 is a high-severity missing authorization vulnerability in MervinPraison PraisonAI, published on 15 Sep 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-57112 exists.

Affected packages and fixed versions:
- praisonai (PyPI): affected from 3.10.0; fixed in 4.6.59
- praisonai (PyPI): affected from 3.10.0; fixed in 4.6.59
- praisonai (PyPI): affected from 3.10.0; fixed in 4.6.59
- praisonaiagents (PyPI): affected from 0.6.0; fixed in 1.6.59
- praisonaiagents (PyPI): affected from 0.6.0; fixed in 1.6.59
- praisonaiagents (PyPI): affected from 0.6.0; fixed in 1.6.59

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

## Sources

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

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