# Apollo Router Query Validation Vulnerable to Excessive Resource Consumption via Named Fragment Processing

Advisory record · `GHSA-3j43-9v8v-cp3f`

- **Identifiers:** `GHSA-3j43-9v8v-cp3f` · `CVE-2025-32380`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-770](https://cwe.mitre.org/data/definitions/770.html)
- **Tags:** [Denial of service](https://agentprime.io/advisories/tag/dos.md)
- **Published:** 7 Apr 2025
- **Updated:** 9 Apr 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 7 Apr 2025, 19:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `apollo-router` (crates.io): affected `<1.61.2 || >=2.0.0-alpha.0, <2.1.1`; fixed in `1.61.2`, `2.1.1`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Apollo Router versions before 1.61.2 and from 2.0.0-alpha.0 before 2.1.1 are vulnerable. A remote attacker who can send GraphQL queries with deeply nested, reused named fragments can cause excessive resource consumption during query validation, leading to denial of service. Upgrade to apollo-router 1.61.2 or 2.1.1. The only known workaround is limiting clients to persisted queries by ID, not freeform queries.

Written 8 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0058, the 48th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:20 UTC: First seen by agentprime
- 31 Oct 2026, 15:20 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-3j43-9v8v-cp3f)

## Sources

- [GitHub Advisory Database: GHSA-3j43-9v8v-cp3f](https://github.com/advisories/GHSA-3j43-9v8v-cp3f)
- [OSV: GHSA-3j43-9v8v-cp3f](https://osv.dev/vulnerability/GHSA-3j43-9v8v-cp3f)
- <https://github.com/apollographql/router/security/advisories/GHSA-3j43-9v8v-cp3f>
- <https://nvd.nist.gov/vuln/detail/CVE-2025-32380>
- <https://github.com/apollographql/router/commit/ab6675a63174715ea6ff50881fc957831d4e9564>
- <https://github.com/apollographql/router/commit/bba032e183b861348a466d3123c7137a1ae18952>
- <https://github.com/apollographql/router>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-3j43-9v8v-cp3f>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-3j43-9v8v-cp3f/>. Everything for agents: <https://agentprime.io/llms.txt>.
