CVE-2025-64530: @apollo/composition Remote Code Execution Vulnerability

HIGH
Advisory Identifier: GHSA-mx7m-j9xf-62hw
CVSS 7.5
CWE-284 CWE-288
Published
Advisory Summary

CVE-2025-64530 is a HIGH (CVSS 7.5) remote code execution vulnerability (CWE-284: Improper Access Control) affecting @apollo/composition libraries in the npm ecosystem. The issue involves @apollo/composition has improper enforcement of access control on interface types and fields. Remediation is available by upgrading affected packages to version 2.9.5, 2.10.4, 2.11.5, 2.12.1.

CVE-2025-64530 at a Glance

CVE Identifier CVE-2025-64530
GHSA Identifier GHSA-mx7m-j9xf-62hw
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification CWE-284: Improper Access Control
Affected Product @apollo/composition
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 7.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2025-64530

To remediate this vulnerability, upgrade all affected @apollo/composition dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

@apollo/composition fixed: 2.9.5
npm install @apollo/composition@2.9.5
@apollo/composition fixed: 2.10.4
npm install @apollo/composition@2.10.4
@apollo/composition fixed: 2.11.5
npm install @apollo/composition@2.11.5
@apollo/composition fixed: 2.12.1
npm install @apollo/composition@2.12.1
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls @apollo/composition

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2025-64530, inspect your project dependencies using npm:

npm ls @apollo/composition

Analyze the terminal output to locate any version of @apollo/composition in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.9.5), your application is affected.

Note: The npm ls @apollo/composition command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-284: Improper Access Control, where the product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. In @apollo/composition, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

# Summary A vulnerability in Apollo Federation's composition logic 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 or named fragments. A fix to composition logic in Federation now disallows interfaces types and fields to contain user-defined access control directives. ## 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 object and interface types and fields. However, the GraphQL specification does not define inheritance rules for directives from interfaces to their implementations. When querying object or interface types/fields, Apollo Router will enforce any directives on those object or interface types/fields, but ignore any directives on interface types/fields they implement. This inconsistent enforcement behavior leads to unexpected runtime security gaps. ## Who is impacted This vulnerability impacts Apollo Federation customers defining `@authenticated`, `@requiresScopes`, or `@policy` directives on interface types/fields. ### Scope of Impact This vulnerability could allow a malicious actor to craft a query that can bypass access control requirements on the interface types/fields by instead querying them via implementing object types/fields that don't have the same access control requirements via inline or named fragments. ## Patches This vulnerability has been fixed in Apollo Federation's composition logic by rejecting user-defined access control directives entirely on interface types and fields (note that access control directives on `@interfaceObject` fields are not rejected, as those are really specifying requirements on the virtual object fields). Instead, Apollo Federation's composition logic will automatically generate access control directives for interface types/fields in the supergraph schema based on the access control directives on the implementations in subgraph schemas. _Note that this is a breaking change to Apollo Federation, as it no longer allows user-defined access control directives directly on interfaces types and fields. You will need to remove all access control requirements on interface types/fields and manually apply them to each implementing object type/field, where appropriate._ If users are using the Apollo Studio build pipeline with federation version 2.9 or above, then this composition patch version update is automatic and they only need to adjust the access control requirements in your subgraph schemas as mentioned above. If users are using Apollo Rover for local composition, they will need to update its composition version (after updating Apollo Router, [if necessary](https://www.apollographql.com/docs/graphos/platform/graph-management/updates#recommended-update-order)) to one of the following versions: - 2.9.5+ - 2.10.4+ - 2.11.5+ - 2.12.1+ Users will then need adjust the access control requirements in your subgraph schemas as mentioned above. ## Workarounds - If using Apollo Rover with an unpatched composition version or are using the Apollo Studio build pipeline with Federation version 2.8 or below, users 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.

CVE-2025-64530 Affected @apollo/composition Versions

4 component(s)
Fixed Versions:
2.9.52.10.42.11.52.12.1
Product / Package Ecosystem Affected Versions Fixed Version
@apollo/composition
npm
< 2.9.5
2.9.5
@apollo/composition
npm
≥ 2.10.0-alpha.3
< 2.10.4
2.10.4
@apollo/composition
npm
≥ 2.11.0-preview.1
< 2.11.5
2.11.5
@apollo/composition
npm
≥ 2.12.0-preview.1
< 2.12.1
2.12.1

References

Frequently Asked Questions

