Quick answers
- Is CVE-2026-62176 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-62176 being exploited in the wild.
- How severe is CVE-2026-62176?
- Critical severity, with a CVSS score of 9.1, published 7 October 2026.
- Which products and versions are affected?
- MervinPraison PraisonAI <= 4.6.77; praisonai (PyPI) <= 4.6.77.
- Is there a fix for CVE-2026-62176?
- Yes: fixed in 4.6.78. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-62176 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-62176?
- Check whether you run MervinPraison 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
- Fixed in: 4.6.78
Technical details
The vulnerability is a code injection flaw (CWE-94) in the deploy/api.py and deploy/docker.py modules. The agents_file parameter is directly interpolated into an f-string template without sanitization, and the generated code is executed via subprocess.Popen(). An attacker can inject strings like `"); import os; os.system("id"); #` to break out of the string literal and inject arbitrary Python statements. The attack requires no user interaction and network access is possible if agents_file originates from an external API or config management system.
Affected products
- MervinPraison PraisonAI <= 4.6.77
Identifiers
- CVE-2026-62176
- GHSA-g6j7-pffp-8whg
Timeline
- 2026-10-07: advisory: GitHub Advisory Database published