CVE-2026-32621 — @apollo/federation-intern…
CRITICALCVE-2026-32621 is a critical-severity (CVSS 9.9) CWE-1321 vulnerability in @apollo/federation-internals. A fix is available for @apollo/federation-internals — see the affected versions and patch details below.
Apollo Federation has prototype pollution via incomplete key sanitization
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-32621.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@apollo/federation-internalsnpmDescription
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.
Patches
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.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @apollo/federation-internals | all versions | 2.9.6npm install @apollo/federation-internals@2.9.6 |
| 📦npm | @apollo/federation-internals | ≥ 2.10.0&&< 2.10.5 | 2.10.5npm install @apollo/federation-internals@2.10.5 |
| 📦npm | @apollo/federation-internals | ≥ 2.11.0&&< 2.11.6 | 2.11.6npm install @apollo/federation-internals@2.11.6 |
| 📦npm | @apollo/federation-internals | ≥ 2.12.0&&< 2.12.3 | 2.12.3npm install @apollo/federation-internals@2.12.3 |
| 📦npm | @apollo/federation-internals | ≥ 2.13.0&&< 2.13.2 | 2.13.2npm install @apollo/federation-internals@2.13.2 |
| 📦npm | @apollo/gateway | all versions | 2.9.6npm install @apollo/gateway@2.9.6 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @apollo/federation-internals, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @apollo/federation-internals to 2.9.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-32621 is resolved across your whole dependency graph.
Workarounds
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.
Frequently Asked Questions
Is CVE-2026-32621 in your dependencies?
Find it across npm, including transitive dependencies.