Bandit versions prior to 1.11.0 are vulnerable to HTTP request smuggling due to improper handling of multiple differing Content-Length headers. Bandit accepts the first Content-Length header and dispatches the request body bytes as a second request on the same connection, violating RFC 9110 and RFC 9112 specifications. This can allow an unauthenticated attacker to bypass edge security controls like WAFs, ACLs, rate limiting, and audit logging if Bandit is behind a permissive proxy that uses the last Content-Length header. The vulnerability was introduced before version 0.1.0 and fixed in version 1.11.0.