llamaCVEVulnerability Intelligence
/
Advisory · GitHub · npm · @apollo/composition

GHSA-M8JR-FXQX-8XX6

Apollo Federation has Improper Enforcement of Access Control on Transitive Fields

Parche disponible
Descargar PNG JSON
CVSS
—
high
Fuente: —
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche4 versionesPrimer parche a -1 d de la divulgación
Exposición371 dDesde la divulgación, 14 nov 2025, 4:49 p. m.
Detección367 dDesde la divulgación hasta su ingreso al índice
Decisión estimadaSeguir
Remediar en la ventana regular de mantenimiento
Estimación de Llama con el árbol SSVC de CISA a partir de la severidad declarada por GHSA (alta) y la evidencia de explotación (sin evaluación oficial): sin explotación conocida, no automatizable e impacto técnico parcial. Hay versiones corregidas disponibles.
Que no se te pase entre tantos tickets.Esto amerita una regla de detección, por si acaso.
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada +1
Explotación
Remediación
Parche 2.9.5 +3
Monitoreo
Detectada
13 nov 25
14 nov 25
17 nov 26
21 nov 26
13 nov 25
15 feb 26
19 may 26
20 ago 26
21 nov 26
FechaFaseEventoDetalle
Remediación Parche 2.9.5 @apollo/composition · -1 d desde divulgación
Remediación Parche 2.10.4 @apollo/composition · -1 d desde divulgación
Remediación Parche 2.11.5 @apollo/composition · -1 d desde divulgación
Remediación Parche 2.12.1 @apollo/composition · -1 d desde divulgación
Divulgación Publicada GHSA-M8JR-FXQX-8XX6 divulgada
Divulgación Modificada Última actualización del registro
Monitoreo Detectada Ingresó al índice
Resumen
Descripción del advisory
Texto original · GitHub · en inglés

# Summary
A vulnerability in Apollo Federation's composition logic did not enforce that fields depending on protected data through `@requires` and/or `@fromContext` directives have the same access control requirements as the fields they reference. This allowed queries to access protected fields indirectly through their dependencies, bypassing access control checks. A fix to composition logic in Federation now enforces that dependent fields match the access control requirements from of the fields they reference.

## Details
Apollo Federation allows users to specify `@authenticated`, `@requiresScopes`, and `@policy` directives https://www.apollographql.com/docs/graphos/routing/security/authorization#authorization-directives to protect fields at the field level. The `@requires` directive allows a field to depend on data from other fields in the schema, and `@fromContext` allows a field to use values from the execution context. However, Apollo Router does not enforce access control requirements on these transitively-accessed fields, and Apollo Federation did not require that fields using `@requires` or `@fromContext` have the same access control as the fields they depend on.

At execution time, when a field decorated with `@requires` or `@fromContext` was resolved, the Router would fetch the required dependency fields from subgraphs without checking whether those fields had their own access control requirements. Access control directives applied to these dependency fields were only enforced when those fields appeared explicitly in the query. If the protected fields were accessed solely as transitive dependencies (in other words, fetched to satisfy `@requires` or `@fromContext` but not directly requested) their access control requirements were silently ignored.

This discrepancy between where access controls could be defined (on any field) and where it was enforced (only on explicitly queried fields) leads to unexpected runtime security gaps.

## Who is impacted
This vulnerability impacts Apollo Federation customers with supergraphs defining `@authenticated`, `@requiresScopes`, or `@policy` directives on fields that are also specified as dependencies in `@requires` or `@fromContext` directives.

### Scope of Impact
The vulnerability could allow a malicious actor to craft a query that indirectly accesses protected fields, allowing them to bypass field-level access control. By querying only fields that depend on protected data (via `@requires` or `@fromContext`) without explicitly requesting the protected fields themselves, an attacker could retrieve sensitive information without meeting the access control requirements.

## Patches
This vulnerability has been fixed in Apollo Federation by updating composition logic to validate that access control requirements on `@requires` and `@fromContext` dependency fields match the resolving field's requirements.

_Note that this is a breaking change to Apollo Federation, as it no longer allows fields using `@requires` or `@fromContext` to have different access control directives from the fields they depend on. You will need to update your subgraphs to ensure that the access control requirements on fields using `@requires` or `@fromContext` match the access control directives on the referenced fields._

If you are using the Apollo Studio build pipeline with Federation version 2.9 or above, then this patch version update is automatic and you only need to adjust the access control requirements in your subgraph schemas as mentioned above.

If you are using Apollo Rover for local composition, you will need to update its composition version (after updating Apollo Router, if necessary https://www.apollographql.com/docs/graphos/platform/graph-management/updates#recommended-update-order) to one of the following versions:

  • 2.9.5+
  • 2.10.4+
  • 2.11.5+
  • 2.12.1+

You will then need to adjust the access control requirements in your subgraph schemas as mentioned above.

## Workarounds
- If you are using Apollo Rover with an unpatched composition version or are using the Apollo Studio build pipeline with Federation version 2.8 or below, you should review your schema for any sensitive fields that are accessed via `@requires` or `@fromContext` and explicitly apply matching access control directives on those transitive fields. Alternatively, consider restructuring your schema so that protected fields are queried directly.
* Customers not using Apollo Router access control features (`@authenticated`, `@requiresScopes`, or `@policy` directives) or not using `@requires` or `@fromContext` directives in combination with field-level access control are not affected and do not need to take action.

Versiones

Rangos afectados

Afectada Corregida Última
@apollo/composition< 2.9.5
@apollo/composition≥ 2.10.0-alpha.3 < 2.10.4
@apollo/composition≥ 2.11.0-preview.1 < 2.11.5
@apollo/composition≥ 2.12.0-preview.0 < 2.12.1
2.9.5
2.10.0-alpha.3
2.10.4
2.11.0-preview.1
2.11.5
2.12.0-preview.0
2.12.1
2.14.4
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
npm@apollo/composition
Corregida 2.9.5, 2.10.4, 2.11.5, 2.12.1 -1 d · -1 d · -1 d · -1 d 2.14.4 no afectada
Versiones corregidas2.9.52.10.42.11.52.12.1
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Referencias
Otrahttps://github.com/apollographql/federation/security/advisories/GHSA-m8jr-fxqx-8xx6
Otrahttps://github.com/apollographql/federation/commit/09e596e6a0c753071ca822e84f525d73ada395cf
Otrahttps://github.com/apollographql/federation/commit/0d8fca1c8cc375bb8486f11f339984b69267417d
Otrahttps://github.com/apollographql/federation/commit/20c75d1d60a48fc289d88c8d29652f1afc7553e4
Otrahttps://github.com/apollographql/federation/commit/e1c58611c3c996b4fff98a54e49f00549ff2115d
Otrahttps://github.com/apollographql/federation

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.