Skip to content
Threat Brief

← All advisories

CVE-2026-40288

Critical 9.8No known exploitationFix available

PraisonAI: Critical RCE via `type: job` workflow YAML

Vendor advisory: GHSA-vc46-vw85-3wvm

Record last updated

CVSS score

9.8

Critical on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

None

No EPSS score available

CISA remediation deadline

None

Not in the KEV catalog

Description

PraisonAI is a multi-agent teams system. In versions below 4.5.139 of PraisonAI and 1.5.140 of praisonaiagents, the workflow engine is vulnerable to arbitrary command and code execution through untrusted YAML files. When praisonai workflow run loads a YAML file with type: job, the JobWorkflowExecutor in job_workflow.py processes steps that support run: (shell commands via subprocess.run()), script: (inline Python via exec()), and python: (arbitrary Python script execution)—all without any validation, sandboxing, or user confirmation. The affected code paths include action_run() in workflow.py and _exec_shell(), _exec_inline_python(), and _exec_python_script() in job_workflow.py. An attacker who can supply or influence a workflow YAML file (particularly in CI pipelines, shared repositories, or multi-tenant deployment environments) can achieve full arbitrary command execution on the host system, compromising the machine and any accessible data or credentials. This issue has been fixed in versions 4.5.139 of PraisonAI and 1.5.140 of praisonaiagents.

Weakness: CWE-78, CWE-94

Patching and mitigation

Patch status
Fix available (source: GitHub Advisory Database)
Fix documented (source date)
Mitigation
None documented
Vendor guidance
github.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
MervinPraisonPraisonAI< 4.5.139Not documentedCVE Program
MervinPraisonpraisonaiagents< 1.5.140Not documentedCVE Program
pipPraisonAIall versions up to and including 4.5.1384.5.139GitHub Advisory Database
pippraisonaiagentsall versions up to and including 1.5.1391.5.140GitHub Advisory Database

Timeline

  1. Disclosure

    CVE record published by GitHub_M

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by GitHub Advisory Database

    Source: GitHub Advisory Database (opens in a new tab)

Vendor guidance and references