Apollo Federation vulnerable to prototype pollution via incomplete key sanitization
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.
Czego dotyczy
Kliknij technologię, aby zobaczyć wszystkie dotyczące jej podatności.
| Platforma | Paczka | Podatne wersje | Poprawka w wersji |
|---|---|---|---|
| Paczka npm | @apollo/federation-internals | < 2.9.6, >= 2.10.0, < 2.10.5, >= 2.11.0, < 2.11.6, >= 2.12.0, < 2.12.3, >= 2.13.0, < 2.13.2 | 2.9.6, 2.10.5, 2.11.6, 2.12.3, 2.13.2 |
| Paczka npm | @apollo/gateway | < 2.9.6, >= 2.10.0, < 2.10.5, >= 2.11.0, < 2.11.6, >= 2.12.0, < 2.12.3, >= 2.13.0, < 2.13.2 | 2.9.6, 2.10.5, 2.11.6, 2.12.3, 2.13.2 |
| Paczka npm | @apollo/query-planner | < 2.9.6, >= 2.10.0, < 2.10.5, >= 2.11.0, < 2.11.6, >= 2.12.0, < 2.12.3, >= 2.13.0, < 2.13.2 | 2.9.6, 2.10.5, 2.11.6, 2.12.3, 2.13.2 |
Odnośniki
- Wektor CVSS
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L- Słabość (CWE)
CWE-1321- Platforma
- npm
- Paczka
@apollo/federation-internals, @apollo/gateway, @apollo/query-planner- Ujawniono
- 13.03.2026
- Aktualizacja
- 11.10.2026 10:22
Źródła i licencje
OSV / GitHub Advisory Database - GHSA-pfjj-6f4p-rvmh - CC BY 4.0
Historia podatności: @apollo/gateway
Wszystkie opisane podatności tej paczki (Paczka npm), od najnowszej. Widać, czy to jednorazowa wpadka, czy paczka, której trzeba pilnować.
- Wszystkich wpisów
- 5
- Pierwsza → ostatnia
- 06.2019 03.2026
- Bez poprawki
- 0
- Wykorzystywana w atakach
- 0
Rozkład istotności
- Krytyczna 1
- Wysoka 4
Ujawnienia w latach
- 2019: 1
- 2020: 0
- 2021: 0
- 2022: 0
- 2023: 0
- 2024: 1
- 2025: 2
- 2026: 1
-
Apollo Federation vulnerable to prototype pollution via incomplete key sanitization ten wpis
Dowiedz się, które podatności dotyczą Twojej aplikacji
Po podłączeniu integracji DockRay i włączeniu raportowania oprogramowania DockRay porównuje zgłoszone wersje komponentów ze znanymi podatnościami i powiadamia o potwierdzonych dopasowaniach. Zakres zależy od obsługiwanej technologii i dostępnych biuletynów.