Skip to main content
Menu
CVEs

Actix HTTP decompression bomb DoS in encoding decoder

CVE-2026-128242EUVD-2026-125050GHSA-GXJ9-VQFQ-HP64Published November 13, 2026, updated

8.7HighCNA
Exploited
No known exploitation
Fix
Fixed in actix-http 3.20.1 · actix-web 4.18.2
Who is exposed
Not reported

Summary

actix-http before 3.20.1 and actix-web before 4.18.2 contain an unbounded decompression vulnerability in encoding::Decoder that lets remote attackers exhaust memory and CPU via compressed bodies. Attackers can send small highly compressed gzip, deflate, Brotli or zstd request bodies to Json, Form, Bytes or String extractors, or serve them to awc clients, causing denial of service.

Who should check

Rust teams using actix-http before 3.20.1 or actix-web before 4.18.2 that decode untrusted compressed bodies, via awc or direct Decoder use.

“actix-http >= 0, < 3.20.1”

vulncheck.com

What to do

  1. Upgrade to a fixed version: actix-http 3.20.1 · actix-web 4.18.2.

  2. Workaround: Configure Decoder::limit() when using the decoder directly.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-128242 (actix-http before 3.20.1 and actix-web before 4.18.2 Decompression Bomb DoS via encoding::Decoder), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-128242 (entry last updated 2026-11-13):
Affected:
- crates.io package actix-http: fixed in 3.20.1
- crates.io package actix-web: fixed in 4.18.2
Fixed versions: 3.20.1, 4.18.2.
Conditions (all must be true for the bug to be hit):
- Application decodes untrusted gzip, deflate, Brotli or zstd bodies with the matching compression feature enabled. (source: https://rustsec.org/advisories/RUSTSEC-2026-0448.html)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
Workaround: Configure Decoder::limit() when using the decoder directly. (source: https://rustsec.org/advisories/RUSTSEC-2026-0448.html)
CISA KEV: CVE-2026-128242 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-128242 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (crates.io): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/actix/actix-web/security/advisories/GHSA-qph8-7859-gq2f
- https://github.com/actix/actix-web/commit/41b54d23ea04f66758c15de7e4ab18325cd25280
- https://github.com/actix/actix-web/commit/0d0be61bd757027bfcecbc53df1b7a600f21ecd0
- https://rustsec.org/advisories/RUSTSEC-2026-0448.html
- https://github.com/actix/actix-web/blob/actix-http-v3.20.0/actix-http/src/encoding/decoder.rs#L239-L301
- https://github.com/actix/actix-web/releases/tag/actix-http-v3.20.1
- https://github.com/actix/actix-web/releases/tag/actix-web-v4.18.2
- https://github.com/actix/actix-web
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-128242
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-128242"}.

Affected versions

cve.now Index

45of 100 · methodology v3
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
  • Reach16/20actix-http: 1.1M downloads a week
  • Severity8.7/10CVSS 8.7
  • No patch0/5No signal

What would change the score

  • Would score about 90 if added to CISA KEV
  • Would score about 85 if CISA's SSVC rates exploitation active
  • Would score about 50 if advisories confirm default setups are exposed

Impact

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  4. Record last updated

Public exploit activity

100%0Nov 13Nov 20
  • EPSS: 0.93%

Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.

Evidence 11

Questions about CVE-2026-128242

Is CVE-2026-128242 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

What does this mean?

A decompression bomb is a small compressed body that expands into a very large amount of data. Decoding it can use excessive memory and CPU, causing denial of service.

Source: rustsec.org

Which versions are affected by CVE-2026-128242?

actix-http (crates.io): before 3.20.1. actix-web (crates.io): before 4.18.2.

Source: cve.now feed data

Am I affected, and how do I check?

The issue affects applications that decode untrusted gzip, deflate, Brotli or zstd bodies with the matching compression feature enabled, in actix-http before 3.20.1 and actix-web before 4.18.2. To check, look at the actix-http and actix-web versions in Cargo.lock (for example with cargo tree -i actix-http) and review which compression features are enabled.

Source: rustsec.org

How do I fix CVE-2026-128242?

Upgrade to a fixed version: actix-http 3.20.1 · actix-web 4.18.2. The vendor's advisory also recommends actix-http 3.20.1 or actix-web 4.18.2 or later.

Source: cve.now feed data, rustsec.org

No corrections so far. Something wrong on this page? Report an error.