Juniper warp: Unbounded memory use on large request bodies
Affects juniper_warpSource GCVE Database
CVSS 7.5 High : upgrade to 0.9.1 soon.
Data as of 29 Oct 2026, 17:51 UTC
- Patch
- Available – fixed in 0.9.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HWhat to do
Upgrade juniper_warp to 0.9.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
crates.iojuniper_warppkg:cargo/juniper_warpOther 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_warp to version 0.9.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, use the make_graphql_filter_with_body_limit() and make_graphql_filter_sync_with_body_limit() functions to set custom limits on request body size. No other mitigation is required once patched.
Description
The juniper_warp crate versions prior to 0.9.1 contain a vulnerability in the make_graphql_filter() and make_graphql_filter_sync() filters, which read the entire POST request body into memory without size limits. This allows an unauthenticated client to send a large request body and exhaust server memory, causing a denial of service. Version 0.9.1 and later implement a default 2 MiB limit on request body size and respond with 413 Payload Too Large for larger bodies, mitigating the issue.