CVE-2026-44336

CRITICALNVD 9.69.6—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.6 under NVD CVSS v3. EPSS exploit probability: 0.6%, top 55% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
9.6
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 9.6Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

PraisonAI is a multi-agent teams system. Prior to version 4.6.34, PraisonAI's MCP (Model Context Protocol) server (praisonai mcp serve) registers four file-handling tools by default — praisonai.rules.create, praisonai.rules.show, praisonai.rules.delete, and praisonai.workflow.show. Each accepts a path or filename string from MCP tools/call arguments and joins it onto ~/.praison/rules/ (or, for workflow.show, accepts an absolute path) with no containment check. The JSON-RPC dispatcher passes params["arguments"] blind to each handler via **kwargs without validating against the advertised input schema. By setting rule_name="../../" an attacker walks out of the rules directory and writes any file the running user can write. Dropping a Python .pth file into the user site-packages directory escalates this primitive to arbitrary code execution in any subsequent Python process the user spawns — the next praisonai CLI invocation, an IDE script run, the user's python REPL, or any background Python service. This issue has been patched in version 4.6.34.

CVSS v3
9.6
EG Score
9.6(medium)
EPSS
45.5%
KEV
Not listed

Published

May 8, 2026

Last Modified

May 11, 2026

Advisory Details (1)

Auto-updated May 8, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

PraisonAI MCP `tools/call` path-traversal => RCE via Python `.pth` injection · Advisory · MervinPraison/PraisonAI · GitHub

https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-9mqq-jqxf-grvw

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
praisonai0.0.1 ... 4.6.9 (725 versions)4.6.34—

Weakness Classification(5)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 52× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 153 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-44336?
CVE-2026-44336 is a critical vulnerability published on May 8, 2026. PraisonAI is a multi-agent teams system. Prior to version 4.6.34, PraisonAI's MCP (Model Context Protocol) server (praisonai mcp serve) registers four file-handling tools by default — praisonai.rules.create, praisonai.rules.show, praisonai.rules.delete, and praisonai.workflow.show. Each accepts a…
When was CVE-2026-44336 disclosed?
CVE-2026-44336 was first published in the National Vulnerability Database on May 8, 2026, with the most recent update on May 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44336 actively exploited?
CVE-2026-44336 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 45.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-44336?
CVE-2026-44336 has a CVSS v3 base score of 9.6 (NVD).
How do I remediate CVE-2026-44336?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44336, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-44336?

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

Start Free Scan →Browse All CVEs