CVE-2026-57145

CRITICALPre-NVD 9.19.1
EchelonGraph scoreLOW confidence

This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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: secondary
9.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: 9.1Exploit: None knownExposed: 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.62, src/praisonai/praisonai/tools/multiedit.py passes the LLM-controlled filepath parameter directly to open for reading and writing without traversal rejection, symlink resolution, a workspace boundary, or protected-path checks. Prompt-influenced agents can read files through edit and diff behavior or overwrite files accessible to the process, exposing secrets and enabling persistence or application tampering. This issue is fixed in 4.6.62.

CVSS v3
9.1
EG Score
9.1(low)
EG Risk
56(Track)
EG Risk 56/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
Severity91% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
30%
KEV
Not listed

Published

June 18, 2026

Last Modified

September 15, 2026

Advisory Details (3)

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

Arbitrary File Read/Write via `multiedit` Tool Without Path Validation · Advisory · MervinPraison/PraisonAI · GitHub

https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-29w3-p9w9-wc47
github_release Patch Available

PraisonAI v4.6.62

Patch available: MervinPraison/PraisonAI v4.6.62

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

commit 2a855c470077 (MervinPraison/PraisonAI)

Patch available: MervinPraison/PraisonAI v4.6.144 (contains commit 2a855c470077)

https://github.com/MervinPraison/PraisonAI/commit/2a855c470077c7d2e2479a575f7ef7f548d51c33

Vendor Advisories for CVE-2026-57145(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 (751 versions)4.6.61

Weakness Classification(1)

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 05:15 UTCEPSS rescore
  5. 2026-09-14 19:24 UTCEG score recompute
  6. 2026-09-14 18:28 UTCEG score recompute
  7. 2026-09-14 16:27 UTCEG score recompute
  8. 2026-07-30 22:29 UTCEG score recompute
  9. 2026-07-26 17:45 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-57145?
CVE-2026-57145 is a critical vulnerability published on June 18, 2026. PraisonAI is a multi-agent teams system. Prior to 4.6.62, src/praisonai/praisonai/tools/multiedit.py passes the LLM-controlled filepath parameter directly to open for reading and writing without traversal rejection, symlink resolution, a workspace boundary, or protected-path checks.…
When was CVE-2026-57145 disclosed?
CVE-2026-57145 was first published in the National Vulnerability Database on June 18, 2026, with the most recent update on September 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-57145 actively exploited?
CVE-2026-57145 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 70.2% of all scored CVEs.
What is the CVSS score of CVE-2026-57145?
CVE-2026-57145 has a CVSS v3 base score of 9.1 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-57145?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-57145, 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-57145

Explore →

Is Your Infrastructure Affected by CVE-2026-57145?

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