CVE-2026-40288

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.9% (59th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this weekElevated
9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
75
EG Risk 75/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.9%
EPSS %ILE
59th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

April 14, 2026

Last Modified

April 20, 2026

Advisory Details (1)

Auto-updated Oct 8, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

Critical RCE via `type: job` workflow YAML · Advisory · MervinPraison/PraisonAI · GitHub

https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-vc46-vw85-3wvm

Affected Packages

(2 across 1 ecosystem)
PyPI(2)
PackageVulnerable rangeFix by version rangeDependents
praisonai0.0.1 ... 4.5.98 (695 versions)
  • every version up to 4.5.139: fixed in 4.5.139
—
praisonaiagents0.0.1 ... 1.5.99 (519 versions)
  • every version up to 1.5.140: fixed in 1.5.140
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 16× in last 7d / 32× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 96 of 183 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 100 are merged into the row they repeat. The 87 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-16 18:53 UTCEG score recompute
  2. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  3. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  4. 2026-10-15 16:03 UTCEG score recompute
  5. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  6. 2026-10-14 10:12 UTCEG score recompute
  7. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  8. 2026-10-13 08:33 UTCEG score recompute
  9. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  10. 2026-10-12 16:09 UTCEG score recompute
  11. 2026-10-11 19:52 UTCEG score recompute
  12. 2026-10-11 17:05 UTCEG score recompute
  13. 2026-10-11 14:31 UTCEG score recompute
  14. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  15. 2026-10-11 07:25 UTCOSV refresh
  16. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  17. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  18. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  19. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  20. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  21. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  22. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  23. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  24. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  25. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.9% · 58th percentile
Show 71 more
  1. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  2. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  3. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  4. 2026-09-21 19:49 UTCOSV refresh
  5. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  6. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  7. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  8. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  9. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  10. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  11. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  12. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  13. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  14. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  15. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  16. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  17. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  18. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  19. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  20. 2026-09-02 16:08 UTCOSV refresh
  21. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  22. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  23. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  24. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  25. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  26. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  27. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  28. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  29. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  30. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  31. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  32. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  33. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  34. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  35. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  36. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  37. 2026-08-16 06:51 UTCEG score recompute
  38. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  39. 2026-08-15 02:13 UTCEG score recompute
  40. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  41. 2026-08-14 04:53 UTCEG score recompute
  42. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  43. 2026-08-12 19:08 UTCEG score recompute
  44. 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  45. 2026-08-11 19:15 UTCEG score recompute
  46. 2026-08-11 13:43 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  47. 2026-08-11 02:49 UTCEG score recompute
  48. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  49. 2026-08-09 16:40 UTCEG score recompute
  50. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  51. 2026-08-09 04:15 UTCEG score recompute
  52. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  53. 2026-08-07 17:46 UTCEG score recompute
  54. 2026-08-06 17:29 UTCEG score recompute
  55. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  56. 2026-08-05 23:32 UTCEG score recompute
  57. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  58. 2026-08-04 15:10 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  59. 2026-08-04 10:38 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  60. 2026-08-03 21:46 UTCEG score recompute
  61. 2026-08-03 10:36 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  62. 2026-08-02 13:30 UTCEG score recompute
  63. 2026-08-02 02:27 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  64. 2026-08-01 04:16 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  65. 2026-07-30 16:28 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  66. 2026-07-30 01:30 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  67. 2026-07-27 14:13 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  68. 2026-07-26 14:54 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  69. 2026-07-25 14:18 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  70. 2026-07-24 14:17 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  71. 2026-07-23 14:18 UTCEPSS rescoreEPSS 0.6% · 45th percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-40288?
CVE-2026-40288 is a critical-severity vulnerability; its CVE record was published on April 14, 2026. 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…
When was the CVE record for CVE-2026-40288 published?
The CVE record for CVE-2026-40288 was published on April 14, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of April 20, 2026; the record at its source may have been updated since.
Is CVE-2026-40288 actively exploited?
CVE-2026-40288 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (59th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-40288?
CVE-2026-40288 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-40288?
A fix for CVE-2026-40288 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-40288

Explore →

Is Your Infrastructure Affected by CVE-2026-40288?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs