Skip to main content
CVE-2026-134342VulnerabilityPublished

actix-http 3.18.10 before 3.20.2 contains an HTTP request smuggling vulnerability in its chunked decoder, which treats

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-134342· Medium 6.9

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

Data as of 21 Nov 2026, 19:45 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 21 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

A fix is available in actix-http version 3.20.2 and later. Users should upgrade to version 3.20.2 or newer to remediate this vulnerability. No additional mitigation steps are indicated.

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 treats a bare line feed (LF) after the last chunk as the start of a trailer section. This allows attackers to send a specially crafted body ending with 0\r\n\n through a connection-reusing proxy, causing the next request's body to be misinterpreted as new requests. This can bypass web application firewalls (WAF) or other upstream protections.

References

Community reviews

Loading reviews…