Summary
Workarounds
A fully effective workaround is not available without a code change. As an interim measure, users who are unable to upgrade immediately may consider placing an input validation layer in front of the gateway to filter operations containing GraphQL names matching known Object.prototype pollution patterns (e.g., __proto__, constructor, prototype). Users should also ensure that subgraphs in their federated graph originate from trusted sources.
Impact
A vulnerability exists in query plan execution within the gateway that may allow pollution of Object.prototype in certain scenarios. A malicious client may be able to pollute Object.prototype in gateway directly by crafting operations with field aliases and/or variable names that target prototype-inheritable properties. Alternatively, if a subgraph were to be compromised by a malicious actor, they may be able to pollute Object.prototype in gateway by crafting JSON response payloads that target prototype-inheritable properties.
Because Object.prototype is shared across the Node.js process, successful exploitation can affect subsequent requests to the gateway instance. This may result in unexpected application behavior, privilege escalation, data integrity issues, or other security impact depending on how polluted properties are subsequently consumed by the application or its dependencies. As of the date of this advisory, Apollo is not aware of any reported exploitation of this vulnerability.
CVE-2026-32621 has a CVSS score of 9.9 (Critical). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.9.6, 2.10.5, 2.11.6, 2.12.3, 2.13.2); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Mitigations addressing prototype pollution exposure have been applied in @apollo/federation-internals, @apollo/gateway, and @apollo/query-planner versions 2.9.6, 2.10.5, 2.11.6, 2.12.3, and 2.13.2. Users are encouraged to upgrade to these versions or later at their earliest convenience.
Frequently Asked Questions
- What is CVE-2026-32621? CVE-2026-32621 is a critical-severity security vulnerability in @apollo/federation-internals (npm), affecting versions < 2.9.6. It is fixed in 2.9.6, 2.10.5, 2.11.6, 2.12.3, 2.13.2.
- How severe is CVE-2026-32621? CVE-2026-32621 has a CVSS score of 9.9 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which packages are affected by CVE-2026-32621?
@apollo/federation-internals(npm) (versions < 2.9.6)@apollo/gateway(npm) (versions < 2.9.6)@apollo/query-planner(npm) (versions < 2.9.6)
- Is there a fix for CVE-2026-32621? Yes. CVE-2026-32621 is fixed in 2.9.6, 2.10.5, 2.11.6, 2.12.3, 2.13.2. Upgrade to this version or later.
- Is CVE-2026-32621 exploitable, and should I be worried? Whether CVE-2026-32621 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-32621 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-32621?
- Upgrade
@apollo/federation-internalsto 2.9.6 or later - Upgrade
@apollo/federation-internalsto 2.10.5 or later - Upgrade
@apollo/federation-internalsto 2.11.6 or later - Upgrade
@apollo/federation-internalsto 2.12.3 or later - Upgrade
@apollo/federation-internalsto 2.13.2 or later - Upgrade
@apollo/gatewayto 2.9.6 or later - Upgrade
@apollo/gatewayto 2.10.5 or later - Upgrade
@apollo/gatewayto 2.11.6 or later - Upgrade
@apollo/gatewayto 2.12.3 or later - Upgrade
@apollo/gatewayto 2.13.2 or later - Upgrade
@apollo/query-plannerto 2.9.6 or later - Upgrade
@apollo/query-plannerto 2.10.5 or later - Upgrade
@apollo/query-plannerto 2.11.6 or later - Upgrade
@apollo/query-plannerto 2.12.3 or later - Upgrade
@apollo/query-plannerto 2.13.2 or later
- Upgrade