# GHSA-9q82-xgwf-vj6h: Apollo Server: Browser bug allows for bypass of XS-Search (read-only Cross-Site Request Forgery) prevention

> A browser bug allows attackers to bypass Apollo Server's CSRF protection, enabling XS-Search attacks to infer data from GraphQL queries.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 26 Mar 2026

## What is GHSA-9q82-xgwf-vj6h?

GHSA-9q82-xgwf-vj6h is a vulnerability in @apollo/server, published on 26 Mar 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### 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, an 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 Server 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 Server's docs](https://www.apollographql.com/docs/apollo-server/security/cors) for more details on CORS, CSRF attacks, and Apollo Server'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 Server's CSRF prevention feature **blocks** "side effect" CSRF attacks: Apollo Server 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.

GraphQL servers are only vulnerable if they rely on cookies (or HTTP Basic Auth) for authentication.

## Patches

The vulnerability is patched in `@apollo/server` v5.5.0. This release contains 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 use case, [file an issue](https://github.com/apollographql/apollo-server/issues) and more configurability can be added.

Apollo is not currently providing a patch for previous major versions of Apollo Server, which are all [end-of-life](https://www.apollographql.com/docs/apollo-server/previous-versions).

### 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 Apollo Server (e.g. in a proxy or middleware).

For example, when using Apollo Server's Express integration, something like this can be placed *before* attaching `expressMiddleware` to the `app`:

```js
app.use((req, res, next) => {
  for (let i = 0; i < req.rawHeaders.length - 1; i += 2) {
    if (
      req.rawHeaders[i].toLowerCase() === 'content-type' &&
      req.rawHeaders[i + 1].includes('message/')
    ) {
      return res.status(415).json({ error: 'Content-Type not allowed' });
    }
  }
  next();
});
```

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 system is not currently vulnerable. Upgrading to the latest version of Apollo Server is still recommended for the broader protection.

## Resources

The browser bug causes a similar vulnerability in Apollo Router; see https://github.com/apollographql/router/security/advisories/GHSA-hff2-gcpx-8f4p

## Which versions are affected by GHSA-9q82-xgwf-vj6h?

4 open source packages ship an affected version, including @apollo/server and apollo-server-core.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@apollo/server` | npm | All versions | 5.5.0 |
| `@apollo/server` | npm | All versions | 5.5.0 |
| `apollo-server-core` | npm | All versions to 3.13.0 | None |
| `apollo-server-core` | npm | All versions to 3.13.0 | None |

## How do I fix GHSA-9q82-xgwf-vj6h?

Upgrade @apollo/server to 5.5.0 or later.

## Is GHSA-9q82-xgwf-vj6h being exploited?

There is no known exploitation of GHSA-9q82-xgwf-vj6h in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-9q82-xgwf-vj6h and fix it if it is affected.

What it is: GHSA-9q82-xgwf-vj6h is a vulnerability in @apollo/server, published on 26 Mar 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of GHSA-9q82-xgwf-vj6h in the wild and no public exploit code.

Affected packages and fixed versions:
- @apollo/server (npm): affected all versions; fixed in 5.5.0
- @apollo/server (npm): affected all versions; fixed in 5.5.0
- apollo-server-core (npm): affected all versions up to 3.13.0; no fix listed
- apollo-server-core (npm): affected all versions up to 3.13.0; no fix listed

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-9q82-xgwf-vj6h/ (Markdown: https://insights.sbomify.com/GHSA-9q82-xgwf-vj6h/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-9q82-xgwf-vj6h

---
From sbomify Insights: https://insights.sbomify.com/GHSA-9q82-xgwf-vj6h/
Summaries are generated and may contain mistakes; the official description above is the record.