PatchSiren cyber security CVE debrief
CVE-2026-61444 MervinPraison CVE debrief
CVE-2026-61444 is a critical code injection vulnerability in PraisonAI versions before 4.6.78. The vulnerability exists in deploy/api.py where the agents_file parameter is directly interpolated into an f-string without sanitization. Attackers can inject arbitrary Python code that executes when the generated server code runs via subprocess.Popen(). This vulnerability has a CVSS score of 9.4 and is considered critical. Users of PraisonAI versions before 4.6.78 should apply the patch to prevent code injection attacks. The vulnerability allows for arbitrary code execution, which can lead to a complete compromise of the affected system.
- Vendor
- MervinPraison
- Product
- PraisonAI
- CVSS
- CRITICAL 9.4
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-10-07
- Original CVE updated
- 2026-10-07
- Advisory published
- 2026-10-07
- Advisory updated
- 2026-10-07
Who should care
Users of PraisonAI versions before 4.6.78 should apply the patch to prevent code injection attacks. This vulnerability has a CVSS score of 9.4 and is considered critical. Operators of PraisonAI, platform administrators, and security teams should review the vulnerability and apply the patch as soon as possible. Additionally, defenders should review compensating controls for exposed systems while remediation is scheduled and verified.
Technical summary
The vulnerability exists in deploy/api.py where the agents_file parameter is directly interpolated into an f-string without sanitization. Attackers can inject arbitrary Python code that executes when the generated server code runs via subprocess.Popen(). The CVSS vector is CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. The vulnerability allows for arbitrary code execution, which can lead to a complete compromise of the affected system.
Defensive priority
High
Recommended defensive actions
- Apply the patch to upgrade PraisonAI to version 4.6.78 or later
- Review and sanitize user input to prevent code injection attacks
- Monitor for suspicious activity and implement compensating controls
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
- Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
- Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
Evidence notes
The CVE record was published on 2026-07-10T15:16:50.610Z and has not been modified since then. The NVD entry is currently Deferred. There is limited information available about the vulnerability, and defenders should verify the affected scope and severity with the vendor. The PraisonAI versions before 4.6.78 are reportedly vulnerable, but specific details about the vulnerability and its impact are not publicly available.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-61444 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-61444
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-61444 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-61444
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-g6j7-pffp-8whg
-
Source reference
Unverified legacy reference
URL: https://www.vulncheck.com/advisories/praisonai-before-code-injection-via-f-string
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.