Quick answers
- Is CVE-2026-57127 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-57127 being exploited in the wild.
- How severe is CVE-2026-57127?
- Critical severity, with a CVSS score of 9.8, published 14 September 2026.
- Which products and versions are affected?
- praisonai (PyPI) ECOSYSTEM:introduced=0,fixed=4.6.59.
- Is there a fix for CVE-2026-57127?
- Yes. praisonai (PyPI): upgrade to 4.6.59 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-57127 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-57127?
- Check whether you run 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.6.59 or later
pip install "praisonai>=4.6.59"
Technical details
The vulnerability is an authentication bypass in PraisonAI's recipe serve component. When an operator selects API-key or JWT authentication, the APIKeyAuthMiddleware or JWTAuthMiddleware is installed but contains a logic flaw: it forwards requests when the corresponding environment variables (PRAISONAI_API_KEY or PRAISONAI_JWT_SECRET) or recipe configuration values are absent, rather than rejecting them. This allows unauthenticated clients to reach protected recipe execution, input, and output endpoints and trigger connected tools. The attack requires network access to the recipe serve endpoint but no authentication credentials. The vulnerability was fixed in version 4.6.58 with hardened input validation and improved middleware logic.
Affected products
- PraisonAI PraisonAI before 4.6.58
Identifiers
- CVE-2026-57127
- GHSA-j4hj-7hfh-g2f4
- PYSEC-2026-3513
Timeline
- 2026-09-14: disclosed
- 2026-06-13: patched: Version 4.6.58 released with fix