llamaCVEVulnerability Intelligence
/
Advisory · GitHub · crates.io · apollo-router

GHSA-HFF2-GCPX-8F4P

Apollo Router Core: Browser Bug Enables Bypass of XS-Search Prevention via Read-Only Cross-Site Request Forgery

Parche disponible
Descargar PNG JSON
CVSS
—
medium
Fuente: —
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche3 versionesPrimer parche a -2 d de la divulgación
Exposición239 dDesde la divulgación, 26 mar 2026, 5:09 p. m.
Detección235 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 (media) 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.
Tranqui, va para la ventana de mantenimiento.Traje la llave inglesa: esto se arregla.
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada +1
Explotación
Remediación
Parche 1.61.13 +2
Monitoreo
Detectada
24 mar 26
26 mar 26
17 nov 26
21 nov 26
24 mar 26
24 may 26
23 jul 26
22 sept 26
21 nov 26
FechaFaseEventoDetalle
Remediación Parche 1.61.13 apollo-router · -2 d desde divulgación
Remediación Parche 2.10.2 apollo-router · -2 d desde divulgación
Remediación Parche 2.12.1 apollo-router · -2 d desde divulgación
Divulgación Publicada GHSA-HFF2-GCPX-8F4P 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

### Impact
In a Cross-Site Request Forgery attack, untrusted web content causes browsers to send authenticated requests to web servers which use cookies for authentication. While the web content is prevented from reading the request's response due to the Cross-Origin Request Sharing (CORS) protocol, the attacker may be able to cause side effects in the server ("CSRF" attack), or learn something about the response via timing analysis ("XS-Search" attack).

Apollo Router has a built-in feature which prevents CSRF and XS-Search attacks: it refuses to process GraphQL requests that could possibly have been sent by a spec-compliant web browser without a protective "preflight" step. See Apollo Router's docs https://www.apollographql.com/docs/graphos/routing/security/csrf for more details on CORS, CSRF attacks, and Apollo Router's CSRF prevention feature.

This feature is fully effective against attacks carried out against users of spec-compliant browsers. Unfortunately, a major browser introduced a bug in 2025 which meant in certain cases, it failed to follow the CORS spec. The browser's maintainers have already committed to fixing the bug and making the browser spec-compliant again.

Even with this bug, Apollo Router's CSRF prevention feature blocks "side effect" CSRF attacks: Apollo Router will still correctly refuse to execute _mutations_ in requests that were not preflighted. However, some specially crafted authenticated GraphQL _queries_ can be issued across origins *without preflight* in buggy versions of this browser, allowing for XS-Search attacks: an attacker can analyze response times to learn facts about the responses to requests such as whether fields return null or approximately how many list entries are returned from fields.

Apollo Router installations are only vulnerable if they rely on cookies (or HTTP Basic Auth) for authentication.

### Patches
The vulnerability is patched in the following versions of Apollo Router:

  • 2.12.1 (latest)
  • 2.10.2 (v2.10 LTS)
  • 1.61.13 (v1; note that Router v1 reaches end-of-support on March 31 2026 https://www.apollographql.com/docs/graphos/resources/runtime-release-lifecycle#end-of-support-eos)

These releases contain a single change: GraphQL requests sent in HTTP `GET` requests which contain a `Content-Type` header naming a type other than `application/json` are rejected. (`GET` requests with no `Content-Type` are allowed.) This change prevents XS-Search attacks even in browsers which are non-compliant in ways similar to this browser.

There are no known cases where GraphQL apps depend on the ability of clients to send non-empty `Content-Type` headers with GET requests other than `application/json`, so this change has not been made configurable; if this change breaks a specific use case, contact support and more configurability can be added.

#### Workarounds
If upgrading is not possible, this particular browser's bug can be mitigated by preventing any HTTP request with a `Content-Type` header containing `message/` from reaching the Apollo Router (e.g. in a load balancer/proxy).

If the load balancer cannot easily be updated to block these requests, it can also be done with a Rhai script within Router:

# config.yaml
rhai:
  scripts: "/directory/with/rhai/script"
  main: "main.rhai"

# main.rhai
fn router_service(service) {
    const request_callback = Fn("process_request");
    service.map_request(request_callback);
}

fn process_request(request) {
    if "content-type" in request.headers {
        if request.headers["content-type"].contains("message/") {
            throw "Error: invalid content type"
        }
    }
}

While the patch prevents a broader class of similar issues, the only known way to exploit this vulnerability is against a particular browser which currently plans to ship a fix in May 2026. If it is already past June 2026 and this vulnerability has not been addressed yet, it is likely that the installation is not currently vulnerable. Upgrading to the latest version of Apollo Router is still recommended for the broader protection.

### Resources
The browser bug causes a similar vulnerability in Apollo Server; see https://github.com/apollographql/apollo-server/security/advisories/GHSA-9q82-xgwf-vj

Incluye detalles técnicos publicados por el investigador. Úselos solo para validar y corregir sus propios sistemas.

Versiones

Rangos afectados

Afectada Corregida Última
apollo-router< 1.61.13
apollo-router≥ 2.0.0 < 2.10.2
apollo-router≥ 2.11.0 < 2.12.1
1.61.13
2.0.0
2.10.2
2.11.0
2.12.1
2.19.0
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
crates.ioapollo-router
Corregida 1.61.13, 2.10.2, 2.12.1 -2 d · -2 d · -2 d 2.19.0 no afectada
Versiones corregidas1.61.132.10.22.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/apollo-server/security/advisories/GHSA-9q82-xgwf-vj6h
Otrahttps://github.com/apollographql/router/security/advisories/GHSA-hff2-gcpx-8f4p
Otrahttps://github.com/apollographql/router/commit/a72e759bcdeef93fcd3dc928cf3c1f4bbebdcc65
Otrahttps://github.com/apollographql/router
Otrahttps://github.com/apollographql/router/releases/tag/v2.12.1
Otrahttps://www.apollographql.com/docs/graphos/resources/runtime-release-lifecycle#end-of-support-eos

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