Unauthenticated tool access via fail-open token validation
Published Apr 3, 2026 · Updated Apr 3, 2026
Authentication bypass in PraisonAI before 4.5.97 allows remote attackers to access MCP tools with an arbitrary Bearer token. OAuthManager.validate_token() iterates the internal token store but returns True after the loop, so an unknown token is accepted when no match exists. Network access to the HTTP MCP server is sufficient, and the store is empty by default; accepted requests can list and invoke registered tools and agent capabilities.
Summary
What happened
Authentication bypass in PraisonAI before 4.5.97 allows remote attackers to access MCP tools with an arbitrary Bearer token. OAuthManager.validate_token() iterates the internal token store but returns True after the loop, so an unknown token is accepted when no match exists. Network access to the HTTP MCP server is sufficient, and the store is empty by default; accepted requests can list and invoke registered tools and agent capabilities.
The record
- CVE
- CVE-2026-34953
- Published
- Apr 3, 2026
- Updated
- Apr 3, 2026
- Vendor
- Mervin Praison
- Product
- PraisonAI
- Classifications
- CWE-863, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 3, 2026CVE publishedPublication date reported by the CVE source.
- Apr 3, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 4.5.97
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- GHSA MCP tools/list proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo