Quick answers
- Is CVE-2026-57124 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-57124 being exploited in the wild.
- How severe is CVE-2026-57124?
- 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-57124?
- 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-57124 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-57124?
- 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
PraisonAI's UI host exposes a POST /api/mcp/connect endpoint without mandatory authentication. The endpoint accepts caller-controlled command and args parameters that are directly passed to StdioMCPClient to spawn local processes. Because the UI service binds to 0.0.0.0 by default, an unauthenticated remote attacker can reach this endpoint over the network and execute arbitrary commands as the service account, even if the subsequent MCP handshake fails. The vulnerability is due to missing input validation and access controls on the endpoint. A fix was released in version 4.6.59 that hardens input validation and enforces access controls.
Affected products
- Mervin Praison PraisonAI prior to 4.6.59
Identifiers
- CVE-2026-57124
- GHSA-p75f-6fp4-p57w
- PYSEC-2026-3517
Timeline
- 2026-09-14: disclosed: CVE-2026-57124 published on NVD
- 2026-06-13: patched: Fix committed (version 4.6.59 released 2026-06-17)