dbcve.org
PraisonaiagentsApplication · Praison

CVE-2026-40288

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-14
Fix available
A fix is available. Upgrade to 1.5.140 / 4.5.139 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 <file.yaml> 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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

PraisonAI and praisonaiagents contain a critical arbitrary command/code execution vulnerability in the workflow engine. When loading YAML files with type: job, the JobWorkflowExecutor directly executes shell commands via run: (subprocess.run()), inline Python via script: (exec()), and full Python scripts via python: without any validation, sandboxing, or user confirmation. Attackers with ability to supply or influence workflow YAML files can achieve full host compromise.

MitigationUpgrade to PraisonAI version 4.5.139 or higher and praisonaiagents version 1.5.140 or higher. Additionally, implement strict validation of YAML workflow files and avoid processing untrusted YAML files in production environments.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PraisonaiagentsApplication
Affected:< 1.5.140
PraisonaiApplication
Affected:< 4.5.139

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed PraisonAI version
    Run 'pip show praisonai' or 'pip show praisonaiagents' to see the installed version number
    Affected if Version is below 4.5.139 for praisonai or below 1.5.140 for praisonaiagents
  2. Identify workflow run usage
    Search command history or scripts for 'praisonai workflow run' commands, especially with YAML file arguments
    Affected if The 'praisonai workflow run' command is used to load YAML workflow files
  3. Inspect YAML workflow files for job type
    Examine YAML files loaded by workflow run commands for 'type: job' directive at the root level
    Affected if YAML files contain 'type: job' which triggers JobWorkflowExecutor processing
  4. Check for dangerous directives in YAML files
    Review YAML workflow files for 'run:', 'script:', or 'python:' directives under the job configuration
    Affected if YAML files contain untrusted run:, script:, or python: directives that will be executed without validation

A user is affected if they run a praisonai or praisonaiagents version below 4.5.139/1.5.140 and use 'praisonai workflow run' to load YAML files containing type: job with run:, script:, or python: directives from untrusted sources

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.5.140 / 4.5.139 or later
Fixed in 1.5.1404.5.139
Interim mitigation

Upgrade to PraisonAI version 4.5.139 or higher and praisonaiagents version 1.5.140 or higher. Additionally, implement strict validation of YAML workflow files and avoid processing untrusted YAML files in production environments.

Recommended fix High confidence

PraisonAI version 4.5.139 or praisonaiagents version 1.5.140

  1. Check which package is installed (praisonai or praisonaiagents): pip show praisonaiagents || pip show praisonai
  2. If praisonaiagents is installed, upgrade to fixed version: pip install --upgrade praisonaiagents==1.5.140
  3. If praisonai is installed, upgrade to fixed version: pip install --upgrade praisonai==4.5.139
  4. Verify the upgrade was successful: pip show praisonaiagents (should show version 1.5.140) or pip show praisonai (should show version 4.5.139)

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Praisonaiagents Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-40288 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-40288 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data