What is CVE-2025-64530?
CVE-2025-64530 is a security vulnerability in @apollo/composition involving @apollo/composition has Improper Enforcement of Access Control on Interface Types and Fields under CWE-284: Improper Access Control.
Which @apollo/composition versions are affected?
Affected versions include releases prior to 2.9.5, 2.10.4, 2.11.5, 2.12.1 across affected packages: @apollo/composition.
What version fixes CVE-2025-64530?
Upgrading to 2.9.5, 2.10.4, 2.11.5, 2.12.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is @apollo/composition affected?
Yes, @apollo/composition is affected in releases prior to 2.9.5, 2.10.4, 2.11.5, 2.12.1. Upgrade your dependency to 2.9.5, 2.10.4, 2.11.5, 2.12.1 or later.
What is the CVSS score of CVE-2025-64530?
CVE-2025-64530 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2025-64530?
CVE-2025-64530 is classified under CWE-284: Improper Access Control (The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.).
How can I check npm dependencies for CVE-2025-64530?
Run the dependency tree command: 'npm ls @apollo/composition'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-mx7m-j9xf-62hw",
  "modified" : "2025-11-14T17:46:55Z",
  "published" : "2025-11-14T17:46:55Z",
  "aliases" : [ "CVE-2025-64530" ],
  "summary" : "@apollo/composition has Improper Enforcement of Access Control on Interface Types and Fields",
  "details" : "# Summary\nA vulnerability in Apollo Federation's composition logic 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 or named fragments. A fix to composition logic in Federation now disallows interfaces types and fields to contain user-defined access control directives.\n\n## Details\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 object and interface types and fields. However, the GraphQL specification does not define inheritance rules for directives from interfaces to their implementations. When querying object or interface types/fields, Apollo Router will enforce any directives on those object or interface types/fields, but ignore any directives on interface types/fields they implement. This inconsistent enforcement behavior leads to unexpected runtime security gaps.\n\n## Who is impacted\nThis vulnerability impacts Apollo Federation customers defining `@authenticated`, `@requiresScopes`, or `@policy` directives on interface types/fields.\n\n### Scope of Impact\nThis vulnerability could allow a malicious actor to craft a query that can bypass access control requirements on the interface types/fields by instead querying them via implementing object types/fields that don't have the same access control requirements via inline or named fragments.\n\n## Patches\nThis vulnerability has been fixed in Apollo Federation's composition logic by rejecting user-defined access control directives entirely on interface types and fields (note that access control directives on `@interfaceObject` fields are not rejected, as those are really specifying requirements on the virtual object fields). Instead, Apollo Federation's composition logic will automatically generate access control directives for interface types/fields in the supergraph schema based on the access control directives on the implementations in subgraph schemas. \n\n_Note that this is a breaking change to Apollo Federation, as it no longer allows user-defined access control directives directly on interfaces types and fields. You will need to remove all access control requirements on interface types/fields and manually apply them to each implementing object type/field, where appropriate._\n\nIf users are using the Apollo Studio build pipeline with federation version 2.9 or above, then this composition patch version update is automatic and they only need to adjust the access control requirements in your subgraph schemas as mentioned above.\n\nIf users are using Apollo Rover for local composition, they will need to update its composition version (after updating Apollo Router, [if necessary](https://www.apollographql.com/docs/graphos/platform/graph-management/updates#recommended-update-order)) to one of the following versions:\n\n- 2.9.5+\n- 2.10.4+\n- 2.11.5+\n- 2.12.1+\n\nUsers will then need adjust the access control requirements in your subgraph schemas as mentioned above.\n\n## Workarounds\n- If using Apollo Rover with an unpatched composition version or are using the Apollo Studio build pipeline with Federation version 2.8 or below, users 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.\n- 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.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@apollo/composition"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.9.5"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@apollo/composition"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.10.0-alpha.3"
      }, {
        "fixed" : "2.10.4"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@apollo/composition"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.11.0-preview.1"
      }, {
        "fixed" : "2.11.5"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@apollo/composition"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.12.0-preview.1"
      }, {
        "fixed" : "2.12.1"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/apollographql/federation/security/advisories/GHSA-mx7m-j9xf-62hw"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-64530"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/apollographql/federation/pull/3340"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/apollographql/federation/pull/3341"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/apollographql/federation/pull/3343"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/apollographql/federation"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-284", "CWE-288" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-11-14T17:46:55Z",
    "nvd_published_at" : "2025-11-13T23:15:49Z"
  }
}