GraphQL Tools: Prototype pollution in mergeIncrementalResult via non-primitive path segments
Affects @graphql-tools/utils 10.10.1 through 12.0.1 when code passes incremental payloads from untrusted sources to mergeIncrementalResult. Fixed in 12.0.2.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 12.0.2
- Who is exposed
- Default setups
Do first: Check every install: default setups are affected.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 50/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Default setups
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
GraphQL Tools, a library for building, stitching, and mocking GraphQL schemas, has a prototype pollution flaw in its mergeIncrementalResult helper. A malicious or compromised upstream server sending crafted incremental (@defer or @stream) responses can remotely, without logging in, write attacker-controlled properties to Object.prototype in the consuming Node.js process.
Read the original description
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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure22/25Default setups, reachable over the network without a login
- Reach20/20@graphql-tools/utils: 57.5M downloads a week
- Severity8.4/10CVSS 8.4
- No patch0/5No signal
What would change the score
- Would score about 90 if added to CISA KEV
- Would score about 85 if CISA's SSVC rates exploitation active
Impact
What to do
Check every install: default setups are affected.
Upgrade to a fixed version: 12.0.2.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- ardatan graphql-tools
From 10.10.1 · fixed in 12.0.2
- @graphql-tools/utilsnpm
From 10.10.1 · fixed in 12.0.2
Evidence 5
- Advisory
- Repository
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-114604
Is CVE-2026-114604 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The bug lets an incremental GraphQL response add arbitrary properties with attacker-chosen values to Object.prototype in the consuming Node.js process. This is prototype pollution.Source: github.com
Which versions are affected by CVE-2026-114604?
graphql-tools: from 10.10.1 before 12.0.2. @graphql-tools/utils (npm): from 10.10.1 before 12.0.2.Source: cve.now feed data
Am I affected, and how do I check?
Affected are @graphql-tools/utils versions 10.10.1 through 12.0.1, and the graphql-tools package in the same ranges. The setup also needs code that calls the public mergeIncrementalResult helper on incremental payloads from another GraphQL server or other untrusted transport, with no runtime check that path segments are only strings or numbers, and with Object.prototype not frozen. The installed version can be checked with npm ls @graphql-tools/utils.Source: github.com
How do I fix CVE-2026-114604?
Upgrade @graphql-tools/utils to 12.0.2 or later, which the advisory says is not affected.Source: github.com