Is CVE-2026-114216 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-114216 being exploited in the wild.

How severe is CVE-2026-114216?

Informational severity, published 26 October 2026.

Which products and versions are affected?

Bandit 1.12.4 to before 1.14.0.

Is there a fix for CVE-2026-114216?

Yes: fixed in Bandit 1.14.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-114216 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-114216?

Check whether you run Bandit at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-114216: Bandit HTTP request smuggling in chunked body reader

CVE-2026-114216 · Severity: info · Published 2026-10-26

Bandit is an Elixir-based web server library. An HTTP request smuggling vulnerability in its chunked body reader allows an unauthenticated remote attacker to bypass a front-end proxy and inject a second request into the application, potentially reaching protected endpoints or causing account takeover. Only deployments with a proxy in front of Bandit are vulnerable; direct exposure is not affected.

Quick answers

Is CVE-2026-114216 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-114216 being exploited in the wild.
How severe is CVE-2026-114216?: Informational severity, published 26 October 2026.
Which products and versions are affected?: Bandit 1.12.4 to before 1.14.0.
Is there a fix for CVE-2026-114216?: Yes: fixed in Bandit 1.14.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-114216 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-114216?: Check whether you run Bandit at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: Bandit 1.14.0

Technical details

The vulnerability is an inconsistent interpretation of HTTP requests (request/response smuggling) in the HTTP/1.1 chunked body reader of lib/bandit/http1/socket.ex. The reader fails to validate chunk extensions against RFC 9112 grammar, allowing bare LF, CR, and other control bytes to be interpreted differently by front-end proxies, causing request desynchronization. An attacker sends a malformed chunk with a bare LF that proxies interpret as a single request boundary but Bandit interprets as two separate pipelined requests.

Affected products

Bandit 1.12.4 to before 1.14.0

Timeline

2026-10-26: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.