CVE-2026-32621: Apollo Federation

Patch now - CVE-2026-32621 is a critical prototype pollution in Apollo Gateway versions before 2.9.6, 2.10.5, 2.11.6, 2.12.3, and 2.13.2 that lets attackers crash the gateway, alter application behavior, or execute remote code with a CVSS 9.9 severity. Update to the patched versions immediately.

Overview

A critical security vulnerability, identified as CVE-2026-32621, has been discovered in Apollo Federation, a popular architecture for building a unified GraphQL API from multiple subgraphs. This flaw resides in the query plan execution logic of the Apollo Gateway. If exploited, it allows an attacker to pollute the base Object.prototype in the gateway’s JavaScript environment, which can lead to severe consequences including denial of service, unexpected application behavior, or potentially remote code execution.

Vulnerability Details

The vulnerability is a form of prototype pollution. In simple terms, it allows an attacker to inject properties into fundamental JavaScript objects that are inherited by all other objects. This can corrupt the application’s logic and state.

Exploitation can occur through two primary vectors:

1. Direct Client Attack: A malicious client can send a specially crafted GraphQL operation (query or mutation) containing field aliases or variable names designed to target inheritable properties on the Object.prototype.
2. Compromised Subgraph Attack: If a federated subgraph is compromised, a malicious actor controlling that subgraph can craft JSON response payloads that, when processed by the gateway, achieve the same prototype pollution effect.

Impact

With a CVSS score of 9.9 (CRITICAL), this vulnerability poses a significant risk. Successful exploitation could allow an attacker to:

• Crash the Apollo Gateway, causing a denial of service for your entire GraphQL API.
• Alter the application’s behavior in unpredictable ways, potentially bypassing security controls or business logic.
• In worst-case scenarios, prototype pollution can be a stepping stone to remote code execution, granting the attacker control over the gateway server.

This flaw highlights how a breach in one subgraph can threaten the integrity of the entire federated graph, similar to risks seen in other ecosystems where a single compromised component can have widespread effects, as seen in recent iOS exploit chains.

Remediation and Mitigation

The only complete remediation is to update the Apollo Gateway to a patched version.

Immediate Action Required: Update your Apollo Gateway to one of the following secure versions:

• Version 2.9.6
• Version 2.10.5
• Version 2.11.6
• Version 2.12.3
• Version 2.13.2

Mitigation Steps (If Immediate Patching is Not Possible):

1. Review Subgraph Security: Strictly audit and monitor the security of all subgraphs in your federation. Treat each as a potential attack vector into the gateway.
2. Input Validation: Implement rigorous input validation and sanitization at the gateway level for incoming GraphQL operations. However, this is a complex mitigation and not a substitute for patching.
3. Network Controls: Restrict access to the GraphQL gateway endpoint as much as possible using network firewalls or API gateways.

Organizations should treat this update with the highest priority, akin to the urgency of critical platform patches. Apply the update in your development and testing environments first, then proceed to production following your standard change management procedures.