Advisory record · GHSA-m77f-652q-wwp4

axum-core has no default limit put on request bodies

CVSS 7.5 HighEPSS 0.010 · 64th percentile

Published by the GitHub Advisory Database at 15 Sept 2022, 03:25 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
axum-corecrates.io<0.2.8 || >=0.3.0-rc.1, <0.3.0-rc.20.2.8, 0.3.0-rc.2
Identifiers
GHSA-m77f-652q-wwp4 · CVE-2022-3212 · RUSTSEC-2022-0055
Weakness (CWE)
CWE-770
Published
15 Sept 2022
Updated
8 Nov 2023

Machine-written summary

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

axum-core versions below 0.2.8 and 0.3.0-rc.1 are vulnerable; fixed in 0.2.8 and 0.3.0-rc.2. A remote peer sending a very large or endless request body can exhaust server memory and crash the server, since no default body size limit was applied to Bytes extraction and to the Form, Json and String extractors built on it. Upgrade axum-core to 0.2.8 or 0.3.0-rc.2; the patched versions set a 2 MB default limit.

Written 9 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 CNA (JFROG)
  • CISA KEV Not listed.
  • EPSS 0.010, the 64th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:20 UTC First seen by agentprime
  2. 31 Oct 2026, 15:20 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.