Quick answers
- Is CVE-2026-56078 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-56078 being exploited in the wild.
- How severe is CVE-2026-56078?
- High severity, with a CVSS score of 8.8, published 18 June 2026.
- Which products and versions are affected?
- MervinPraison PraisonAI Agents < 1.5.115; praisonaiagents (PyPI) ECOSYSTEM:introduced=0,fixed=1.5.115.
- Is there a fix for CVE-2026-56078?
- Yes. praisonaiagents (PyPI): upgrade to 1.5.115 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-56078 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-56078?
- Check whether you run MervinPraison PraisonAI Agents or praisonaiagents (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- praisonaiagents (PyPI): upgrade to 1.5.115 or later
pip install "praisonaiagents>=1.5.115"
Technical details
A path traversal vulnerability (CWE-22) exists in the MultiAgentMonitor component of PraisonAI. The root cause is the lack of sanitization of agent IDs when they are concatenated with a base directory to create file paths. An authenticated attacker with network access can provide an agent ID containing traversal sequences (e.g., '../') to read, write, or overwrite files outside the intended directory. This can lead to sensitive information disclosure, denial of service via file corruption, or remote code execution if executable files are overwritten. The issue is fixed in version 1.5.115. Additionally, the advisory notes a related memory state leakage issue where non-unique agent IDs allow context sharing between different agents.
Affected products
- MervinPraison PraisonAI (praisonaiagents) < 1.5.115
Identifiers
- CVE-2026-56078
- GHSA-766v-q9x3-g744
- PYSEC-2026-2943
Timeline
- 2026-04-07: advisory: Initial GitHub security advisory published
- 2026-06-18: disclosed: CVE-2026-56078 published to NVD
- 2026-06-18: patched: Fix confirmed in version 1.5.115