Skip to content

Apollo Compiler Named Fragment Processing Vulnerability

High severity GitHub Reviewed Published Apr 7, 2025 in apollographql/apollo-rs • Updated Apr 8, 2025

Package

cargo apollo-compiler (Rust)

Affected versions

< 1.27.0

Patched versions

1.27.0

Description

Impact

Summary

A vulnerability in Apollo Compiler allowed queries with deeply nested and reused named fragments to be prohibitively expensive to validate. This could lead to excessive resource consumption and denial of service in applications.

Details

Named fragments were being processed once per fragment spread in some cases during query validation, leading to exponential resource usage when deeply nested and reused fragments were involved.

Fix/Mitigation

The validation logic has been updated to process each named fragment only once, preventing redundant traversal.

Patches

This has been remediated in apollo-compiler version 1.27.0.

Workarounds

No known direct workarounds exist.

Acknowledgements

We appreciate the efforts of the security community in identifying and improving the performance and security of query validation mechanisms.

References

@jasonbarnett667 jasonbarnett667 published to apollographql/apollo-rs Apr 7, 2025
Published to the GitHub Advisory Database Apr 7, 2025
Reviewed Apr 7, 2025
Published by the National Vulnerability Database Apr 7, 2025
Last updated Apr 8, 2025

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

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

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(18th percentile)

Weaknesses

CVE ID

CVE-2025-31496

GHSA ID

GHSA-7mpv-9xg6-5r79

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.