DoS in axum-core due to missing request size limit
Priority LOW 35CWE-770Published · Updated
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Denial of service
- Confidentiality · integrity · availability
- None · None · High
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub. Impact type from CWE-770.
Summary
<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 it matters now
EPSS 0.01002 63rd percentileScored 2026-11-07
Public exploit Yes 2 exploit referencesTagged by NVD
Fix Fixed axum-core (tokio-rs): 0.2.8axum-core (crates.io): 0.2.8, 0.3.0-rc.2
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| tokio-rs | axum-core | 0.3.0-rc.1; before 0.2.8 | 0.2.8 | Patch available | CNA |
| — | axum-core (crates.io) | before 0.2.8 | 0.2.8 | Patch available | GHSA-m77f-652q-wwp4 |
| — | axum-core (crates.io) | 0.3.0-rc.1 to before 0.3.0-rc.2 | 0.3.0-rc.2 | Patch available | GHSA-m77f-652q-wwp4 |
- axum-core Vendortokio-rs Affected 0.3.0-rc.1; before 0.2.8 Fixed in 0.2.8 Patch available CNA
- axum-core (crates.io) Vendor— Affected before 0.2.8 Fixed in 0.2.8 Patch available GHSA-m77f-652q-wwp4
- axum-core (crates.io) Vendor— Affected 0.3.0-rc.1 to before 0.3.0-rc.2 Fixed in 0.3.0-rc.2 Patch available GHSA-m77f-652q-wwp4
CPE configurations NVD · 2
| CPE | Versions | Role | Vendor |
|---|---|---|---|
| cpe:2.3:a:axum-core_project:axum-core:*:*:*:*:*:rust:*:* | before 0.2.8 | Vulnerable | Axum-core Project |
| cpe:2.3:a:axum-core_project:axum-core:0.3.0:rc1:*:*:*:rust:*:* | 0.3.0 rc1 | Vulnerable | Axum-core Project |
- cpe:2.3:a:axum-core_project:axum-core:*:*:*:*:*:rust:*:* Versions before 0.2.8 Vulnerable ·Axum-core Project
- cpe:2.3:a:axum-core_project:axum-core:0.3.0:rc1:*:*:*:rust:*:* Versions 0.3.0 rc1 Vulnerable ·Axum-core Project
Remediation
- Fix · CNA axum-core (tokio-rs) Fixed in 0.2.8
- Fix · GHSA-m77f-652q-wwp4 axum-core (crates.io) Fixed in 0.2.8 Advisory →
- Fix · GHSA-m77f-652q-wwp4 axum-core (crates.io) Fixed in 0.3.0-rc.2 Advisory →
Timeline
- 2026-10-02 Threatist record created from CVE-2022-3212
- 2026-10-03 Alias added: GHSA-m77f-652q-wwp4
References
More tokio-rs vulnerabilities
- TI-2024-18146 Mio's tokens for named pipes may be delivered after deregistration CVSS 3.1CRITICAL 9.1
- TI-2026-20650 Bytes is vulnerable to integer overflow in BytesMut::reserve CVSS 4.0MEDIUM 5.5
- TI-2026-79968 Race condition in Tokio time Interval can cause use-after-free CVSS 4.0MEDIUM 5.8
- TI-2023-08715 Tokio's reject_remote_clients configuration may get dropped when creating a Windows named pipe CVSS 3.1MEDIUM 5.4
- TI-2025-34841 slab allows out-of-bounds access in `get_disjoint_mut` due to incorrect bounds check CVSS 4.0MEDIUM 5.1
- TI-2025-35976 Tracing logging user input may result in poisoning logs with ANSI escape sequences CVSS 4.0LOW 2.3
Sources
- CVE-2022-3212 · CVE Program
- CVE-2022-3212 · NVD
- FIRST EPSS
- GHSA-m77f-652q-wwp4 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences