{"answers":{"affected":"1 open source package ship an affected version, including juniper_warp.","exploited":"There is no known exploitation of RUSTSEC-2026-0419 in the wild and no public exploit code.","fix":"Upgrade juniper_warp to 0.9.1 or later.","what":"RUSTSEC-2026-0419 is a vulnerability in juniper_warp, published on 29 Oct 2026."},"fix_prompt":"Check this codebase for RUSTSEC-2026-0419 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2026-0419 is a vulnerability in juniper_warp, published on 29 Oct 2026. \nExploitation: There is no known exploitation of RUSTSEC-2026-0419 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- juniper_warp (crates.io): affected from 0.0.0-0; fixed in 0.9.1\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/RUSTSEC-2026-0419/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0419/index.md)","id":"RUSTSEC-2026-0419","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0419/index.md","name":"RUSTSEC-2026-0419","record":{"aliases":["GHSA-fj3h-2jc3-973v"],"analysis":null,"analysis_generated_by":null,"assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"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.\n\n`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.","ecosystems":["crates.io"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Unbounded memory use on large request bodies","id":"RUSTSEC-2026-0419","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":null,"year":"2026"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["0.9.1"],"introduced":["0.0.0-0"],"last_affected":[],"package":"juniper_warp","purl":"pkg:cargo/juniper_warp","source":"RUSTSEC-2026-0419"}],"products":null,"published":"2026-10-29","related":[],"sources":[{"class":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":null,"url":"https://insights.sbomify.com/RUSTSEC-2026-0419/"}