CVE-2026-55522
HIGHDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Exploit Intelligence
Low risk: more likely to be exploited than 5% of all known CVEs.
References
Related Vulnerabilities
Other CWE-94 (Code Injection) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2017-9841 | Critical | 9.8 | 100% | KEV | Fix |
| CVE-2015-1635 | Critical | 9.8 | 100% | KEV | - |
| CVE-2022-22954 | Critical | 9.8 | 100% | KEV + Ransom | - |
| CVE-2025-3248 | Critical | 9.8 | 100% | KEV + Ransom | Fix |
| CVE-2025-49704 | High | 8.8 | 100% | KEV + Ransom | Fix |
| CVE-2021-22204 | Medium | 6.8 | 100% | KEV | Fix |
Common questions
How do I fix CVE-2026-55522?
No published fix for CVE-2026-55522 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-55522 being actively exploited?
Not that we know of. CVE-2026-55522 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.15% is the estimated probability that it will be exploited in the next 30 days. That is higher than 5% of all scored CVEs.
How severe is CVE-2026-55522?
CVE-2026-55522 has a CVSS v3 base score of 7.8, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-55522
Markdown
[](https://tridentstack.com/cve/CVE-2026-55522)HTML
<a href="https://tridentstack.com/cve/CVE-2026-55522"><img src="https://tridentstack.com/cve/badge/CVE-2026-55522.svg" alt="CVE-2026-55522"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-08-06.