Answer in brief
CVE-2026-40288 records a Critical severity (CVSS 9.8) vulnerability in PraisonAI has critical RCE via `type: job` workflow YAML. The current sources do not mark it as known exploited. The current feed maps PraisonAI (pip), praisonaiagents (pip). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 9.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps PraisonAI (pip), praisonaiagents (pip). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:a:praison:praisonai:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:a:praison:praisonaiagents:*:*:*:*:*:python:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| PraisonAIpip | <=4.5.138 | 4.5.139 |
| praisonaiagentspip | <=1.5.139 | 1.5.140 |
Published upstream
Apr 10, 2026
Evidence: source:ghsa:source_dates:source-dates:recordSource modified
Nov 16, 2026
Evidence: source:ghsa:source_dates:source-dates:recordFirst seen by HOL
Oct 28, 2026
`praisonai workflow run <file.yaml>` loads untrusted YAML and if `type: job` executes steps through `JobWorkflowExecutor` in job_workflow.py. This supports: - `run:` → shell command execution via `subprocess.run()` - `script:` → inline Python execution via `exec()` - `python:` → arbitrary Python script execution A malicious YAML file can execute arbitrary host commands. ### Affected Code - workflow.py → `action_run()` - job_workflow.py → `_exec_shell()`, `_exec_inline_python()`, `_exec_python_script()` ### PoC Create `exploit.yaml`: ```yaml type: job name: exploit steps: - name: write-file run: python -c "open('pwned.txt','w').write('owned')" ``` Run: ```bash praisonai workflow run exploit.yaml ``` ### Reproduction Steps 1. Save the YAML above as `exploit.yaml`. 2. Execute `praisonai workflow run exploit.yaml`. 3. Confirm `pwned.txt` appears in the working directory. ### Impact Remote or local attacker-supplied workflow YAML can execute arbitrary host commands and code, enabling full system compromise in CI or shared deployment contexts. **Reporter:** Lakshmikanthan K (letchupkt)
Quoted source text, attributed separately from HOL analysis.