Juniper: Excessive CPU and memory use on crafted GraphQL documents
Affects juniperSource GCVE Database
CVSS 7.5 High : upgrade to 0.17.2 soon.
Data as of 29 Oct 2026, 17:51 UTC
- Patch
- Available – fixed in 0.17.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HWhat to do
Upgrade juniper to 0.17.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
crates.iojuniperpkg:cargo/juniperOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to Juniper version 0.17.2 or later, which includes fixes that limit tokens and fields, optimize validation to avoid repeated fragment visits, and cap conflict comparisons and reports. These changes prevent excessive resource consumption from crafted GraphQL documents. No additional mitigation is required once patched.
Description
The Juniper GraphQL library versions before 0.17.2 contain performance vulnerabilities where crafted GraphQL documents can cause excessive CPU and memory usage. These issues arise from inefficient validation and execution logic, including quadratic parsing time and exponential fragment expansion. The vulnerability allows unauthenticated requests to consume significant server resources, potentially leading to denial of service. Version 0.17.2 addresses these issues by imposing limits on tokens and fields, optimizing validation rules, and capping conflict reports.