PraisonAI is a multi-agent teams system. Prior to praisonai 4.6.51, is_path_within_directory() uses os.path.abspath() rather than os.path.realpath() for the workspace boundary. A symlink inside workspace can point outside and still pass the check, allowing read_file and other code tools to access files outside the configured workspace. This issue is fixed in version 4.6.58.
CVE-2026-55540
HIGHPre-NVD 7.17.1—Trending — 3 sources updated this weekElevated
EchelonGraph scoreMEDIUM confidence
This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 81% 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
7.1EG
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.1Exploit: Elevated riskExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.1
- EG Score
- 7.1(medium)
- EG Risk
- 48(Track*)EG Risk 48/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 computedSeverity71% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Watch closely — could escalate to Attend. - EPSS PROB
- 0%
- EPSS %ILE
- 19%
- KEV
- Not listed
Published
August 25, 2026
Last Modified
August 27, 2026
Advisory Details (3)
Auto-updated Aug 25, 2026🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
github Patch Available🟡 PoC Available
[Path Traversal] agent tools escape the configured workspace via symlinks · Advisory · MervinPraison/PraisonAI · GitHub
https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-ch89-h4r2-c8f8github_release Patch Available
PraisonAI v4.6.58
Patch available: MervinPraison/PraisonAI v4.6.58
https://github.com/MervinPraison/PraisonAI/releases/tag/v4.6.58github_commit Patch Available
commit 2f9677abb2ea (MervinPraison/PraisonAI)
Patch available: MervinPraison/PraisonAI v4.6.137 (contains commit 2f9677abb2ea)
https://github.com/MervinPraison/PraisonAI/commit/2f9677abb2ea68eab864ee8b6a828fd0141612e1Vendor Advisories for CVE-2026-55540(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| praisonai | 0.0.1 ... 4.6.9 (748 versions) | 4.6.58 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 11× 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.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 03:09 UTCEG score recompute
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 17:36 UTCEG score recompute
- 2026-08-27 17:14 UTCEG score recompute
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-27 00:14 UTCEG score recompute
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 15:21 UTCEG score recompute
- 2026-08-25 15:15 UTCEG score recompute
- 2026-08-25 15:14 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-55540?
CVE-2026-55540 is a high vulnerability published on August 25, 2026. PraisonAI is a multi-agent teams system. Prior to praisonai 4.6.51, ispathwithindirectory() uses os.path.abspath() rather than os.path.realpath() for the workspace boundary. A symlink inside workspace can point outside and still pass the check, allowing readfile and other code tools to access files…
When was CVE-2026-55540 disclosed?
CVE-2026-55540 was first published in the National Vulnerability Database on August 25, 2026, with the most recent update on August 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55540 actively exploited?
CVE-2026-55540 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 80.9% of all scored CVEs.
What is the CVSS score of CVE-2026-55540?
CVE-2026-55540 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-55540?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55540, 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-55540
Is Your Infrastructure Affected by CVE-2026-55540?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.