CVE-2026-77604

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-11-09. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-117780 (ENISA EUVD) · GHSA-vvr2-h2jp-838m (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Code Graph RAG is an AI-powered knowledge graph and retrieval system for querying, understanding, and editing multi-language codebases. Prior to 0.0.345, the MCPToolsRegistry.read_file implementation in codebase_rag/mcp/tools.py joins attacker-controlled file_path input to project_root without resolving and verifying containment when offset or limit selects the paginated branch. An absolute path causes pathlib to discard the configured root, while relative traversal can also resolve outside it. The protected non-paginated branch uses validate_project_path, but the paginated branch bypasses that validation before opening the path. An unauthenticated caller of a network-exposed HTTP MCP server can therefore read arbitrary UTF-8-readable files available to the server process, including credentials, environment data, private keys, source, and configuration; local callers through the stdio transport can reach the same vulnerable code path. This issue is fixed in version 0.0.345.

CVSS v3
7.5
EG Score
7.5HIGHhigh confidence
EG Risk
65
EG Risk 65/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
33rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 5, 2026

Last Modified

November 12, 2026

Advisory Details (3)

Auto-updated Nov 5, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_release.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

MCP paginated read_file path traversal / arbitrary file read · Advisory · vitali87/code-graph-rag · GitHub

https://github.com/vitali87/code-graph-rag/security/advisories/GHSA-vvr2-h2jp-838m
GitHub release Patch Available

v0.0.345

Patch available: vitali87/code-graph-rag v0.0.345

https://github.com/vitali87/code-graph-rag/releases/tag/v0.0.345
GitHub commit

commit 6541e920a279 (vitali87/code-graph-rag)

Fix landed in vitali87/code-graph-rag commit 6541e920a279 — awaiting tagged release

https://github.com/vitali87/code-graph-rag/commit/6541e920a27961fa8f3ff49ef38c0e0bd09cd626

Vendor Advisories for CVE-2026-77604(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
pipcode-graph-rag @ 0.0.345 (fixes < 0.0.345)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
code-graph-rag0.0.100 ... 0.0.99 (10 versions)
  • every version up to 0.0.345: fixed in 0.0.345
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 13× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-12 22:28 UTCEchelonGraph re-scored
  2. 2026-11-12 22:28 UTCGHSA enrichmentGHSA-vvr2-h2jp-838m · GitHub severity HIGH · GitHub CVSS 7.5
  3. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  4. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  5. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  6. 2026-11-09 23:41 UTCEchelonGraph re-scored
  7. 2026-11-09 23:41 UTCGHSA enrichmentGHSA-vvr2-h2jp-838m · GitHub severity HIGH · GitHub CVSS 7.5
  8. 2026-11-09 22:55 UTCEchelonGraph re-scored
  9. 2026-11-09 22:55 UTCGHSA enrichmentGHSA-vvr2-h2jp-838m · GitHub severity HIGH · GitHub CVSS 7.5
  10. 2026-11-09 21:46 UTCEchelonGraph re-scored
  11. 2026-11-09 21:46 UTCGHSA enrichmentGHSA-vvr2-h2jp-838m · GitHub severity HIGH · GitHub CVSS 7.5
  12. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  13. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  14. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  15. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  16. 2026-11-05 21:04 UTCENISA EUVD ID recordedEUVD-2026-117780 · Source: ENISA EUVD
  17. 2026-11-05 20:18 UTCEchelonGraph re-scoredFirst assessed: 7.5 HIGH
  18. 2026-11-05 20:17 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Same product

1 shown

PyPI:code-graph-rag

Frequently asked(5)

What is CVE-2026-77604?
CVE-2026-77604 is a high-severity vulnerability; its CVE record was published on November 5, 2026. Code Graph RAG is an AI-powered knowledge graph and retrieval system for querying, understanding, and editing multi-language codebases. Prior to 0.0.345, the MCPToolsRegistry.read_file implementation in codebase_rag/mcp/tools.py joins attacker-controlled file_path input to project_root without…
When was the CVE record for CVE-2026-77604 published?
The CVE record for CVE-2026-77604 was published on November 5, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 12, 2026; the record at its source may have been updated since.
Is CVE-2026-77604 actively exploited?
CVE-2026-77604 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-77604?
CVE-2026-77604 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-77604?
A fix for CVE-2026-77604 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-77604 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-77604

Explore →

Is Your Infrastructure Affected by CVE-2026-77604?

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

Book a Demo →Browse All CVEs