ZDF
Sign inSign up

Vulnerabilities

Vulnerability · RUSTSEC-2026-0447

Compressed request bodies can exhaust memory before extractor limits apply

Published Nov 6, 2026 · catalog updated Nov 6, 2026 · RustSec Rust

Last checked Nov 7, 2026. A connected source was read within the last 7 days.

Open the advisory

Exploitation likelihood is not on this record for RUSTSEC-2026-0447. A missing EPSS score is not a low risk. Compare RustSec Rust with the linked advisory before you change production.

Gaps on this record

  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
  • EPSS is missing. A missing score is not a low risk.

Same product and reporting

Severity
Unknown—
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Awaiting synchronization with FIRST
Remediation
Advisory link
Affected products
crates.io actix-web

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • crates.io actix-web0.0.0-0 → 4.18.2

How to fix RUSTSEC-2026-0447

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for RUSTSEC-2026-0447. A missing EPSS score is not a low risk. Compare RustSec Rust with the linked advisory before you change production.

Which versions are affected?

Compare what you have installed with 0.0.0-0 → 4.18.2. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Nov 6, 2026 · GitHub Advisory Database

    Detected

    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. Upgr

  2. Nov 6, 2026 · GitHub Advisory Database

    Fix available

    actix-web fixed in 4.18.2

  3. Nov 6, 2026 · GitHub Advisory Database

    Fix available

    actix-web fixed in 4.18.2

  4. Nov 6, 2026 · GitHub Advisory Database

    Updated

    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. Upgr

Sources

  • GitHub Advisory DatabasePackage advisoryGHSA-qph8-7859-gq2f

    GitHub Advisory Database record mirrored by OSV.

    github.com
  • OpenSSF OSV / OSV ScannerPackage advisoryRUSTSEC-2026-0447

    Compressed request bodies can exhaust memory before extractor limits apply

    osv.dev
  • RustSec Advisory DBVendor advisoryRUSTSEC-2026-0447

    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

    crates.io

References

Freshness

Last verified in this catalog Nov 6, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • GitHub Advisory DatabaseNov 7, 2026
  • OpenSSF OSV / OSV ScannerNov 7, 2026
  • RustSec Advisory DBNov 7, 2026