Vulnerability in @graphql-tools/utils (CVE-2026-104852)
Summary
Vulnerability in @graphql-tools/utils (CVE-2026-104852). Risk of unauthorized operations or information disclosure. Exploitable via constructor. Mitigation: upgrade to 12.0.1 or later.
Original description
The description as published by the source.
Closed by https://github.com/ardatan/graphql-tools/pull/8423
Mitigated in Hive Gateway by https://github.com/graphql-hive/gateway/pull/2600
A client can alias fields to constructor, __proto__ or prototype so that the response keys from two subgraphs collide on those names during result merging. Because mergeDeep recursed through inherited properties, the merge walked {}.constructor to Object, then Object.__proto__ to Function.prototype, and wrote a subgraph-supplied value over Function.prototype.call, breaking every subsequent request in the process until restart. This is remotely triggerable by an unauthenticated client with a single query against any supergraph that merges an object from two subgraphs, which is the ordinary @shareable or entity case, so it is a denial of service rather than a theoretical hardening issue.
{
shared {
fieldA
constructor: fieldB {
__proto__: child {
call: value
}
}
}
}
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-104852 has been found in @graphql-tools/utils.
Attackers can target a specific entry point like constructor over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade @graphql-tools/utils to 12.0.1 or later.
If unsure, ask your IT team or search "@graphql-tools/utils CVE-2026-104852" on the vendor's site.
CVE-2026-104852 (@graphql-tools/utils) — CWE-1321
Attack surface: constructor / __proto__ / prototype / mergeDeep
Patched: 12.0.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-1321) exists in @graphql-tools/utils. Attackers reach the vulnerable code path via constructor.
Check the vendor advisory for the affected versions of @graphql-tools/utils. Attack surface: constructor / __proto__ / prototype / mergeDeep.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 12.0.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@graphql-tools/utils' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@graphql-tools/utils' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@graphql-tools/utilsを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @graphql-tools/utils to 12.0.1ステージング環境で 12.0.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com