# CVE-2026-61427: PraisonAI before 4.6.78 Authentication Bypass via HTTP-stream

> Unauthenticated attackers can access MCP tools and execute arbitrary code if the server is bound to a network interface without an API key.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/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:** 15 Jul 2026
- **Updated:** 16 Jul 2026
- **Also known as:** CVE-2026-62178, GHSA-hc5v-gxvj-58wh, PYSEC-2026-4257

## What is CVE-2026-61427?

CVE-2026-61427 is a medium-severity authentication bypass vulnerability in MervinPraison PraisonAI, published on 15 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PraisonAI before 4.6.78 exposes the MCP HTTP-stream transport without authentication by default: the CLI --api-key option defaults to None, and the server only enforces Authorization/Bearer checks when an API key is configured. When an operator runs 'praisonai mcp serve --transport http-stream' without an API key, an unauthenticated client (no Authorization header, and no Origin header, which is also permitted) can initialize a session, enumerate the available tools (tools/list), and invoke tools (tools/call). Additionally, the dispatcher forwards tool-call arguments to handlers without validating them against the advertised inputSchema. The server binds to 127.0.0.1 by default, so remote exploitation requires the operator to bind to a network-accessible address (e.g., --host 0.0.0.0).

Weakness: CWE-20 (Improper Input Validation)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `praisonai` | PyPI | All versions | 4.6.78 |
| `praisonai` | PyPI | All versions | 4.6.78 |
| `praisonai` | PyPI | All versions | 4.6.78 |

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

Upgrade praisonai to 4.6.78 or later.

## Is CVE-2026-61427 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-61427 is a medium-severity authentication bypass vulnerability in MervinPraison PraisonAI, published on 15 Jul 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-61427 exists.

Affected packages and fixed versions:
- praisonai (PyPI): affected all versions; fixed in 4.6.78
- praisonai (PyPI): affected all versions; fixed in 4.6.78
- praisonai (PyPI): affected all versions; fixed in 4.6.78

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

## Sources

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

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