Advisory

RUSTSEC-2026-0419

Also known as: GHSA-fj3h-2jc3-973v

Summary

Unbounded memory use on large request bodies

Details

The make_graphql_filter() and make_graphql_filter_sync() filters of juniper_warp read the whole body of a POST request into memory before they parsed the body. The filters 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_warp 0.9.1 reads at most 2 MiB of a request body by default. The filters respond with 413 Payload Too Large to larger bodies. make_graphql_filter_with_body_limit() and make_graphql_filter_sync_with_body_limit() set another limit.

Severity

High Basis: CVSS v3 score 7.5, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Dates

Published
2026-10-29 12:00 UTC
Modified
2026-10-29 14:15 UTC

Affected packages and fixes

juniper_warp

crates.io · All systems

Affected

  • introduced 0.0.0-0, fixed 0.9.1 (semver)

Fixed versions

0.9.1

Fix

  • Fixed version 0.9.1
    cargo update -p juniper_warp --precise 0.9.1

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: RustSec Advisory Database · CC0-1.0

Sources & licences