Host code execution via untrusted workflow YAML
Published Apr 14, 2026 · Updated Apr 14, 2026
Code injection in PraisonAI before 4.5.139 and praisonaiagents before 1.5.140 allows attackers to execute host commands via workflow YAML. JobWorkflowExecutor passes run values to subprocess.run(), evaluates script values with exec(), and launches python paths without validation or sandboxing. Exploitation requires attacker influence over a YAML file processed as a job workflow, exposing the host and accessible data or credentials.
Summary
What happened
Code injection in PraisonAI before 4.5.139 and praisonaiagents before 1.5.140 allows attackers to execute host commands via workflow YAML. JobWorkflowExecutor passes run values to subprocess.run(), evaluates script values with exec(), and launches python paths without validation or sandboxing. Exploitation requires attacker influence over a YAML file processed as a job workflow, exposing the host and accessible data or credentials.
The record
- CVE
- CVE-2026-40288
- Published
- Apr 14, 2026
- Updated
- Apr 14, 2026
- Vendor
- PraisonAI
- Product
- PraisonAI
- Classifications
- CWE-78, CWE-94, T1059
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 14, 2026CVE publishedPublication date reported by the CVE source.
- Apr 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 4.5.139
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GitHub advisory workflow YAML proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo