# GHSA-hff2-gcpx-8f4p: Apollo Router Core: Browser Bug Enables Bypass of XS-Search Prevention via Read-Only Cross-Site Request Forgery - **Severity:** Not scored - **Exploited in the wild:** Not known - **Fix available:** Yes - **Published:** 26 Mar 2026 ## What is GHSA-hff2-gcpx-8f4p? GHSA-hff2-gcpx-8f4p is a vulnerability in apollo-router, published on 26 Mar 2026. ### Official description ### 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 ## Which versions are affected by GHSA-hff2-gcpx-8f4p? 6 open source packages ship an affected version, including apollo-router. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `apollo-router` | crates.io | All versions | 1.61.13 | | `apollo-router` | crates.io | All versions | 1.61.13 | | `apollo-router` | crates.io | From 2.0.0 | 2.10.2 | | `apollo-router` | crates.io | From 2.0.0 | 2.10.2 | | `apollo-router` | crates.io | From 2.11.0 | 2.12.1 | | `apollo-router` | crates.io | From 2.11.0 | 2.12.1 | ## How do I fix GHSA-hff2-gcpx-8f4p? Upgrade apollo-router to a fixed version for your release line: 1.61.13, 2.10.2 or 2.12.1. ## Is GHSA-hff2-gcpx-8f4p being exploited? There is no known exploitation of GHSA-hff2-gcpx-8f4p in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for GHSA-hff2-gcpx-8f4p and fix it if it is affected. What it is: GHSA-hff2-gcpx-8f4p is a vulnerability in apollo-router, published on 26 Mar 2026. Exploitation: There is no known exploitation of GHSA-hff2-gcpx-8f4p in the wild and no public exploit code. Affected packages and fixed versions: - apollo-router (crates.io): affected all versions; fixed in 1.61.13 - apollo-router (crates.io): affected all versions; fixed in 1.61.13 - apollo-router (crates.io): affected from 2.0.0; fixed in 2.10.2 - apollo-router (crates.io): affected from 2.0.0; fixed in 2.10.2 - apollo-router (crates.io): affected from 2.11.0; fixed in 2.12.1 - apollo-router (crates.io): affected from 2.11.0; fixed in 2.12.1 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/GHSA-hff2-gcpx-8f4p/ (Markdown: https://insights.sbomify.com/GHSA-hff2-gcpx-8f4p/index.md) ``` ## Sources - OSV: https://osv.dev/vulnerability/GHSA-hff2-gcpx-8f4p --- From sbomify Insights: https://insights.sbomify.com/GHSA-hff2-gcpx-8f4p/ Summaries are generated and may contain mistakes; the official description above is the record.