CVE-2026-114604

published 5 Nov 2026 · updated 9 Nov 2026

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

8.4HighCVSS 8.4EPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. No fixed version is recorded.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
ardatan>=10.10.1 <12.0.2

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-114604 severity on Zeptric[![CVE-2026-114604](https://zeptric.io/badge/cve/CVE-2026-114604.svg)](https://zeptric.io/cve/CVE-2026-114604)