# CVE-2025-32380: Apollo Router Query Validation Vulnerable to Excessive Resource Consumption via Named Fragment Processing > Attackers can cause denial of service in Apollo Router by submitting queries with deeply nested named fragments, exhausting server resources. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 9 Apr 2025 - **Updated:** 9 Apr 2025 - **Also known as:** GHSA-3j43-9v8v-cp3f ## What is CVE-2025-32380? CVE-2025-32380 is a high-severity denial of service vulnerability in apollographql router, published on 9 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description The Apollo Router Core is a configurable, high-performance graph router written in Rust to run a federated supergraph that uses Apollo Federation 2. A vulnerability in Apollo Router's usage of Apollo Compiler allowed queries with deeply nested and reused named fragments to be prohibitively expensive to validate. This could lead to excessive resource consumption and denial of service. Apollo Router's usage of Apollo Compiler has been updated so that validation logic processes each named fragment only once, preventing redundant traversal. This has been remediated in apollo-router versions 1.61.2 and 2.1.1. Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling) ## Which versions are affected by CVE-2025-32380? 4 open source packages ship an affected version, including apollo-router. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `apollo-router` | crates.io | All versions | 1.61.2 | | `apollo-router` | crates.io | All versions | 1.61.2 | | `apollo-router` | crates.io | From 2.0.0-alpha.0 | 2.1.1 | | `apollo-router` | crates.io | From 2.0.0-alpha.0 | 2.1.1 | ## How do I fix CVE-2025-32380? Upgrade apollo-router to a fixed version for your release line: 1.61.2 or 2.1.1. ## Is CVE-2025-32380 being exploited? There is no known exploitation of CVE-2025-32380 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-32380 and fix it if it is affected. What it is: CVE-2025-32380 is a high-severity denial of service vulnerability in apollographql router, published on 9 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-32380 in the wild and no public exploit code. Affected packages and fixed versions: - apollo-router (crates.io): affected all versions; fixed in 1.61.2 - apollo-router (crates.io): affected all versions; fixed in 1.61.2 - apollo-router (crates.io): affected from 2.0.0-alpha.0; fixed in 2.1.1 - apollo-router (crates.io): affected from 2.0.0-alpha.0; fixed in 2.1.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/CVE-2025-32380/ (Markdown: https://insights.sbomify.com/CVE-2025-32380/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-32380 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-32380 - OSV: https://osv.dev/vulnerability/CVE-2025-32380 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-32380/ Summaries are generated and may contain mistakes; the official description above is the record.