Quick answers
- Is CVE-2026-40149 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-40149 being exploited in the wild.
- How severe is CVE-2026-40149?
- High severity, with a CVSS score of 7.9, published 9 April 2026.
- Which products and versions are affected?
- praisonai (PyPI) ECOSYSTEM:introduced=0,fixed=4.5.128.
- Is there a fix for CVE-2026-40149?
- Yes. praisonai (PyPI): upgrade to 4.5.128 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-40149 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-40149?
- Check whether you run Praisonai or praisonai (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- praisonai (PyPI): upgrade to 4.5.128 or later
pip install "praisonai>=4.5.128"
Technical details
An authentication bypass exists in PraisonAI's gateway component due to the `_check_auth()` function returning `None` when `auth_token` is not configured (the default state). An attacker can send a POST request to the `/api/approval/allow-list` endpoint to add arbitrary tool names, such as `shell_exec` or `file_write`, to the `ExecApprovalManager` allowlist. Because the `register()` function in `exec_approval.py` prioritizes the allowlist as a 'fast path' for auto-approval, subsequent agent requests to use these tools will execute immediately without human review. This vulnerability is primarily exploitable by local attackers or via SSRF/CORS-related attacks. The issue is fixed in version 4.5.128.
Affected products
- MervinPraison PraisonAI < 4.5.128
Identifiers
- CVE-2026-40149
- GHSA-4wr3-f4p3-5wjh
- PYSEC-2026-2901
Timeline
- 2026-04-09: disclosed
- 2026-04-10: advisory
- 2026-04-10: patched: Fixed in version 4.5.128