CVE-2026-114604

HIGHPre-NVD 8.48.4
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (44th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

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

Also known asEUVD-2026-117792 (ENISA EUVD) · GHSA-c4qx-w738-7hr3 (GitHub Security Advisories)Source: ENISA EUVD

8.4EG
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.5%CVSS: 8.4Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

GraphQL Tools provides utilities for building, stitching, and mocking GraphQL schemas. From 10.10.1 until 12.0.2, the @graphql-tools/utils mergeIncrementalResult helper passes incrementalResult.path segments to setObjectKeyPath without runtime primitive-type validation. A non-primitive segment can bypass strict comparisons against __proto__, constructor, and prototype, then be coerced during property access so a malicious or compromised upstream incremental GraphQL response writes attacker-controlled properties to Object.prototype in the consuming Node.js process. The affected implementation is packages/utils/src/mergeIncrementalResult.ts and is reachable when consumers merge untrusted @defer or @stream transport results. This issue is fixed in version 12.0.2.

CVSS
8.4
EG Score
8.4HIGHmedium confidence
EG Risk
54
EG Risk 54/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)
Severity84% × 45%
Impact severity (EG Severity): CVSS 8.4 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.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.5%
EPSS %ILE
44th
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 (8.4): severity, escalated by confirmed exploitation. This CVE's 8.4 is its impact severity (EG Severity), not escalated.

EG Severity
8.4 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-10). 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, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade 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, Track* at medium and Attend at high mission impact.

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 no (CISA Vulnrichment) · Technical impact total (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; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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

October 22, 2026

Last Modified

November 9, 2026

Advisory Details (4)

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

commit 20d36a5c6eb8 (ardatan/graphql-tools)

Fix landed in ardatan/graphql-tools commit 20d36a5c6eb8 — awaiting tagged release

https://github.com/ardatan/graphql-tools/commit/20d36a5c6eb8fd5524420988e01a48618c450d70
GitHub commit

commit 19f5b3373fd7 (ardatan/graphql-tools)

Fix landed in ardatan/graphql-tools commit 19f5b3373fd7 — awaiting tagged release

https://github.com/ardatan/graphql-tools/commit/19f5b3373fd7ace0688d19950fc529ce8347952a
GitHub pull request

Fix prototype pollution in mergeIncrementalResult path walker

Fix merged in ardatan/graphql-tools PR #8467 on 2026-09-30 — awaiting tagged release

https://github.com/ardatan/graphql-tools/pull/8467
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Prototype pollution in mergeIncrementalResult via non-primitive path segments · Advisory · ardatan/graphql-tools · GitHub

https://github.com/ardatan/graphql-tools/security/advisories/GHSA-c4qx-w738-7hr3

Vendor Advisories for CVE-2026-114604(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@graphql-tools/utils @ 12.0.2 (fixes >= 10.10.1, <= 12.0.1)—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)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
@graphql-tools/utils—
  • 10.10.1 up to 12.0.2: fixed in 12.0.2
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 16× 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-12 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  2. 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  3. 2026-11-11 03:37 UTCEchelonGraph re-scored
  4. 2026-11-11 03:37 UTCGHSA enrichmentGHSA-c4qx-w738-7hr3 · GitHub severity HIGH
  5. 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  6. 2026-11-09 19:27 UTCEchelonGraph re-scored
  7. 2026-11-09 19:27 UTCGHSA enrichmentGHSA-c4qx-w738-7hr3 · GitHub severity HIGH
  8. 2026-11-09 18:41 UTCEchelonGraph re-scored
  9. 2026-11-09 18:41 UTCGHSA enrichmentGHSA-c4qx-w738-7hr3 · GitHub severity HIGH
  10. 2026-11-09 18:40 UTCEchelonGraph re-scored
  11. 2026-11-09 18:40 UTCGHSA enrichmentGHSA-c4qx-w738-7hr3 · GitHub severity HIGH
  12. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  13. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  14. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  15. 2026-11-06 16:36 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  16. 2026-11-05 22:04 UTCENISA EUVD ID recordedEUVD-2026-117792 · Source: ENISA EUVD
  17. 2026-11-05 21:28 UTCEchelonGraph re-scored
  18. 2026-11-05 21:28 UTCGHSA enrichmentGHSA-c4qx-w738-7hr3 · GitHub severity HIGH
  19. 2026-11-05 20:48 UTCEchelonGraph re-scoredFirst assessed: 8.4 HIGH
  20. 2026-11-05 20:48 UTCGHSA enrichmentGHSA-c4qx-w738-7hr3 · GitHub severity HIGH
  21. 2026-11-05 20:47 UTCMITRE cvelistV5CVSS → 8.4 · CVSS v4 → 8.4
  22. 2026-11-01 07:59 UTCGHSA enrichmentGHSA-c4qx-w738-7hr3 · GitHub severity HIGH
  23. 2026-10-25 14:50 UTCEchelonGraph re-scored
  24. 2026-10-22 17:21 UTCEchelonGraph re-scored

Related CVEs(same product + same CWE)

Same product

1 shown

npm:@graphql-tools/utils

Frequently asked(5)

What is CVE-2026-114604?
CVE-2026-114604 is a high-severity vulnerability; its CVE record was published on October 22, 2026. GraphQL Tools provides utilities for building, stitching, and mocking GraphQL schemas. From 10.10.1 until 12.0.2, the @graphql-tools/utils mergeIncrementalResult helper passes incrementalResult.path segments to setObjectKeyPath without runtime primitive-type validation. A non-primitive segment can…
When was the CVE record for CVE-2026-114604 published?
The CVE record for CVE-2026-114604 was published on October 22, 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 9, 2026; the record at its source may have been updated since.
Is CVE-2026-114604 actively exploited?
CVE-2026-114604 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-114604?
CVE-2026-114604 has a CVSS base score of 8.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-114604?
A fix for CVE-2026-114604 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-114604 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-114604

Explore →

Is Your Infrastructure Affected by CVE-2026-114604?

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

Book a Demo →Browse All CVEs