CVE-2026-32621
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedApollo Federation is an architecture for declaratively composing APIs into a unified graph. Prior to 2.9.6, 2.10.5, 2.11.6, 2.12.3, and 2.13.2, 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. This vulnerability is fixed in 2.9.6, 2.10.5, 2.11.6, 2.12.3, and 2.13.2.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceApollo Federation gateway contains a prototype pollution vulnerability in its query plan execution. Attackers can pollute Object.prototype either by sending malicious GraphQL operations with specially crafted field aliases/variable names targeting prototype-inheritable properties, or by compromising a subgraph to return malicious JSON responses with prototype-targeting property names.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Apollo Federation gateway versionRun `npm list @apollo/gateway` or check package.json for the installed version of @apollo/gateway. If using a container, check the image tags or Dockerfile. For Java deployments, check the classpath for apollo-gateway JAR versions.Affected if The installed version is earlier than 2.9.6, 2.10.5, 2.11.6, 2.12.3, or 2.13.2 (or falls between these patch releases)
-
Confirm gateway accepts GraphQL operations from untrusted sourcesReview the gateway configuration and network exposure. Check if the GraphQL endpoint is publicly accessible or accepts operations from clients outside your trusted network. Inspect any API gateway or authentication layer in front of the Apollo gateway.Affected if The gateway endpoint is reachable by untrusted clients or lacks strict authentication/authorization on the GraphQL endpoint
-
Assess subgraph trust boundaryReview the list of subgraphs registered with the federation gateway. Check the configuration for subgraph URLs in the gateway setup (often in index.ts or gateway.ts). Determine if any subgraphs are operated by third parties or reside outside your trusted infrastructure.Affected if Any registered subgraph is operated by untrusted parties or could be compromised
-
Audit recent GraphQL operation logs for suspicious aliasesExamine GraphQL access logs or query logs for operations containing field aliases that resemble JavaScript property names such as __proto__, constructor, or prototype, or unusual variable names that could attempt prototype pollution.Affected if Log analysis reveals GraphQL operations with suspicious field aliases targeting prototype-inheritable properties
You are affected if your Apollo Federation gateway version is unpatched (below 2.9.6/2.10.5/2.11.6/2.12.3/2.13.2) AND the gateway processes GraphQL operations from untrusted clients or connects to untrusted subgraphs.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Apollo Federation gateway to version 2.9.6, 2.10.5, 2.11.6, 2.12.3, or 2.13.2 or later. Additionally, implement input validation to reject field aliases and variable names that target prototype-inheritable properties (__proto__, constructor, prototype).
Upgrade @apollo/gateway to 2.13.2 (or 2.9.6, 2.10.5, 2.11.6, 2.12.3 depending on your release line)
- 1. Identify the current Apollo Federation gateway version by checking package.json or running npm list @apollo/gateway (or equivalent package manager command)
- 2. Determine which release line (2.9.x, 2.10.x, 2.11.x, 2.12.x, or 2.13.x) is appropriate for your environment based on your current major/minor version
- 3. Upgrade the @apollo/gateway package to version 2.13.2 (or the corresponding patch for your minor version: 2.9.6, 2.10.5, 2.11.6, or 2.12.3)
- 4. Run npm install or yarn install to install the updated package
- 5. Test the gateway to ensure query plan execution functions correctly
- 6. Verify that the vulnerability is mitigated by confirming Object.prototype is no longer polluted by field aliases or subgraph responses
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,864.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32621 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-32621 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data