CVE-2026-56839

HIGHPre-NVD 7.37.3
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 77% 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.3EG
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.3Exploit: 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. Prior to 4.6.59, the CODE_TOOLS wrappers keep _workspace_root as None and pass workspace=None to read_file, search_replace, and apply_diff helpers that enforce path containment only for a truthy workspace. An application that exposes code_read_file, code_search_replace, or code_apply_diff before set_workspace can therefore let prompt-influenced calls read and modify files outside the intended project directory, while explicitly configured workspaces remain effective. This vulnerability is fixed in 4.6.59.

CVSS v3
7.3
EG Score
7.3(medium)
EG Risk
49(Track*)
EG Risk 49/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
Severity73% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
23%
KEV
Not listed

Published

June 18, 2026

Last Modified

September 16, 2026

Advisory Details (3)

Auto-updated Sep 14, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_release.
github_release Patch Available

PraisonAI v4.6.59

Patch available: MervinPraison/PraisonAI v4.6.59

https://github.com/MervinPraison/PraisonAI/releases/tag/v4.6.59
github_commit Patch Available

commit b4270173d412 (MervinPraison/PraisonAI)

Patch available: MervinPraison/PraisonAI v4.6.143 (contains commit b4270173d412)

https://github.com/MervinPraison/PraisonAI/commit/b4270173d4123fb1ee8910588f0896668ee21b59
github Patch Available🟡 PoC Available

Code Agent Tools Fail Open Without a Workspace Boundary · Advisory · MervinPraison/PraisonAI · GitHub

https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-gcq3-mfvh-3x25

Vendor Advisories for CVE-2026-56839(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)
PackageVulnerable rangeFixed inDependents
praisonai0.0.1 ... 4.6.9 (749 versions)4.6.59

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 7× 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-18 19:28 UTCEPSS rescore
  2. 2026-09-17 19:31 UTCEPSS rescore
  3. 2026-09-16 14:08 UTCEPSS rescore
  4. 2026-09-16 13:47 UTCEG score recompute
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-14 18:09 UTCEG score recompute
  7. 2026-09-14 16:27 UTCEG score recompute
  8. 2026-07-30 22:30 UTCEG score recompute
  9. 2026-07-26 18:44 UTCEG score recompute
  10. 2026-07-23 03:20 UTCEG score recompute
  11. 2026-07-20 21:33 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-56839?
CVE-2026-56839 is a high vulnerability published on June 18, 2026. PraisonAI is a multi-agent teams system. Prior to 4.6.59, the CODETOOLS wrappers keep workspaceroot as None and pass workspace=None to readfile, searchreplace, and applydiff helpers that enforce path containment only for a truthy workspace. An application that exposes codereadfile,…
When was CVE-2026-56839 disclosed?
CVE-2026-56839 was first published in the National Vulnerability Database on June 18, 2026, with the most recent update on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56839 actively exploited?
CVE-2026-56839 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 76.6% of all scored CVEs.
What is the CVSS score of CVE-2026-56839?
CVE-2026-56839 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2026-56839?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56839, 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-56839

Explore →

Is Your Infrastructure Affected by CVE-2026-56839?

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