RUSTSEC-2026-0419

    Dashboard / Vulnerabilities / RUSTSEC-2026-0419

    RUSTSEC-2026-0419

    Published: 29 Oct 2026Last Modified: 29 Oct 2026

    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.

    References: https://crates.io/crates/juniper_warp, https://rustsec.org/advisories/RUSTSEC-2026-0419.html, https://github.com/graphql-rust/juniper/pull/1406

    Affected packages

    Package

    Name: juniper_warp

    Purl: pkg:cargo/juniper_warp

    Affected ranges

    Type: SEMVER

    Events:

    Introduced- 0.0.0-0
    Fixed -0.9.1

    Affected versions

    Common Vulnerability Scoring System

    Attack Vector
    Network
    Adjacent
    Local
    Physical
    Privileges Required
    None
    Low
    High
    User Interaction
    None
    Required
    Scope
    Unchanged
    Changed
    Confidentiality
    None
    Low
    High
    Integrity
    None
    Low
    High
    Availability
    None
    Low
    High
    RUSTSEC-2026-0419 | CVE-DB