# RUSTSEC-2026-0415: Unbounded memory use on large request bodies


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 28 Oct 2026
- **Also known as:** GHSA-pfrg-qg4f-grmv

## What is RUSTSEC-2026-0415?

RUSTSEC-2026-0415 is a vulnerability in juniper_hyper, published on 28 Oct 2026. 

### Official description

The `graphql()` and `graphql_sync()` functions of `juniper_hyper` read the whole body of a POST request into memory before they parsed the body. The functions had no limit on the size of the body. A client could thus send a large body and exhaust the memory of the server. The request needs no authentication.

`juniper_hyper` 0.10.1 reads at most 2 MiB of a request body by default. The functions respond with `413 Payload Too Large` to larger bodies. A `juniper_hyper::BodyLimit` in the extensions of a request changes the limit for the request.

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `juniper_hyper` | crates.io | From 0.0.0-0 | 0.10.1 |

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

Upgrade juniper_hyper to 0.10.1 or later.

## Is RUSTSEC-2026-0415 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

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-0415/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0415/index.md)
```

## Sources

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

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