{"id":"CVE-2025-64347","aliases":["EUVD-2025-38037","GHSA-g8jh-vg5j-4h3f"],"status":"published","title":"Apollo Router Improperly Enforces Renamed Access Control Directives","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.","severity":{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","level":"high","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-09","score":0.00326,"percentile":0.25892,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-284"],"published":"2025-11-06T15:45:34Z","modified":"2026-10-28T02:30:25Z","fixes":[{"ecosystem":"crates.io","package":"apollo-router","fixed_in":["1.61.12","2.8.1"],"sources":["ghsa","osv"]}],"affected":[{"source":"ghsa","ecosystem":"crates.io","package":"apollo-router","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.61.12"}]}]},{"source":"ghsa","ecosystem":"crates.io","package":"apollo-router","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.0.0-alpha.0"},{"fixed":"2.8.1"}]}]},{"source":"osv","ecosystem":"crates.io","package":"apollo-router","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.61.12"}]}]},{"source":"osv","ecosystem":"crates.io","package":"apollo-router","ranges":[{"type":"SEMVER","events":[{"introduced":"2.0.0-alpha.0"},{"fixed":"2.8.1"}]}]}],"products":[{"vendor":"apollographql","product":"router"},{"vendor":"asus","product":"router"}],"references":[{"url":"https://github.com/apollographql/router/security/advisories/GHSA-g8jh-vg5j-4h3f","tags":["x_refsource_CONFIRM","advisory","web"]},{"url":"https://github.com/apollographql/router/commit/78e4b20a2fc26cc5f141aa47992ed85375266a2b","tags":["x_refsource_MISC","fix","web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-64347","tags":["advisory"]},{"url":"https://github.com/advisories/GHSA-g8jh-vg5j-4h3f"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/64xxx/CVE-2025-64347.json","tags":["advisory"]},{"url":"https://github.com/apollographql/router","tags":["package"]}],"sources":{"cve":[{"id":"CVE-2025-64347","title":"Apollo Router Improperly Enforces Renamed Access Control Directives","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.","status":"published","published":"2025-11-07T17:47:28.36Z","modified":"2025-11-07T18:25:59.775Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","level":"high","assessor":"cna"}],"cwes":["CWE-284"],"updated_at":"2026-11-02T14:32:46.750177Z"}],"euvd":[{"id":"EUVD-2025-38037","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.","status":"published","published":"2025-11-07T17:47:28Z","modified":"2025-11-07T18:25:59Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","level":"high"}],"updated_at":"2026-11-02T19:49:19.321345Z"}],"ghsa":[{"id":"GHSA-g8jh-vg5j-4h3f","title":"Apollo Router Improperly Enforces Renamed Access Control Directives","description":"# Summary \nA 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.\n\n## Details\n\nApollo 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](https://www.apollographql.com/docs/graphos/schema-design/federated-schemas/reference/directives#renaming-directives), 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.\n\n## Who Is Impacted\n\nThis vulnerability impacts Apollo Router customers defining `@authenticated`, `@requiresScopes`, or `@policy` directives on schema elements that were renamed via `@link` imports are impacted.\n\n### Scope of Impact\n\nThe 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.\n\n## Patches\n\nThis 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:\n\n- 1.61.12+\n- 2.8.1+\n\n## Workarounds\n\n- If you are not immediately updating Router to a patched version, you should remove any renames of access control directives in the `imports` argument to the `@link` directive.\n- Customers not using Apollo Router with renamed access control directives (`@authenticated`, `@requiresScopes`, and `@policy`) are not affected and do not need to take action.","status":"published","published":"2025-11-06T15:45:34Z","modified":"2025-11-07T20:31:54Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","level":"high"}],"cwes":["CWE-284"],"updated_at":"2026-11-02T14:39:07.985215Z"}],"nvd":[{"id":"CVE-2025-64347","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.","status":"published","published":"2025-11-07T18:15:37.313Z","modified":"2026-06-17T09:54:15.037Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","level":"high","assessor":"secondary"}],"cwes":["CWE-284"],"updated_at":"2026-11-02T14:11:42.870953Z"}],"osv":[{"id":"CVE-2025-64347","title":"Apollo Router Improperly Enforces Renamed Access Control Directives","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.","status":"published","published":"2025-11-07T17:47:28.36Z","modified":"2026-10-28T02:30:25.087106645Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","level":"high"}],"cwes":["CWE-284"],"updated_at":"2026-11-02T15:44:51.851511Z"},{"id":"GHSA-g8jh-vg5j-4h3f","title":"Apollo Router Improperly Enforces Renamed Access Control Directives","description":"# Summary \nA 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.\n\n## Details\n\nApollo 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](https://www.apollographql.com/docs/graphos/schema-design/federated-schemas/reference/directives#renaming-directives), 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.\n\n## Who Is Impacted\n\nThis vulnerability impacts Apollo Router customers defining `@authenticated`, `@requiresScopes`, or `@policy` directives on schema elements that were renamed via `@link` imports are impacted.\n\n### Scope of Impact\n\nThe 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.\n\n## Patches\n\nThis 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:\n\n- 1.61.12+\n- 2.8.1+\n\n## Workarounds\n\n- If you are not immediately updating Router to a patched version, you should remove any renames of access control directives in the `imports` argument to the `@link` directive.\n- Customers not using Apollo Router with renamed access control directives (`@authenticated`, `@requiresScopes`, and `@policy`) are not affected and do not need to take action.","status":"published","published":"2025-11-06T15:45:34Z","modified":"2025-11-07T20:31:54Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","level":"high"}],"cwes":["CWE-284"],"updated_at":"2026-11-02T15:46:47.472172Z"}]}}