How severe is GHSA-98f9-fqg5-hvq5?

GHSA-98f9-fqg5-hvq5 has a CVSS score of 9.1/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-98f9-fqg5-hvq5?

GHSA-98f9-fqg5-hvq5 affects the following packages: praisonai (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-98f9-fqg5-hvq5?

Update praisonai to 4.5.97 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-98f9-fqg5-hvq5 is resolved across your whole dependency graph.

How do I detect GHSA-98f9-fqg5-hvq5 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for praisonai. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-98f9-fqg5-hvq5 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-98f9-fqg5-hvq5?

O3 pinpoints whether GHSA-98f9-fqg5-hvq5 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-98f9-fqg5-hvq5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-98f9-fqg5-hvq5 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-98f9-fqg5-hvq5?

GHSA-98f9-fqg5-hvq5 is classified as CWE-863 (CWE-863). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-98f9-fqg5-hvq5 published, and has it been updated?

GHSA-98f9-fqg5-hvq5 was published on April 1, 2026 and was last updated on June 29, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

GHSA-98f9-fqg5-hvq5

CRITICAL

GHSA-98f9-fqg5-hvq5 is a critical-severity (CVSS 9.1) CWE-863 vulnerability in praisonai. O3 Security confirms whether GHSA-98f9-fqg5-hvq5 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

PraisonAI Has Authentication Bypass via OAuthManager.validate_token()

Also known asCVE-2026-34953PYSEC-2026-468

Published

Apr 1, 2026

Updated

Jun 29, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Real-World Exposure

1 pkg affected

🐍praisonai

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Summary

OAuthManager.validate_token() 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)

# source
def validate_token(self, token: str) -> bool:
    for stored_token in self._tokens.values():
        if stored_token.access_token == token:
            return not stored_token.is_expired()

# sink -- _tokens is empty by default, loop never executes, falls through
    return True

PoC

# install: pip install -e src/praisonai
# start server: praisonai mcp serve --transport http-stream --port 8080

curl -s -X POST http://127.0.0.1:8080/mcp \
  -H "Authorization: Bearer fake_token_abc123" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"tools/list","id":1}'

# expected output: 200 OK with full tool list (50+ tools)
# including praisonai.agent.run, praisonai.workflow.run, praisonai.containers.file_write

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

def validate_token(self, token: str) -> bool:
    for stored_token in self._tokens.values():
        if stored_token.access_token == token:
            return not stored_token.is_expired()
    # Unknown tokens must be rejected.
    # For external/JWT tokens, call the introspection endpoint here before returning.
    return False

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`praisonai`	all versions	4.5.97

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for praisonai. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update praisonai to 4.5.97 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-98f9-fqg5-hvq5 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-98f9-fqg5-hvq5 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-98f9-fqg5-hvq5. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary `OAuthManager.validate_token()` 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) ```python # source def validate_token(self, token: str) -> bool: for stored_token in self._tokens.values(): if stored_token.access_token == token: return not stored_token.is_expired()

O3 Security · Impact-Aware SCA

Is GHSA-98f9-fqg5-hvq5 in your dependencies?

O3 detects GHSA-98f9-fqg5-hvq5 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works