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


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 28 Oct 2026
- **Also known as:** GHSA-36rq-8957-mjrx

## What is RUSTSEC-2026-0417?

RUSTSEC-2026-0417 is a vulnerability in juniper, published on 28 Oct 2026. 

### Official 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.

## Which versions are affected by RUSTSEC-2026-0417?

1 open source package ship an affected version, including juniper.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `juniper` | crates.io | From 0.0.0-0 | 0.17.2 |

## How do I fix RUSTSEC-2026-0417?

Upgrade juniper to 0.17.2 or later.

## Is RUSTSEC-2026-0417 being exploited?

There is no known exploitation of RUSTSEC-2026-0417 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for RUSTSEC-2026-0417 and fix it if it is affected.

What it is: RUSTSEC-2026-0417 is a vulnerability in juniper, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of RUSTSEC-2026-0417 in the wild and no public exploit code.

Affected packages and fixed versions:
- juniper (crates.io): affected from 0.0.0-0; fixed in 0.17.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/RUSTSEC-2026-0417/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0417/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/RUSTSEC-2026-0417

---
From sbomify Insights: https://insights.sbomify.com/RUSTSEC-2026-0417/
Summaries are generated and may contain mistakes; the official description above is the record.