CVE-2026-114604 Ardatan CVE debrief

Who should care

GraphQL API developers and administrators who use `@graphql-tools/utils` versions 10.10.1 through 12.0.1 should assess their exposure and apply patches or updates to prevent potential prototype pollution attacks.

Why it matters

CVE-2026-114604 is a prototype pollution vulnerability in `@graphql-tools/utils` that requires attention from GraphQL API developers and administrators to assess exposure and apply patches.

• Potential security issues due to prototype pollution
• Need to verify and monitor GraphQL API usage for potential attacks
• Priority to apply patches or updates to `@graphql-tools/utils` version 12.0.2 or later

Technical summary

The `mergeIncrementalResult` function in `@graphql-tools/utils` is vulnerable to prototype pollution due to its ability to walk through non-primitive path segments. This allows an attacker to pollute the prototype of an object, potentially leading to security issues. The vulnerability was verified against source code reads at `134d67ae36a559651f43ec7fe4a9da76f4a00c2b` and `master` HEAD `ccca0ff0dc8ea20726fd116b2f19a38709c30e62`, as well as published npm builds 10.10.0, 10.10.1, 11.0.0, 12.0.0, and 12.0.1. GraphQL API developers and administrators should prioritize assessing exposure and applying patches to prevent potential prototype pollution attacks.

Defensive priority

GraphQL API developers and administrators should prioritize assessing exposure and applying patches to prevent potential prototype pollution attacks.

Recommended defensive actions

• Assess exposure of GraphQL APIs using `@graphql-tools/utils` versions 10.10.1 through 12.0.1
• Apply patches or updates to `@graphql-tools/utils` version 12.0.2 or later
• Verify and monitor GraphQL API usage for potential prototype pollution attacks
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability was verified against source code reads at `134d67ae36a559651f43ec7fe4a9da76f4a00c2b` and `master` HEAD `ccca0ff0dc8ea20726fd116b2f19a38709c30e62`, as well as published npm builds 10.10.0, 10.10.1, 11.0.0, 12.0.0, and 12.0.1.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.