Juniper hyper: Unbounded memory use on large request bodies
Affects juniper_hyperSource GCVE Database
CVSS 7.5 High : upgrade to 0.10.1 soon.
Data as of 29 Oct 2026, 17:51 UTC
- Patch
- Available – fixed in 0.10.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HWhat to do
Upgrade juniper_hyper to 0.10.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
crates.iojuniper_hyperpkg:cargo/juniper_hyperOther 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 juniper_hyper to version 0.10.1 or later, which enforces a default 2 MiB limit on request body size and returns a 413 Payload Too Large response for larger requests. Alternatively, configure the juniper_hyper::BodyLimit extension to set appropriate request body size limits. Since a patch is available, applying the official fix is the recommended remediation.
Description
The juniper_hyper crate versions before 0.10.1 have a vulnerability where the graphql() and graphql_sync() functions read the entire POST request body into memory without size limits. This can lead to unbounded memory consumption and potential denial of service by exhausting server memory. Version 0.10.1 introduces a default 2 MiB limit on request body size, responding with 413 Payload Too Large for larger bodies, and allows customization of this limit via juniper_hyper::BodyLimit.