Skip to main content
Menu
CVEs

Actix HTTP HTTP request smuggling in chunked decoder

Affects actix-http 3.18.10 before 3.20.2 when a proxy in front of an actix-web server reuses connections for later requests. Fixed in 3.20.2.

CVE-2026-134342Published November 21, 2026, updated

6.9MediumCNA
Exploited
No known exploitation
Fix
Fixed in 3.20.2
Who is exposed
Not reported

Summary

Written by a model

actix-http 3.18.10 before 3.20.2 contains an HTTP request smuggling vulnerability in its chunked decoder, which treats a bare LF after the last chunk as the start of a trailer section. Attackers can send a body ending in 0\r\n\n through a connection-reusing proxy so the next request's body is parsed as new requests, bypassing WAF or upstream protections.

Who should check

Teams running actix-web servers on actix-http 3.18.10 before 3.20.2 behind a connection-reusing proxy or WAF

“Affecting actix-http >= 3.18.10, < 3.20.2”

vulncheck.com

What to do

Upgrade to a fixed version: 3.20.2.

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-134342 (actix-http 3.18.10 before 3.20.2 HTTP Request Smuggling via Chunked Transfer-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-134342 (entry last updated 2026-11-21):
Affected:
- crates.io package actix-http: from 3.18.10, fixed in 3.20.2
Fixed versions: 3.20.2.
Conditions (all must be true for the bug to be hit):
- Affected: actix-http 3.18.10 up to before 3.20.2 (source: https://www.vulncheck.com/advisories/actix-http-3.18.10-before-3.20.2-http-request-smuggling-via-chunked-transfer-encoding-decoder)
- A proxy in front of the actix-web server reuses the connection for subsequent requests (source: https://github.com/actix/actix-web/security/advisories/GHSA-2q7f-mf9f-5qhr)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-134342 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134342 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-2q7f-mf9f-5qhr
- https://www.vulncheck.com/advisories/actix-http-3.18.10-before-3.20.2-http-request-smuggling-via-chunked-transfer-encoding-decoder
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-134342
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-134342"}.

Affected versions

cve.now Index

40Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach16/20actix-http: 1.1M downloads a week
  • Severity6.9/10CVSS 6.9
  • No patch0/5No signal

What would change the score

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

Impact

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · actix/actix-web · Advisory GHSA-2q7f-mf9f-5qhr
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-134342
RecordNVD · CVE-2026-134342
Other links 1
Linkvulncheck.com · advisories/actix-http-3.18.10-before-3.20.2-http-request-smuggling-via-chunked-transfer-encoding-decoder

Questions about CVE-2026-134342

Is CVE-2026-134342 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?

The chunked transfer-encoding decoder in actix-http can be tricked into treating one request as two, so a smuggled request can get past a WAF or other upstream protections and reach endpoints those protections would otherwise block.

Source: vulncheck.com, github.com

Which versions are affected by CVE-2026-134342?

actix-http (crates.io): from 3.18.10 before 3.20.2.

Source: cve.now feed data

Am I affected, and how do I check?

Versions from 3.18.10 up to, but not including, 3.20.2 of actix-http are affected, in setups where a proxy in front of an actix-web server reuses the connection for subsequent requests. To check a project, look up the actix-http version in its Cargo.lock file (for example with cargo tree -p actix-http) and confirm whether a proxy sits in front of the server.

Source: vulncheck.com, github.com

How do I fix CVE-2026-134342?

Upgrade actix-http to version 3.20.2, which is the fixed version named in the advisory.

Source: vulncheck.com, github.com

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