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).
CVE-2026-61427
Score 7.3 from GitHub Security Advisory published 2026-07-15. a secondary CVSS source baseline 7.3; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.3
- EG Score
- 7.3(high)
- EPSS
- —
- KEV
- Not listed
Published
July 15, 2026
Last Modified
July 15, 2026
Advisory Details (2)
Auto-updated Jul 15, 2026PraisonAI before 4.6.78 Authentication Bypass via HTTP-stream | Advisories | VulnCheck
https://www.vulncheck.com/advisories/praisonai-before-authentication-bypass-via-http-streamMCP HTTP-stream transport is unauthenticated by default, exposing tool enumeration and an unvalidated tool-call surface · Advisory · MervinPraison/PraisonAI · GitHub
https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-hc5v-gxvj-58whVendor Advisories for CVE-2026-61427(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 4× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-15 23:09 UTCEG score recompute
- 2026-07-15 23:09 UTCGHSA enrichment
- 2026-07-15 11:55 UTCEG score recompute
- 2026-07-15 11:54 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-20
- CVE-2002-2444EG 9.8CRITICAL
- CVE-2005-0116NVD 0.0EG 9.0EPSS 99%NONE
- CVE-2002-1359NVD 0.0EG 9.0EPSS 100%NONE
- CVE-2000-0380NVD 0.0EG 9.0EPSS 98%NONE
- CVE-2000-0258EG 7.5EPSS 97%HIGH
- CVE-2004-2771EG 0.0EPSS 93%NONE
- CVE-2002-2443EG 0.0EPSS 93%NONE
- CVE-2002-2433EG 0.0NONE
- CVE-2003-1569EG 0.0NONE
- CVE-2003-1568EG 0.0NONE
Frequently asked(4)
What is CVE-2026-61427?
When was CVE-2026-61427 disclosed?
What is the CVSS score of CVE-2026-61427?
How do I remediate CVE-2026-61427?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-61427
Is Your Infrastructure Affected by CVE-2026-61427?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.