CVE-2026-57117: MervinPraison PraisonAI · OS Command Injection
Affects MervinPraison PraisonAISource CVE Database V5
Not known to be exploited · CVSS 8.8 High : upgrade to 4.6.59 soon.
Data as of 26 Oct 2026, 14:18 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.6.59
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 23 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade PraisonAI and mervinpraison/PraisonAI to 4.6.59.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| MervinPraisonPraisonAI | Affected
| Fixed in
|
GitHubmervinpraison/PraisonAIpkg:github/mervinpraison/PraisonAIOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade PraisonAI to version 4.6.59 or later, where this vulnerability has been patched. No other mitigations are specified or recommended by the vendor advisory.
Description
CVE-2026-57117 is an OS command injection vulnerability in MervinPraison PraisonAI versions 4.6.10 up to but not including 4.6.59. The vulnerability arises because file operation commands are constructed using raw path arguments without proper neutralization, allowing an attacker to inject arbitrary shell commands. This affects local subprocess execution and Docker container execution environments. The issue has been patched in version 4.6.59.