CVE-2026-128065

MEDIUMPre-NVD 6.96.9
EchelonGraph scoreLOW confidence

This medium-severity CVE scores 6.9 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). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: a secondary CVSS source
Elevated

Also known asEUVD-2026-124776 (ENISA EUVD) · GHSA-gg5j-6742-v827 (GitHub Security Advisories)Source: ENISA EUVD

6.9EG
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: —CVSS: 6.9Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

@grpc/grpc-js implements the core functionality of gRPC purely in JavaScript, without a C++ addon. From 1.14.0 through 1.14.1, XdsServer in @grpc/grpc-js-xds can acknowledge Route and VirtualHost resources while failing to apply their RBACPerRoute override configurations. The override parser is not registered under the override message type, override maps are stored under a type URL instead of the configured HTTP filter name, and VirtualHost override maps are not read. When experimental RBAC is enabled and a trusted xDS control plane supplies a broad top-level ALLOW policy with a stricter matching override, affected servers evaluate RPCs under the broad policy and can accept requests that should be denied. This issue is fixed in version 1.14.2.

CVSS
6.9
EG Score
6.9MEDIUMlow confidence
EG Risk
62
EG Risk 62/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)
Severity69% × 45%
Impact severity (EG Severity): CVSS 6.9 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
—
EPSS %ILE
—
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 (6.9): severity, escalated by confirmed exploitation. This CVE's 6.9 is its impact severity (EG Severity), not escalated.

EG Severity
6.9 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
Unknown (no EPSS on record)Unknown, not low: FIRST has published no EPSS probability for this CVE.
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 12, 2026

Last Modified

November 13, 2026

Advisory Details (2)

Auto-updated Nov 13, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit.
GitHub commit Patch Available

commit b8f3ced4d469 (grpc/grpc-node)

Patch available: grpc/grpc-node @grpc/[email protected] (contains commit b8f3ced4d469)

https://github.com/grpc/grpc-node/commit/b8f3ced4d4699338dd33dc0f7b1d68d689a31d0e
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

RBAC override configs in VirtualHost and Route resources are not applied · Advisory · grpc/grpc-node · GitHub

https://github.com/grpc/grpc-node/security/advisories/GHSA-gg5j-6742-v827

Vendor Advisories for CVE-2026-128065(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
npm@grpc/grpc-js-xds @ 1.14.2 (fixes >= 1.14.0, < 1.14.2)—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.

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 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 → 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-13 02:28 UTCEchelonGraph re-scored
  2. 2026-11-13 02:28 UTCGHSA enrichmentGHSA-gg5j-6742-v827 · GitHub severity MODERATE
  3. 2026-11-13 01:42 UTCEchelonGraph re-scored
  4. 2026-11-13 01:42 UTCGHSA enrichmentGHSA-gg5j-6742-v827 · GitHub severity MODERATE
  5. 2026-11-13 00:52 UTCEchelonGraph re-scored
  6. 2026-11-13 00:52 UTCGHSA enrichmentGHSA-gg5j-6742-v827 · GitHub severity MODERATE
  7. 2026-11-13 00:28 UTCEchelonGraph re-scored
  8. 2026-11-13 00:28 UTCGHSA enrichmentGHSA-gg5j-6742-v827 · GitHub severity MODERATE
  9. 2026-11-13 00:01 UTCENISA EUVD ID recordedEUVD-2026-124776 · Source: ENISA EUVD
  10. 2026-11-12 23:46 UTCGHSA enrichmentGHSA-gg5j-6742-v827 · GitHub severity MODERATE
  11. 2026-11-12 22:52 UTCEchelonGraph re-scoredFirst assessed: 6.9 MEDIUM
  12. 2026-11-12 22:51 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-128065?
CVE-2026-128065 is a medium-severity vulnerability; its CVE record was published on November 12, 2026. @grpc/grpc-js implements the core functionality of gRPC purely in JavaScript, without a C++ addon. From 1.14.0 through 1.14.1, XdsServer in @grpc/grpc-js-xds can acknowledge Route and VirtualHost resources while failing to apply their RBACPerRoute override configurations. The override parser is not…
When was the CVE record for CVE-2026-128065 published?
The CVE record for CVE-2026-128065 was published on November 12, 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 13, 2026; the record at its source may have been updated since.
What is the CVSS score of CVE-2026-128065?
CVE-2026-128065 has a CVSS base score of 6.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-128065?
A fix for CVE-2026-128065 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-128065 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-128065

Explore →

Is Your Infrastructure Affected by CVE-2026-128065?

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