GHSA-hff2-gcpx-8f4p: Apollo Router Core Browser Bug Enables Bypass Of Vulnerability

MODERATE
CWE-200
Published
Advisory Summary

GHSA-hff2-gcpx-8f4p is a MODERATE browser bug enables bypass of vulnerability (CWE-200: Exposure of Sensitive Information to an Unauthorized Actor) affecting Apollo Router Core libraries in the crates.io ecosystem. The issue involves browser bug enables bypass of xs-search prevention via read-only cross-site request forgery. Remediation is available by upgrading affected packages to version 2.12.1, 2.10.2, 1.61.13.

GHSA-hff2-gcpx-8f4p at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-hff2-gcpx-8f4p
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Affected Product Apollo Router Core
Package Ecosystem crates.io
Published Date
Last Updated

How to Fix GHSA-hff2-gcpx-8f4p

To remediate this vulnerability, upgrade all affected Apollo Router Core dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

apollo-router fixed: 2.12.1
Upgrade apollo-router to 2.12.1
apollo-router fixed: 2.10.2
Upgrade apollo-router to 2.10.2
apollo-router fixed: 1.61.13
Upgrade apollo-router to 1.61.13
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for apollo-router

How to Check if You Are Affected

To determine whether your application is affected by GHSA-hff2-gcpx-8f4p, inspect your project dependencies for Apollo Router Core:

inspect dependencies for apollo-router

Analyze the terminal output to locate any version of Apollo Router Core in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.12.1), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor, where the product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. In Apollo Router Core, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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

GHSA-hff2-gcpx-8f4p Affected Apollo Router Core Versions

3 component(s)
Fixed Versions:
2.12.12.10.21.61.13
Product / Package Ecosystem Affected Versions Fixed Version
apollo-router
crates.io
≥ 2.11.0
< 2.12.1
2.12.1
apollo-router
crates.io
≥ 2.0.0
< 2.10.2
2.10.2
apollo-router
crates.io
< 1.61.13
1.61.13

References

Frequently Asked Questions

What is GHSA-hff2-gcpx-8f4p?
GHSA-hff2-gcpx-8f4p is a security vulnerability in Apollo Router Core involving Browser Bug Enables Bypass of XS-Search Prevention via Read-Only Cross-Site Request Forgery under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor.
Which Apollo Router Core versions are affected?
Affected versions include releases prior to 2.12.1, 2.10.2, 1.61.13 across affected packages: apollo-router.
What version fixes GHSA-hff2-gcpx-8f4p?
Upgrading to 2.12.1, 2.10.2, 1.61.13 (or the latest patched release for your respective branch) resolves the vulnerability.
Is apollo-router affected?
Yes, apollo-router is affected in releases prior to 2.12.1, 2.10.2, 1.61.13. Upgrade your dependency to 2.12.1, 2.10.2, 1.61.13 or later.
What CWE is associated with GHSA-hff2-gcpx-8f4p?
GHSA-hff2-gcpx-8f4p is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor (The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.).
How can I check crates.io dependencies for GHSA-hff2-gcpx-8f4p?
Run the dependency tree command: 'inspect dependencies for apollo-router'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-hff2-gcpx-8f4p",
  "modified" : "2026-03-26T22:09:01Z",
  "published" : "2026-03-26T22:09:01Z",
  "aliases" : [ ],
  "summary" : "Apollo Router Core: Browser Bug Enables Bypass of XS-Search Prevention via Read-Only Cross-Site Request Forgery",
  "details" : "### Impact\nIn 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).\n\nApollo 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.\n\nThis 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.\n\nEven 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.\n\nApollo Router installations are only vulnerable if they rely on cookies (or HTTP Basic Auth) for authentication.\n\n### Patches\nThe vulnerability is patched in the following versions of Apollo Router:\n\n- 2.12.1 (latest)\n- 2.10.2 (v2.10 LTS)\n- 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))\n\nThese 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.\n\nThere 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.\n\n#### Workarounds\nIf 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).\n\nIf the load balancer cannot easily be updated to block these requests, it can also be done with a Rhai script within Router:\n\n```\n# config.yaml\nrhai:\n  scripts: \"/directory/with/rhai/script\"\n  main: \"main.rhai\"\n\n# main.rhai\nfn router_service(service) {\n    const request_callback = Fn(\"process_request\");\n    service.map_request(request_callback);\n}\n\nfn process_request(request) {\n    if \"content-type\" in request.headers {\n        if request.headers[\"content-type\"].contains(\"message/\") {\n            throw \"Error: invalid content type\"\n        }\n    }\n}\n```\n\nWhile 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.\n\n### Resources\nThe browser bug causes a similar vulnerability in Apollo Server; see https://github.com/apollographql/apollo-server/security/advisories/GHSA-9q82-xgwf-vj",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "apollo-router"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.11.0"
      }, {
        "fixed" : "2.12.1"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "apollo-router"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.0.0"
      }, {
        "fixed" : "2.10.2"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "apollo-router"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.61.13"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/apollographql/apollo-server/security/advisories/GHSA-9q82-xgwf-vj6h"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/apollographql/router/security/advisories/GHSA-hff2-gcpx-8f4p"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/apollographql/router/commit/a72e759bcdeef93fcd3dc928cf3c1f4bbebdcc65"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/apollographql/router"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/apollographql/router/releases/tag/v2.12.1"
  }, {
    "type" : "WEB",
    "url" : "https://www.apollographql.com/docs/graphos/resources/runtime-release-lifecycle#end-of-support-eos"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-200" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-26T22:09:01Z",
    "nvd_published_at" : null
  }
}