How severe is GHSA-7mpv-9xg6-5r79?

GHSA-7mpv-9xg6-5r79 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-7mpv-9xg6-5r79?

GHSA-7mpv-9xg6-5r79 affects the following packages: apollo-compiler (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-7mpv-9xg6-5r79?

Update apollo-compiler to 1.27.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7mpv-9xg6-5r79 is resolved across your whole dependency graph.

How do I detect GHSA-7mpv-9xg6-5r79 in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for apollo-compiler, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-7mpv-9xg6-5r79 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is GHSA-7mpv-9xg6-5r79 actively exploited in the wild?

No public exploit code has been indexed for GHSA-7mpv-9xg6-5r79 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-7mpv-9xg6-5r79?

GHSA-7mpv-9xg6-5r79 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 38th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-7mpv-9xg6-5r79?

GHSA-7mpv-9xg6-5r79 is classified as CWE-770 (CWE-770). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-7mpv-9xg6-5r79 published, and has it been updated?

GHSA-7mpv-9xg6-5r79 was published on April 7, 2025 and was last updated on April 8, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀

🦀 crates.io

Not in CISA KEV

HIGH severity

Apollo Compiler Named Fragment Processing VulnerabilityGHSA-7mpv-9xg6-5r79

HIGHFix: apollographql/apollo-rs#952

GHSA-7mpv-9xg6-5r79 is a high-severity (CVSS 7.5) CWE-770 vulnerability in apollo-compiler. A fix is available for apollo-compiler — see the affected versions and patch details below.

Also known asCVE-2025-31496

Published

Apr 7, 2025

Updated

Apr 8, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-7mpv-9xg6-5r79.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs38th percentile — riskier than 38% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🦀apollo-compiler

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`apollo-compiler`	all versions	1.27.0`cargo update -p apollo-compiler --precise 1.27.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for apollo-compiler, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update apollo-compiler to 1.27.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7mpv-9xg6-5r79 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

# 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