PraisonAI Has Authentication Bypass via OAuthManager.validate_token()

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

9.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

EPSS

• CVE-2026-34953: 0.39% estimated exploitation activity in the next 30 days; percentile 33.19 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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 Impact Any unauthenticated attacker with network access to the MCP HTTP server can call all registered tools including agent execution, workflow runs, container file read/write, and skill loading. The server binds to 0.0.0.0 by default with no API key required. Suggested Fix

Published by the source

1 Apr 2026, 23:29 UTC

Last modified by the source

29 Jun 2026, 12:26 UTC

Source last checked

26 Oct 2026, 13:40 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-98f9-fqg5-hvq5

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GHSA-98f9-fqg5-hvq5

3. Revision 1 · created · 23 Oct 2026

   Published from ghsa record GHSA-98f9-fqg5-hvq5

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-34953

Advisory: PraisonAI Has Authentication Bypass via OAuthManager.validate_token()
IDs: CVE-2026-34953, GHSA-98f9-fqg5-hvq5
Record: https://patchnext.com/advisories/cve-2026-34953 (revision 3, source checked 26 Oct 2026, 13:40 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: praisonai 4.5.97. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI praisonai: affected <= 4.5.96; fixed in 4.5.97

## Suggested inspection (read-only)
- `python -m pip show praisonai`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on praisonai.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-98f9-fqg5-hvq5 (GitHub-reviewed advisory GHSA-98f9-fqg5-hvq5 lists affected ranges: PyPI praisonai >=0 <=4.5.96)
- Verified: https://osv.dev/vulnerability/GHSA-98f9-fqg5-hvq5 (OSV record GHSA-98f9-fqg5-hvq5 lists affected ranges: PyPI praisonai >=0 <4.5.97 (fixed))

Commands are suggestions: review each one before running it.