CVE-2026-57586

HIGHPre-NVD 8.68.6—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 90% 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
8.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.6Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

CodeRAG is a lightweight semantic code search and distillation utility for AI coding agents. Prior to 1.3.1, the default agent-coderag sync flow in code_rag/entry/cli.py calls sync_dependencies for an indexed path, and code_rag/core/manager.py treats build.gradle or build.gradle.kts as sufficient to invoke _sync_gradle. _sync_gradle prefers a repository-controlled gradlew or gradlew.bat file and passes it directly to asyncio.create_subprocess_exec with the repository root as the working directory; validate_path in code_rag/core/utils.py constrains the directory location but does not validate the executable's content or integrity. A victim who indexes an attacker-controlled Gradle repository therefore executes attacker-supplied code with the victim's operating-system privileges, allowing disclosure, modification, persistence, or denial of service in the user environment. This issue is fixed in 1.3.1.

CVSS v3
8.6
EG Score
8.6(medium)
EG Risk
39(Track)
EG Risk 39/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
Severity86% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
10%
KEV
Not listed

Published

September 15, 2026

Last Modified

September 15, 2026

Advisory Details (3)

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

v1.3.1

Patch available: naranor/agent-coderag v1.3.1

https://github.com/naranor/agent-coderag/releases/tag/v1.3.1
github_commit Patch Available

commit 1d917513cd95 (naranor/agent-coderag)

Patch available: naranor/agent-coderag v1.3.1 (contains commit 1d917513cd95)

https://github.com/naranor/agent-coderag/commit/1d917513cd95209bab9cbb5fe00df84989805e7d
github Patch Available🟡 PoC Available

Gradle Wrapper Execution During Dependency Discovery Enables Arbitrary Code Execution · Advisory · naranor/agent-coderag · GitHub

https://github.com/naranor/agent-coderag/security/advisories/GHSA-wg5p-8h9p-3mr7

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
agent-coderag1.1.0, 1.2.0, 1.2.1, 1.3.01.3.1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 20× 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-24 21:40 UTCEG score recompute
  2. 2026-09-24 14:04 UTCEPSS rescore
  3. 2026-09-23 21:23 UTCEG score recompute
  4. 2026-09-23 17:54 UTCEPSS rescore
  5. 2026-09-22 21:15 UTCEG score recompute
  6. 2026-09-22 09:11 UTCEG score recompute
  7. 2026-09-20 20:59 UTCEG score recompute
  8. 2026-09-20 20:16 UTCEPSS rescore
  9. 2026-09-19 20:51 UTCEG score recompute
  10. 2026-09-18 20:41 UTCEG score recompute
  11. 2026-09-18 19:28 UTCEPSS rescore
  12. 2026-09-17 20:12 UTCEG score recompute
  13. 2026-09-17 19:31 UTCEPSS rescore
  14. 2026-09-16 20:02 UTCEG score recompute
  15. 2026-09-16 14:08 UTCEPSS rescore
  16. 2026-09-15 19:38 UTCEG score recompute
  17. 2026-09-15 18:24 UTCEG score recompute
  18. 2026-09-15 15:31 UTCEG score recompute
  19. 2026-09-15 14:33 UTCEG score recompute
  20. 2026-09-15 14:32 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-57586?
CVE-2026-57586 is a high vulnerability published on September 15, 2026. CodeRAG is a lightweight semantic code search and distillation utility for AI coding agents. Prior to 1.3.1, the default agent-coderag sync flow in coderag/entry/cli.py calls syncdependencies for an indexed path, and coderag/core/manager.py treats build.gradle or build.gradle.kts as sufficient to…
When was CVE-2026-57586 disclosed?
CVE-2026-57586 was first published in the National Vulnerability Database 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-57586 actively exploited?
CVE-2026-57586 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 89.7% of all scored CVEs.
What is the CVSS score of CVE-2026-57586?
CVE-2026-57586 has a CVSS v3 base score of 8.6 (NVD).
How do I remediate CVE-2026-57586?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-57586, 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-57586

Explore →

Is Your Infrastructure Affected by CVE-2026-57586?

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