Skip to main content
VulnerabilityPublished Updated

CVE-2026-39805: mtrudel bandit · HTTP Request/Response Smuggling

Affects mtrudel banditSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.3 Medium : upgrade to 1.11.0 when convenient.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.11.0, f2ca636eb6df385219957e8934e9fc6efa1630d1
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 May 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 29 Oct 2026.

What to do

Upgrade bandit and mtrudel/bandit to 1.11.0; bandit to f2ca636eb6df385219957e8934e9fc6efa1630d1.

Affected software

ProductAffectedFixed in
mtrudelbanditAffected
  • >=0.1.0 <1.11.0
Fixed in
  • 1.11.0
mtrudelbanditAffected
  • ≥ 7bc8d97cd22697c299baa8012b7f419a7606a80c, < f2ca636eb6df385219957e8934e9fc6efa1630d1
Fixed in
  • f2ca636eb6df385219957e8934e9fc6efa1630d1
GitHubmtrudel/banditpkg:github/mtrudel/banditOther threatsAffected
  • <1.11.0
Fixed in
  • 1.11.0
Hexbanditpkg:hex/banditOther threatsAffected
  • >=0.1.0 <1.11.0
Fixed in
  • 1.11.0

CPE configurations (1)

  • cpe:2.3:a:mtrudel:bandit:*:*:*:*:*:*:*:*

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

AI-suggested

If you cannot patch yet, users should consider deploying additional proxy or WAF configurations that reject requests with multiple conflicting Content-Length headers or enforce strict HTTP request parsing according to RFC 9112 §6.3. Monitoring for anomalous HTTP request patterns involving duplicate Content-Length headers may help detect exploitation attempts.

Description

Inconsistent Interpretation of HTTP Requests vulnerability in mtrudel bandit allows HTTP request smuggling via duplicate Content-Length headers. 'Elixir.Bandit.Headers':get_content_length/1 in lib/bandit/headers.ex uses List.keyfind/3, which returns only the first matching header. When a request contains two Content-Length headers with different values, Bandit silently accepts it, uses the first value to read the body, and dispatches the remaining bytes as a second pipelined request on the same keep-alive connection. RFC 9112 §6.3 requires recipients to treat this as an unrecoverable framing error. When Bandit sits behind a proxy that picks the last Content-Length value and forwards the request rather than rejecting it, an unauthenticated attacker can smuggle requests past edge WAF rules, path-based ACLs, rate limiting, and audit logging. This issue affects bandit: before 1.11.0.

References

Community reviews

Loading reviews…