CVE-2026-55522

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (11th percentile of EPSS-scored CVEs). 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, secondary
Elevated
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

PraisonAI is a multi-agent teams system. In versions 3.9.26 through 4.6.57 of praiseonai and 0.12.12 through 1.6.57 of praiseonaiagents, the workflow "include" feature is vulnerable to code execution. Workflow._execute_include() implicitly imports and runs an included recipe's tools.py via a raw importlib.util.spec_from_file_location() and spec.loader.exec_module() call, without honoring the PRAISONAI_ALLOW_TEMPLATE_TOOLS/PRAISONAI_ALLOW_LOCAL_TOOLS autoload opt-in gates or routing through the centralized safe loader that protects the other tools.py autoload paths. As a result, a workflow that includes an attacker-controlled local recipe directory executes arbitrary module-level Python code during include setup, before any child workflow parsing or model call, and the same sink is reachable through the higher-level praisonai.recipe.run() recipe API. An attacker who can cause a victim process to run a workflow or recipe that includes an untrusted local recipe achieves arbitrary Python code execution as the PraisonAI process user, a variant that bypasses the hardening applied to the previously disclosed automatic tools.py RCE advisory family. This issue has been fixed in version 4.6.58 of praisonai and 1.6.58 of praisonaiagents.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
51
EG Risk 51/100CISA SSVC

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
Severity78% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.
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.2%
EPSS %ILE
11th
KEV
Not listed

CISA SSVCTrack 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 no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 5, 2026

Last Modified

September 8, 2026

Advisory Details (1)

Auto-updated Aug 5, 2026
🔬 Proof of concept available. Patch available. Sources: github.
githubMentions a patch (unverified)🟡 PoC Available

Workflow Include Bypasses tools.py Autoload Opt-In and Executes Included Recipe Code · Advisory · MervinPraison/PraisonAI · GitHub

https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-hxmv-c4g6-5fqc

Vendor Advisories for CVE-2026-55522(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(2 across 1 ecosystem)
PyPI(2)
PackageVulnerable rangeFix by version rangeDependents
praisonai3.10.0 ... 4.6.9 (252 versions)
  • 3.9.26 up to 4.6.58: fixed in 4.6.58
—
praisonaiagents0.12.12 ... 1.6.9 (277 versions)
  • 0.12.12 up to 1.6.58: fixed in 1.6.58
—

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 46× 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 112 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-55522?
CVE-2026-55522 is a high vulnerability published on August 5, 2026. PraisonAI is a multi-agent teams system. In versions 3.9.26 through 4.6.57 of praiseonai and 0.12.12 through 1.6.57 of praiseonaiagents, the workflow "include" feature is vulnerable to code execution. Workflow.executeinclude() implicitly imports and runs an included recipe's tools.py via a raw…
When was CVE-2026-55522 disclosed?
CVE-2026-55522 was first published on August 5, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55522 actively exploited?
CVE-2026-55522 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (11th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-55522?
CVE-2026-55522 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-55522?
A fix for CVE-2026-55522 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-55522 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-55522?

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