Skip to main content
← Vulnerabilities

Compressed request bodies can exhaust memory before extractor limits apply

Exploited
No known exploitation
Fix
Fixed in 4.18.2
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 4.18.2.

Published
Last modified
10/100 · provisional
None on Exploit-DB, Metasploit or GitHub

Summary

Compressed request bodies handled by the actix-web and actix-http Rust web frameworks can exhaust server memory or CPU before size limits are enforced, causing denial of service. The flaw is reachable remotely by sending a small compressed request body, and it only affects applications that have the matching compression feature enabled.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Read the original description

Body extractors do not pass their size limits to the decompression layer. A small compressed request can therefore cause a large allocation before the extractor rejects the decoded body. A remote attacker can use this to exhaust memory or CPU resources and cause denial of service.

This affects applications that read compressed request bodies with the corresponding compression feature enabled.

Upgrade to actix-web 4.18.2 or later with actix-http 3.20.1 or later. As a workaround, reject compressed request bodies at a reverse proxy or in middleware before body extraction.

cve.now Index

10Pcve.now Index 10 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach10/20Affects crates.io packages
  • Severity?/10Unknown. No CVSS score or vendor rating
  • No patch0/5No signal

What would change the score

  • Would score about 65 if added to CISA KEV
  • Would score about 60 if CISA's SSVC rates exploitation active
  • Would score about 32 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 4.18.2.

Timeline

  1. Advisory published
  2. Record last updated
  3. First seen by cve.now

Affected versions

  • actix-webcrates.io

    From 0.0.0-0 · fixed in 4.18.2

Evidence 3

  1. Advisory
  2. Repository
  3. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about RUSTSEC-2026-0447

Is RUSTSEC-2026-0447 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by RUSTSEC-2026-0447?

actix-web (crates.io): from 0.0.0-0 before 4.18.2.Source: cve.now feed data

How do I fix RUSTSEC-2026-0447?

Upgrade to a fixed version: 4.18.2.Source: cve.now feed data