CVE-2026-59249— Elixir Mint Mint 输入验证错误漏洞

Sign-tolerant HTTP/1 chunk-size parser in Mint enables response smuggling against strict intermediaries on pooled connections

Inconsistent interpretation of HTTP requests (HTTP response smuggling) vulnerability in elixir-mint mint allows a malicious HTTP/1 server to desynchronize a strict intermediary and the Mint client on the same pooled connection, enabling response-queue poisoning against subsequent requests that share the connection. The Mint.HTTP1.decode_body/5 function in lib/mint/http1.ex parses the chunk-size line of a Transfer-Encoding: chunked response with Integer.parse(data, 16). RFC 7230 defines chunk-size = 1*HEXDIG and forbids any sign prefix, but Integer.parse/2 accepts an optional leading + or -. A chunk-size line of +5 is accepted as a five-byte chunk; lines of +0 and -0 are accepted as the terminating zero-length chunk and end the message body early. An RFC-strict intermediary in the response path rejects these forms, so the intermediary and the Mint client disagree on where one response ends and the next begins. On a pooled keep-alive connection, an attacker-influenced origin can inject bytes that the client attributes to the next legitimate response on the same connection, poisoning the response queue and corrupting the responses returned to unrelated in-flight requests. This issue affects mint: from 0.1.0 before 1.9.3.

N/A

HTTP请求的解释不一致性(HTTP请求私运)

Elixir Mint Mint 输入验证错误漏洞

elixir-mint mint是elixir-mint的HTTP客户端库。 Elixir Mint Mint 0.1.0版本至1.9.3之前版本存在输入验证错误漏洞，该漏洞源于对HTTP请求的解析不一致，Transfer-Encoding: chunked响应中块大小行的Integer.parse(data, 16)函数接受可选的前导+或-符号，而与RFC 7230严格中介的分块解析不一致，导致同一连接上HTTP响应夹带攻击，使得恶意HTTP/1服务器能够对后续请求进行响应队列投毒。

N/A

N/A