Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-c4qx-w738-7hr3 | GraphQL Tools: Prototype pollution in mergeIncrementalResult via non-primitive path segments |
Thu, 05 Nov 2026 22:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Ardatan
Ardatan graphql-tools |
|
| Vendors & Products |
Ardatan
Ardatan graphql-tools |
Thu, 05 Nov 2026 20:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | GraphQL Tools: Prototype pollution in mergeIncrementalResult via non-primitive path segments | |
| Weaknesses | CWE-1321 | |
| References |
|
|
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-11-05T20:37:39.814Z
Reserved: 2026-10-21T20:34:25.599Z
Link: CVE-2026-114604
No data.
Status : Awaiting Analysis
Published: 2026-11-05T21:18:37.057
Modified: 2026-11-05T21:18:37.187
Link: CVE-2026-114604
No data.
OpenCVE Enrichment
Updated: 2026-11-05T21:45:05Z
Github GHSA