CVE-2025-64347: Apollo Router Improperly Enforces Renamed Access Control Directives
Summary A vulnerability in Apollo Router allowed for 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.
Published Nov 6, 2025 · Updated Nov 7, 2025
Affected packages
apollo-router
- Ecosystem
- Rust (crates.io)
- Affected
- < 1.61.12
- Fixed in
- 1.61.12
- Check
cargo tree -i apollo-router
apollo-router
- Ecosystem
- Rust (crates.io)
- Affected
- >= 2.0.0-alpha.0, < 2.8.1
- Fixed in
- 2.8.1
- Check
cargo tree -i apollo-router
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
A vulnerability in Apollo Router allowed for 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.
Details
Apollo Federation allows users to specify access control directives (@authenticated, @requiresScopes, and @policy](https://www.apollographql.com/docs/graphos/routing/security/authorization#authorization-directives)) to protect schema data access at the element level. These directives can optionally be renamed via the `imports` argument to the `@link` directive, which can be useful if their default names match an existing user-defined directive in their subgraph schema. However, Apollo Router's access control logic ignored the imports argument, and would accordingly ignore access control directives that were renamed in this way.
Who Is Impacted
This vulnerability impacts Apollo Router customers defining @authenticated, @requiresScopes, or @policy directives on schema elements that were renamed via @link imports are impacted.
Scope of Impact
The vulnerability could allow a malicious actor to craft a query that can bypass access control requirements on schema elements protected by renamed access control directives.
Patches
This vulnerability has been fixed in Apollo Router by updating the access control logic to handle the imports argument in @link directives. You will need to update Router to one of the following versions:
- 1.61.12+
- 2.8.1+
Workarounds
- If you are not immediately updating Router to a patched version, you should remove any renames of access control directives in the
importsargument to the@linkdirective. - Customers not using Apollo Router with renamed access control directives (
@authenticated,@requiresScopes, and@policy) are not affected and do not need to take action.
Credited to sachindshinde.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Rust (crates.io) vulnerabilities
All Rust (crates.io) entriesGHSA-hff2-gcpx-8f4p
Apollo Router Core: Browser Bug Enables Bypass of XS-Search Prevention via Read-Only Cross-Site Request Forgery
medium6.3Mar 26, 2026CVE-2025-64173
Apollo Router Affected by an Access Control Bypass on Polymorphic Types
high7.5Nov 6, 2025CVE-2025-32032
Apollo Router Query Planner Vulnerable to Excessive Resource Consumption via Optimization Bypass
high7.5Apr 7, 2025CVE-2025-32033
Apollo Router Operation Limits Vulnerable to Bypass via Integer Overflow
high7.5Apr 7, 2025CVE-2025-32034
Apollo Router Query Planner Vulnerable to Excessive Resource Consumption via Named Fragment Expansion
high7.5Apr 7, 2025CVE-2025-32380
Apollo Router Query Validation Vulnerable to Excessive Resource Consumption via Named Fragment Processing
high7.5Apr 7, 2025
