Advisories
This weekExploitable · Confirmed

@graphql-tools/utils: GraphQL Tools: Prototype pollution in mergeIncrementalResult via non-primitive path segments

There is evidence it can be used, or an emergency alert, without the proof that makes it urgent.

Does it affect what I run?

@graphql-tools/utils (npm)

Checked in your browser. The version you type is not sent anywhere.

Who is affected

  • @graphql-tools/utils (npm): from 10.10.1, before 12.0.2

The fix

  • @graphql-tools/utils (npm) fixed in 12.0.2

    npm
    npm install "@graphql-tools/utils@12.0.2"
    pnpm
    pnpm add "@graphql-tools/utils@12.0.2"
    yarn
    yarn add "@graphql-tools/utils@12.0.2"
    bun
    bun add "@graphql-tools/utils@12.0.2"
    Check what is installed
    npm ls @graphql-tools/utils
    Paste into Cursor, Lovable or Claude Code
    Upgrade the npm dependency @graphql-tools/utils to 12.0.2 or the nearest later release, to fix CVE-2026-114604. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.

Fix commands generated from the advisory's versions. No model wrote them.

In plain words

Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.

Evidence

Timeline

  1. First published here, as "For your digest".
  2. Level changed from "For your digest" to "This week".
  3. Evidence added: CISA's assessment in the CVE record says a proof of concept is public. (CISA Vulnrichment (SSVC and KEV fields inside CVE records))