Skip to main content
VulnerabilityPublished Updated

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

Affects praisonaiSource GCVE Database

0
Compare
Authoritative record:CVE-2026-34953· Critical 9.1

Not known to be exploited · CVSS 9.1 Critical : upgrade to 4.5.97 as a priority.

Data as of 16 Nov 2026, 16:37 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 4.5.97
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Upgrade praisonai to 4.5.97.

Affected software

ProductAffectedFixed in
PyPIpraisonaiAffected
  • <4.5.97
Fixed in
  • 4.5.97

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in PraisonAI version 4.5.97 that fixes the authentication bypass by rejecting unknown tokens in the validate_token() method. Users should upgrade to version 4.5.97 or later. Until patched, no reliable workaround is described. The vendor's suggested fix changes the method to return false for tokens not found in the internal store, preventing unauthorized access.

Description

PraisonAI versions prior to 4.5.97 contain an authentication bypass vulnerability in the OAuthManager.validate_token() method. The method incorrectly returns true for any token not found in its internal token store, which is empty by default. This allows any HTTP request with an arbitrary Bearer token to be treated as authenticated, granting full access to all registered tools and agent capabilities. The server binds to all interfaces (0.0.0.0) by default and requires no API key, increasing exposure risk.

References

Community reviews

Loading reviews…