Skip to main content
VulnerabilityPublished

CVE-2026-134342: actix-http · HTTP Request/Response Smuggling

Affects actix-httpSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.9 Medium : upgrade to 3.20.2 when convenient.

Data as of 21 Nov 2026, 17:15 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.06.9
CNA (VulnCheck)CVSS 3.16.5
Patch
Available – fixed in 3.20.2
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:L/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Upgrade actix-http to 3.20.2.

Affected software

ProductAffectedFixed in
actixactix-httpAffected
  • >=3.18.10 <3.20.2
Fixed in
  • 3.20.2
crates.ioactix-httppkg:cargo/actix-httpOther threatsAffected
  • >=3.18.10 <3.20.2
Fixed in
  • 3.20.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade actix-http to version 3.20.2 or later, where this vulnerability is fixed. No other mitigation is indicated by the vendor advisory. Applying the official fix fully addresses the issue.

Description

actix-http versions from 3.18.10 up to but not including 3.20.2 contain an HTTP request smuggling vulnerability in the chunked decoder. The flaw arises because the decoder incorrectly treats a bare LF after the last chunk as the start of a trailer section. This allows attackers to craft a request body ending with 0\r\n\n that can cause the next request's body to be parsed as new requests when passing through a connection-reusing proxy, potentially bypassing WAF or upstream protections.

References

Community reviews

Loading reviews…