Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2022-3212: <bytes::Bytes as axum_core::extract::FromRequest>::from_request would not, by default, set a limit for the siz

52
This week
HIGH 7.5REMOTEUPGRADE

CVE-2022-3212 is a high-severity flaw (CVSS 7.5) affecting axum-core. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

<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

Why this priority

  • High severity
  • Public exploit reference
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score7.5 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance1.0% (top 37%)
CISA exploited listNo
WeaknessCWE-770
Published2022-09-14
Last modified2026-06-17
Publisher (CNA): JFrog · Vendor: axum-core project

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

axum-core project axum-core UPGRADE
Affected: < 0.2.8 · 0.3.0 rc1
Fixed in: 0.2.8
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy axum-core || rpm -q axum-core || axum-core --version
2. UPGRADE to 0.2.8 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade axum-core
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade axum-core
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-3212?

axum-core: upgrade to 0.2.8. Exact commands for each OS are on this page.

Is CVE-2022-3212 being exploited?

CVE-2022-3212 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-3212 affect?

CVE-2022-3212 affects axum-core. Severity is high (CVSS 7.5). <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 memo

How urgent is CVE-2022-3212?

Priority 52/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.