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%, top 95% 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, 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%CVSS: 7.8Exploit: Elevated riskExposed: 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. 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.8(medium)
EG Risk
51(Track*)
EG Risk 51/100SSVC: Track*

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%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

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.
github Patch Available🟡 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 rangeFixed inDependents
praisonai3.10.0 ... 4.6.9 (252 versions)4.6.58—
praisonaiagents0.12.12 ... 1.6.9 (277 versions)1.6.58—

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 50× 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.

  1. 2026-09-19 07:37 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-18 04:57 UTCEG score recompute
  4. 2026-09-17 19:31 UTCEPSS rescore
  5. 2026-09-17 01:04 UTCEG score recompute
  6. 2026-09-16 14:08 UTCEPSS rescore
  7. 2026-09-16 05:18 UTCEG score recompute
  8. 2026-09-16 05:15 UTCEPSS rescore
  9. 2026-09-15 16:13 UTCEG score recompute
  10. 2026-09-15 03:11 UTCEPSS rescore
  11. 2026-09-13 22:26 UTCEG score recompute
  12. 2026-09-13 16:47 UTCEPSS rescore
  13. 2026-09-11 18:02 UTCEG score recompute
  14. 2026-09-11 14:53 UTCEPSS rescore
  15. 2026-09-10 15:50 UTCEG score recompute
  16. 2026-09-10 09:35 UTCEPSS rescore
  17. 2026-09-09 10:44 UTCEG score recompute
  18. 2026-09-08 22:01 UTCEPSS rescore
  19. 2026-09-07 18:11 UTCEG score recompute
  20. 2026-09-07 16:01 UTCEPSS rescore
  21. 2026-09-06 20:38 UTCEG score recompute
  22. 2026-09-06 13:47 UTCEPSS rescore
  23. 2026-09-05 18:25 UTCEG score recompute
  24. 2026-09-04 09:26 UTCEG score recompute
  25. 2026-09-04 05:06 UTCEPSS rescore
Show 55 more
  1. 2026-09-03 06:41 UTCEG score recompute
  2. 2026-09-02 14:12 UTCEPSS rescore
  3. 2026-09-01 19:00 UTCEG score recompute
  4. 2026-09-01 13:54 UTCEPSS rescore
  5. 2026-09-01 04:40 UTCEPSS rescore
  6. 2026-08-30 23:30 UTCEG score recompute
  7. 2026-08-30 19:17 UTCEPSS rescore
  8. 2026-08-30 10:25 UTCEG score recompute
  9. 2026-08-30 01:22 UTCEPSS rescore
  10. 2026-08-29 21:20 UTCEG score recompute
  11. 2026-08-28 21:41 UTCEPSS rescore
  12. 2026-08-27 19:54 UTCEG score recompute
  13. 2026-08-27 14:25 UTCEPSS rescore
  14. 2026-08-27 03:32 UTCEG score recompute
  15. 2026-08-26 14:46 UTCEPSS rescore
  16. 2026-08-26 01:20 UTCEG score recompute
  17. 2026-08-25 13:49 UTCEPSS rescore
  18. 2026-08-24 23:06 UTCEG score recompute
  19. 2026-08-24 10:01 UTCEG score recompute
  20. 2026-08-23 07:49 UTCEG score recompute
  21. 2026-08-23 00:19 UTCEPSS rescore
  22. 2026-08-22 05:38 UTCEG score recompute
  23. 2026-08-21 23:49 UTCEPSS rescore
  24. 2026-08-21 03:26 UTCEG score recompute
  25. 2026-08-20 22:55 UTCEPSS rescore
  26. 2026-08-20 00:38 UTCEG score recompute
  27. 2026-08-19 17:04 UTCEPSS rescore
  28. 2026-08-18 22:24 UTCEG score recompute
  29. 2026-08-18 13:48 UTCEPSS rescore
  30. 2026-08-17 20:14 UTCEG score recompute
  31. 2026-08-17 13:47 UTCEPSS rescore
  32. 2026-08-16 18:03 UTCEG score recompute
  33. 2026-08-16 14:56 UTCEPSS rescore
  34. 2026-08-16 04:58 UTCEG score recompute
  35. 2026-08-16 02:14 UTCEPSS rescore
  36. 2026-08-15 02:47 UTCEG score recompute
  37. 2026-08-15 01:30 UTCEPSS rescore
  38. 2026-08-14 00:36 UTCEG score recompute
  39. 2026-08-13 22:00 UTCEPSS rescore
  40. 2026-08-12 22:25 UTCEG score recompute
  41. 2026-08-12 13:51 UTCEPSS rescore
  42. 2026-08-11 20:14 UTCEG score recompute
  43. 2026-08-11 07:08 UTCEG score recompute
  44. 2026-08-11 00:00 UTCEPSS rescore
  45. 2026-08-09 15:52 UTCEG score recompute
  46. 2026-08-09 13:46 UTCEPSS rescore
  47. 2026-08-09 02:47 UTCEG score recompute
  48. 2026-08-08 16:37 UTCEPSS rescore
  49. 2026-08-08 00:36 UTCEG score recompute
  50. 2026-08-07 11:31 UTCEG score recompute
  51. 2026-08-06 22:24 UTCEG score recompute
  52. 2026-08-06 13:47 UTCEPSS rescore
  53. 2026-08-05 20:32 UTCEG score recompute
  54. 2026-08-05 19:40 UTCEG score recompute
  55. 2026-08-05 19:40 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

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 in the National Vulnerability Database 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% probability of exploitation in the next 30 days, which ranks it in the top 95.3% of all scored CVEs.
What is the CVSS score of CVE-2026-55522?
CVE-2026-55522 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-55522?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55522, 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-55522

Explore →

Is Your Infrastructure Affected by CVE-2026-55522?

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

Start Free Scan →Browse All CVEs