# CVE-2025-64347: Apollo Router Improperly Enforces Renamed Access Control Directives > Attackers can bypass access controls on renamed schema elements in Apollo Router, gaining unauthorized read access to protected data. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 7 Nov 2025 - **Updated:** 7 Nov 2025 - **Also known as:** GHSA-g8jh-vg5j-4h3f ## What is CVE-2025-64347? CVE-2025-64347 is a high-severity missing authorization vulnerability in apollographql router, published on 7 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Apollo Router Core is a configurable Rust graph router written to run a federated supergraph using Apollo Federation 2. Versions 1.61.12-rc.0 and below and 2.8.1-rc.0 allow unauthorized access to protected data through schema elements with access control directives (@authenticated, @requiresScopes, and @policy) that were renamed via @link imports. Router did not enforce renamed access control directives on schema elements (e.g. fields and types), allowing queries to bypass those element-level access controls. This issue is fixed in versions 1.61.12 and 2.8.1. Weakness: CWE-284 (Improper Access Control) ## Which versions are affected by CVE-2025-64347? 4 open source packages ship an affected version, including apollo-router. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `apollo-router` | crates.io | All versions | 1.61.12 | | `apollo-router` | crates.io | All versions | 1.61.12 | | `apollo-router` | crates.io | From 2.0.0-alpha.0 | 2.8.1 | | `apollo-router` | crates.io | From 2.0.0-alpha.0 | 2.8.1 | ## How do I fix CVE-2025-64347? Upgrade apollo-router to a fixed version for your release line: 1.61.12 or 2.8.1. ## Is CVE-2025-64347 being exploited? There is no known exploitation of CVE-2025-64347 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-64347 and fix it if it is affected. What it is: CVE-2025-64347 is a high-severity missing authorization vulnerability in apollographql router, published on 7 Nov 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-64347 in the wild and no public exploit code. Affected packages and fixed versions: - apollo-router (crates.io): affected all versions; fixed in 1.61.12 - apollo-router (crates.io): affected all versions; fixed in 1.61.12 - apollo-router (crates.io): affected from 2.0.0-alpha.0; fixed in 2.8.1 - apollo-router (crates.io): affected from 2.0.0-alpha.0; fixed in 2.8.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-64347/ (Markdown: https://insights.sbomify.com/CVE-2025-64347/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-64347 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-64347 - OSV: https://osv.dev/vulnerability/CVE-2025-64347 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-64347/ Summaries are generated and may contain mistakes; the official description above is the record.