mtrudel bandit · CRLF Injection
Source GCVE Database
Not known to be exploited · CVSS 6.9 Medium : upgrade to 1.12.5 when convenient.
Data as of 19 Nov 2026, 12:38 UTC
Thin evidence
One scorer or none| CNA (EEF) | CVSS 4.0 | 6.9 |
|---|
- Patch
- Available – fixed in 1.12.5, d38cf046c9a3cae4d0f88001c2ceb4143f86366b
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 20 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 18 Nov 2026.
What to do
Upgrade bandit to 1.12.5; bandit to d38cf046c9a3cae4d0f88001c2ceb4143f86366b.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| mtrudelbandit | Affected
| Fixed in
|
| banditmtrudel/bandit | Affected
| Fixed in
|
Hexbanditpkg:hex/banditOther threats | Affected
| Fixed in
|
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, downstream applications should sanitize and validate HTTP/2 header field values before use to mitigate injection risks. Avoid directly logging or forwarding untrusted header values without proper neutralization.
Description
A CRLF Injection vulnerability in mtrudel bandit versions from 1.4.0 before 1.12.5 allows unauthenticated remote attackers to inject CR, LF, or NUL characters into HTTP/2 request headers. The vulnerability arises because Bandit.HTTP2.Stream.read_headers/1 does not validate header field values for these characters, unlike the HTTP/1 path. While Bandit itself does not directly expose these injected bytes in responses or logs, downstream applications that consume these headers may be at risk if they handle header values insecurely. Additionally, a related issue allows duplicate :authority pseudo-headers, potentially causing inconsistent host resolution.
References
- github.com/mtrudel/bandit/security/advisories/GHSA-x3gh-xhj4-3vq8 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-75484 (opens in a new tab)
- github.com/mtrudel/bandit/commit/d38cf046c9a3cae4d0f88001c2ceb4143f86366b (opens in a new tab)
- github.com/mtrudel/bandit/commit/fff06efe3be962b484bd4d3eb339372fda5a231f (opens in a new tab)
- cna.erlef.org/cves/CVE-2026-75484.html (opens in a new tab)
- osv.dev/vulnerability/EEF-CVE-2026-75484 (opens in a new tab)