Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.4amended

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

CVE-2026-114604GHSA-c4qx-w738-7hr3

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@graphql-tools/utils 12.0.2), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
8.4 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:H/VA:H/SC:N/SI:N/SA:N · score source
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Report metadata | Field | Value | | --- | --- | | Package | @graphql-tools/utils (npm, pkg:github/ardatan/graphql-tools) | | Repository | https://github.com/ardatan/graphql-tools | | Component | mergeIncrementalResult / setObjectKeyPath (packages/utils/src/mergeIncrementalResult.ts) | | Vulnerability class | Prototype pollution (via unvalidated object path traversal) | | Verified against | Source read at 134d67ae36a559651f43ec7fe4a9da76f4a00c2b; master HEAD ccca0ff0dc8ea20726fd116b2f19a38709c30e62; published npm builds 10.10.0, 10.10.1, 11.0.0, 12.0.0, 12.0.1 | | Affected versions | @graphql-tools/utils = 10.10.1 through the scanned 12.0.0 source; introduced by fbb58b51c4993ba9680ce6c2ef7203ab3a142713 ("remove dset dependency"). 12.0.1 also reproduces. 10.10.0 does not. | | API surface | Public, documented export (packages/utils/src/index.ts:55) | | Affected in default configuration | Yes — no options are involved; the forbidden-key check in setObjectKeyPath is the only defense and…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 5 · amended ·

    Amended from ghsa record GHSA-c4qx-w738-7hr3

  2. Revision 4 · amended ·

    Amended from ghsa record GHSA-c4qx-w738-7hr3

  3. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  4. Revision 2 · amended ·

    Amended from osv record GHSA-c4qx-w738-7hr3

  5. Revision 1 · created ·

    Published from ghsa record GHSA-c4qx-w738-7hr3

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-114604

Advisory: GraphQL Tools: Prototype pollution in mergeIncrementalResult via non-primitive path segments
IDs: CVE-2026-114604, GHSA-c4qx-w738-7hr3
Record: https://patchnext.com/advisories/cve-2026-114604 (revision 5, source checked 26 Oct 2026, 13:07 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @graphql-tools/utils 12.0.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @graphql-tools/utils: affected >= 10.10.1, <= 12.0.1; fixed in 12.0.2

## Suggested inspection (read-only)
- `npm ls @graphql-tools/utils --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @graphql-tools/utils.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-c4qx-w738-7hr3 (GitHub-reviewed advisory GHSA-c4qx-w738-7hr3 lists affected ranges: npm @graphql-tools/utils >=10.10.1 <=12.0.1)
- Verified: https://osv.dev/vulnerability/GHSA-c4qx-w738-7hr3 (OSV record GHSA-c4qx-w738-7hr3 lists affected ranges: npm @graphql-tools/utils >=10.10.1 <12.0.2 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…