Skip to main content
No exploitation reportedFix available

CVE-2022-3212

No exploitation reported by the sources we read.

  • Published2022-09-14
  • Fixed in0.3.0-rc.2 · 0.2.8
  • WeaknessCWE-770

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

<bytes::Bytes as axum_core::extract::FromRequest>::from_request would not, by default, set a limit for the size of the request body. That meant if a malicious peer would send a very large (or infinite) body your server might run out of memory and crash. This also applies to these extractors which used Bytes::from_request internally: axum::extract::Form axum::extract::Json String

Timeline

dates in UTC
  1. 2022-09-1416:15CVE publishedNVD

Versions per branch

OSV · NVD
Axum-core project axum-core
BranchAffectedFixed in
0.3≥ 0.3.0-rc.1, < 0.3.0-rc.20.3.0-rc.2
0.2< 0.2.80.2.8
0.x≥ 0.0.0-0, < 0.2.80.2.8
0.3= 0.3.0no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

  1. Update Axum-core project axum-core to 0.3.0-rc.2 · 0.2.8

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • CNACVSS 3.17.5known since 2026-10-23
  • NVDCVSS 3.17.5read 2026-10-23
  • CNAweakness (CWE)CWE-770known since 2026-10-23
  • NVDweakness (CWE)CWE-770read 2026-10-23
  • FIRST EPSSEPSS score1.0 %2026-11-18
  • OSVaffected packages—
  • GitHub AdvisoriesadvisoryHIGH2022-09-15

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Published
2022-09-14
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-m77f-652q-wwp4

Frequently asked questions

What is CVE-2022-3212?

<bytes::Bytes as axum_core::extract::FromRequest>::from_request would not, by default, set a limit for the size of the request body. That meant if a malicious peer would send a very large (or infinite) body your server might run out of memory and crash. This also applies to these extractors which used Bytes::from_request internally: axum::extract::Form axum::extract::Json String

Is CVE-2022-3212 actively exploited?

Active exploitation of CVE-2022-3212 has not been confirmed. Its EPSS score was 1.0% on 2026-11-18, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2022-3212?

CVE-2022-3212 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record