Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
CriticalPublic exploit

Authentication bypass in PraisonAI MCP server token validation

IdentifiersCVE-2026-34953CWE-863· Incorrect Authorization

CVE-2026-34953 affects PraisonAI, a multi-agent teams system, in versions prior to 4.5.97. The flaw is in OAuthManager.validate_token(), which returns True for tokens not found in its internal token store. Because that store is empty by default, arbitrary Bearer tokens supplied in HTTP requests to the MCP server are accepted as authenticated. This results in an authentication bypass on the MCP server, allowing unauthorized access to all registered tools and agent capabilities exposed through the service.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

A remote, unauthenticated attacker can send an HTTP request to the PraisonAI MCP server with any arbitrary Bearer token and be treated as an authenticated user. Successful exploitation grants full access to registered tools and agent capabilities, resulting in high confidentiality and integrity impact. The provided context does not indicate direct availability impact.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible, restrict network access to the MCP server to trusted clients only, place the service behind a compensating authentication control such as a reverse proxy or API gateway enforcing independent authentication, and monitor for requests using unexpected or arbitrary Bearer tokens. Because the vulnerable logic accepts invalid tokens by design, mitigation should focus on preventing untrusted access until the patched version can be deployed.

Remediation

Patch, then assume compromise.

Upgrade PraisonAI to version 4.5.97 or later, which patches the token validation logic in OAuthManager.validate_token() and prevents arbitrary Bearer tokens from being accepted as authenticated.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
PraisonPraisonaiapplication
PraisonAIPraisonaiapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity7

Community discussion across Reddit, Mastodon, and other social sources.