Security Digest · Vulnerability record

CVE-2026-34953: PraisonAI Has Authentication Bypass via OAuthManager.validate_token()

PraisonAI is a multi-agent teams system. Prior to version 4.5.97, OAuthManager.validatetoken() returns True for any token not found in its internal store, which is empty by default.

CVSS 9.1 Critical EPSS 0.4% · p35

Should you act?

Critical and remotely reachable

No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

  • Not in CISA KEV, but CISA’s SSVC assessment records a public proof-of-concept, so attack code exists.
  • EPSS 0.4%, percentile 35: FIRST’s model estimates a 0.4% chance of exploitation activity in the next 30 days, higher than 35% of all scored CVEs (low). EPSS is a probability, not a verdict.
  • Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
  • Only applies if your dependency tree includes praisonai (PyPI) <= 4.5.96, fixed in 4.5.97. Check your lockfile, including transitive dependencies.

What it is

PraisonAI is a multi-agent teams system. Prior to version 4.5.97, OAuthManager.validatetoken() returns True for any token not found in its internal store, which is empty by default. Any HTTP request to the MCP server with an arbitrary Bearer token is treated as authenticated, granting full access to all registered tools and agent capabilities. This issue has been patched in version 4.5.97.

From the GitHub advisory

Summary

OAuthManager.validatetoken() returns True for any token not found in its internal store, which is empty by default. Any HTTP request to the MCP server with an arbitrary Bearer token is treated as authenticated, granting full access to all registered tools and agent capabilities.

Details

oauth.py:364 (source) -> oauth.py:374 (loop miss) -> oauth.py:381 (sink)

PoC

Weakness type: CWE-863.

Product: praisonai (PyPI) · Assigned by: GitHub_M · Published: 2026-04-03

Affected and fixed versions

EcosystemPackageVulnerableFirst fixed
PyPIpraisonai<= 4.5.964.5.97
VendorProductAffected versions (per CVE record)
MervinPraisonPraisonAI< 4.5.97

Severity scores

Scored byCVSSScoreVector
GitHub_M3.19.1 CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
GitHub3.19.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
  • Attack vector: network (remotely reachable)
  • Attack complexity: low
  • Privileges required: none (no login)
  • User interaction: none
  • Scope: unchanged

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

  • CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
  • CISA SSVC assessment: exploitation poc, automatable yes, technical impact partial.
  • FIRST EPSS (model of 2026-10-21): 0.42% probability of exploitation activity in the next 30 days; percentile 35.

Timeline

  • — GitHub-reviewed advisory GHSA-98f9-fqg5-hvq5 published (critical)
  • — CVE record published by GitHub_M
  • — CVE record last updated

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vulnerability records

  1. GitHub Advisory GHSA-98f9-fqg5-hvq5 github.com
  2. CVE.org record CVE-2026-34953 cve.org
  3. NVD entry CVE-2026-34953 nvd.nist.gov

Other references from the CVE record and advisory

  1. github.com github.com

Critical PyPI advisories · Today’s Security Digest