Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Versions of juniper_warp before 0.9.1 read the entire body of a POST request into memory through the make_graphql_filter() and make_graphql_filter_sync() filters, with no size limit. An unauthenticated remote client can send a large body and exhaust the server's memory. Upgrade to juniper_warp 0.9.1, which limits request bodies to 2 MiB by default and responds with 413 Payload Too Large to larger ones; the make_graphql_filter_with_body_limit() and make_graphql_filter_sync_with_body_limit() functions can set a different limit.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 7.5 | High | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | OSV |
- CISA KEV Not listed.
- EPSS No score.
Timeline
- 31 Oct 2026, 14:24 UTC First seen by agentprime
- 31 Oct 2026, 14:24 UTC Confirmed by OSV