Bug 2567593 (CVE-2026-114604) - CVE-2026-114604 @graphql-tools/utils: @graphql-tools/utils: Prototype pollution via unvalidated incremental response path segments
Summary: CVE-2026-114604 @graphql-tools/utils: @graphql-tools/utils: Prototype polluti...
Keywords:
Status: NEW
Alias: CVE-2026-114604
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-11-05 22:10 UTC by OSIDB Bzimport
Modified: 2026-11-05 23:36 UTC (History)
35 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-11-05 22:10:36 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.