Advisory record · GHSA-pfrg-qg4f-grmv

Unbounded memory use on large request bodies

CVSS 7.5 High

Published by the GitHub Advisory Database at 28 Oct 2026, 12:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
juniper_hypercrates.io>=0.0.0-0, <0.10.10.10.1
Identifiers
GHSA-pfrg-qg4f-grmv · RUSTSEC-2026-0415
Published
28 Oct 2026
Updated
29 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

juniper_hyper versions before 0.10.1 read the entire body of a POST request into memory in the graphql() and graphql_sync() functions, with no size limit. An unauthenticated client can send a very large body and exhaust the server's memory. Upgrade to juniper_hyper 0.10.1, which reads at most 2 MiB by default and returns 413 Payload Too Large for larger bodies; the limit can be changed per request with a BodyLimit in the request extensions.

Written 3 Nov 2026.

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

ScoreRatingCVSSVectorSource
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

  1. 31 Oct 2026, 14:24 UTC First seen by agentprime
  2. 31 Oct 2026, 14:24 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.