ZDF
Sign inSign up

Vulnerabilities

Security incident · CVE-2026-114604

GraphQL Tools: Prototype pollution in mergeIncrementalResult via non-primitive path segments

Published Oct 22, 2026 · catalog updated Oct 22, 2026 · Red Hat Red Hat Enterprise Linux

Last checked Nov 7, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-114604. EPSS is 0.52%. Act only if a listed version of Red Hat Red Hat Enterprise Linux is installed.

Gaps on this record

  • No vendor fix or required action is stored. Compare the linked advisory before you change production.

Same product and reporting

Severity
High7.3
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.52%
Remediation
Version ranges on file
Affected products
npm @graphql-tools · npm @graphql-tools/utils

## Report metadata | Field | Value | | --- | --- | | Package | (npm, ) | | Repository | https://github.com/ardatan/graphql-tools | | Component | / ( ) | | Vulnerability class | Prototype pollution (via unvalidated object path traversal) | | Verified against | Source read at ; HEAD ; published npm builds 10.10.0, 10.10.1, 11.0.0, 12.0.0, 12.0.1 | | Affected versions | >= 10.10.1 through the scanned 12.0.0 source; introduced by ("remove dset dependency"). 12.0.1 also reproduces. 10.10.0 does not. | | API surface | Public, documented export ( ) | | Affected in default configuration | Yes — no options are involved; the forbidden-key check in is the only defense and it is on by default | ## Summary merges an incremental GraphQL response part into an accumulated execution result by walking and assigning at the resolved location. tries to reject dangerous segments with strict string equality against , and (lines 50-52 and 60-62), but it never validates that a path segment is a primitive string or number. A JSON path segment such as is an array object, so and the guard passes; the very next statement does , whose coercion turns that array into the string key and resolves . The following, innocuous-looking segment is then assigned directly onto . In a consuming app, is the response part being merged — data parsed from an upstream / multipart or incremental-delivery response from another GraphQL server or transport. The TypeScript annotation is not a runtime check, so a malicious, compromised, or MITM'd upstream can choose the value and therefore choose global prototype keys and values in the gateway or client process. Comparable paths through the same helper, for contrast: - Plain string segment -> blocked by strict equality, lines 50-52 (confirmed by a control case in testing) - Array segment -> **unsafe: passes the guard at lines 50-52, then coerced to the key at lines 53-57** - Same operation in 10.10.0 and earlier, which used -> not exploitable (0/5 attack payloads succe

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • npm @graphql-toolsversion unspecified
  • npm @graphql-tools/utils>= 10.10.1, <= 12.0.1

How to fix CVE-2026-114604

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-114604. EPSS is 0.52%. Act only if a listed version of Red Hat Red Hat Enterprise Linux is installed.

Which versions are affected?

Compare what you have installed with >= 10.10.1, <= 12.0.1. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-1321: Improperly Controlled Modification of Object Prototype Attributes (Prototype Pollution); CWE-915: Improperly Controlled Modification of Dynamically-Determined Object Attributes. EPSS 0.52%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 22, 2026 · GitHub Advisory Database

    Detected

    ## Report metadata | Field | Value | | --- | --- | | Package | (npm, ) | | Repository | https://github.com/ardatan/graphql-tools | | Component | / ( ) | | Vulnerability class | Prototype pollution (via unvalidated object path traversal) | | Verified against | Source read at ; HEAD ; published npm builds 10.10.0, 10.10.1, 11.0.0, 12.0.0, 12.0.1 | | Affected versions | >= 10.10.1 through the scanned

  2. Oct 22, 2026 · GitHub Advisory Database

    Updated

    ## Report metadata | Field | Value | | --- | --- | | Package | (npm, ) | | Repository | https://github.com/ardatan/graphql-tools | | Component | / ( ) | | Vulnerability class | Prototype pollution (via unvalidated object path traversal) | | Verified against | Source read at ; HEAD ; published npm builds 10.10.0, 10.10.1, 11.0.0, 12.0.0, 12.0.1 | | Affected versions | >= 10.10.1 through the scanned

Sources

  • CVE.orgVulnerability recordCVE-2026-114604

    CVE.org record is not available yet.

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-114604

    30-day exploitation probability 0.52%

    first.org
  • GitHub Advisory DatabasePackage advisoryGHSA-c4qx-w738-7hr3

    GraphQL Tools: Prototype pollution in mergeIncrementalResult via non-primitive path segments

    github.com
  • GitLab Advisory DatabasePackage advisoryCVE-2026-114604

    mergeIncrementalResult merges an incremental GraphQL response part into an accumulated execution result by walking ['data', &hellip;incrementalResult.path] and assigning at the resolved location. setObjectKeyPath tries to reject dangerous segments with strict string equality against ' proto ', 'constructor' and 'prototype' (lines 50-52 and 60-62), but it never validates that a path segment is a pr

    advisories.gitlab.com
  • Red Hat Security DataVendor advisoryCVE-2026-114604

    @graphql-tools/utils: @graphql-tools/utils: Prototype pollution via unvalidated incremental response path segments

    access.redhat.com

References

Freshness

Last verified in this catalog Nov 6, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • Red Hat Security DataNov 7, 2026
  • FIRST EPSSNov 6, 2026
  • GitHub Advisory DatabaseOct 23, 2026
  • GitLab Advisory DatabaseOct 23, 2026
  • CVE.orgOct 23, 2026