Skip to content

GHSA-x33c-7c2v-mrj9 CVE-2025-64173

Apollo Router Affected by an Access Control Bypass on Polymorphic Types

High crates.io
Severity
7.5 / 10
High · CVSS 3.1
Exploit chance (EPSS)
0.34%
Chance of exploitation in the next 30 days. Higher than 27.63% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-288 Authentication Bypass Using an Alternate Path or Channel
Fix
1.61.12
Upgrade apollo-router to this version or later

Description

Summary

A vulnerability in Apollo Router allowed for unauthenticated queries to access data that required additional access controls. Router incorrectly handled access control directives on interface types/fields and their implementing object types/fields, applying them to interface types/fields while ignoring directives on their implementing object types/fields when all implementations had the same requirements.

Details

Apollo Federation allows users to specify access control directives (@authenticated, @requiresScopes, and @policy) to protect object and interface types and fields. However, the GraphQL specification does not define inheritance rules for directives from interfaces to their implementations. Apollo Router will enforce any directives on the interface types/fields but ignore any directives on the implementation object types/fields (as long as all implementations have the same requirements). This inconsistent enforcement behavior leads to unexpected runtime security gaps.

Who is impacted

This vulnerability impacts Apollo Router customers defining @authenticated, @requiresScopes, or @policy directives inconsistently on polymorphic types (i.e., object types that implement interface types). Specifically, if the same access control directives are applied to all implementing types/fields but not on their implemented interface types/fields, they could be impacted.

Scope of Impact

This vulnerability could allow a malicious actor to craft a query that can bypass access control requirements on the object types/fields by instead querying them via implemented interface types/fields that don't have the same access control requirements.

Patches

This vulnerability has been fixed at runtime in Apollo Router. You may 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 apply any included access control requirements to both the appropriate interface types/fields and their implementations.
  • Customers not using Apollo Router access control features (@authenticated, @requiresScopes, or @policy directives) or not specifying inconsistent access control requirements on polymorphic types/fields are not affected and do not need to take action.

Affected versions

crates.io

PackageVulnerableFixed in
apollo-router
< 1.61.12
1.61.12
apollo-router
>= 2.0.0-alpha.0, < 2.8.1
2.8.1

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

apollo-router crates.io → 1.61.12

cargo
cargo update -p apollo-router --precise 1.61.12

Severity breakdown

CVSS 3.1 7.5

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Weakness

CWE-288: Authentication Bypass Using an Alternate Path or Channel

The product requires authentication, but the product has an alternate path or channel that does not require authentication.

How to prevent it
  • Architecture and Design: Funnel all access through a single choke point to simplify how users can access a resource. For every access, perform a check to determine if the user has permissions to access the resource.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-hff2-gcpx-8f4p
Apollo Router Core: Browser Bug Enables Bypass of XS-Search Prevention via Read-Only Cross-Site Request Forgery
Medium Also affects apollo-router
GHSA-g8jh-vg5j-4h3f
Apollo Router Improperly Enforces Renamed Access Control Directives
High Also affects apollo-router
GHSA-3j43-9v8v-cp3f
Apollo Router Query Validation Vulnerable to Excessive Resource Consumption via Named Fragment Processing
High Also affects apollo-router
GHSA-84m6-5m72-45fp
Apollo Router Operation Limits Vulnerable to Bypass via Integer Overflow
High Also affects apollo-router
GHSA-75m2-jhh5-j5g2
Apollo Router Query Planner Vulnerable to Excessive Resource Consumption via Named Fragment Expansion
High Also affects apollo-router
GHSA-94hh-jmq8-2fgp
Apollo Router Query Planner Vulnerable to Excessive Resource Consumption via Optimization Bypass
High Also affects apollo-router
GHSA-x6xq-whh3-gg32
Apollo Router Coprocessors may cause Denial-of-Service when handling request bodies
High Also affects apollo-router
GHSA-fmj9-77q8-g6c4
Apollo Query Planner and Apollo Gateway may infinitely loop on sufficiently complex queries
High Also affects apollo-router
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor