Reference page — cumulative record through Saturday, October 3, 2026 UTC. Reference pages update as the archive grows; only dated daily editions are immutable pages of record.
CVE-2026-94194
elixir-mint mint — Mint HTTP/1 client applies chunked framing when chunked is not the final transfer coding, enabling response smuggling through intermediaries
AV AC AT PR UI VC VI VA CVSS EPSS %ile KEV
N L P N N L L N 6.3 .0033 23.6 —
AFFECTED
Product Versions Fixed
mint 0.1.0 – —
mint 60089586ec7adc9fddb09f69a2f5919ba9ac7f33 – 2ec8b696b5475ecbdaa87c0098957bca339e17c0
TIMELINE
Sep 24 Reserved by EEF
Sep 28 PATCH SHIPPED — CVE-2026-94194 (elixir-mint mint). Fixed in mint 2ec8b696b5475ecbdaa87c0098957bca339e17c0.
Sep 28 Published (CNA: EEF)
Description
Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') vulnerability in elixir-mint mint allows a malicious HTTP/1 server to desynchronize an intermediary and the Mint client on a pooled connection, poisoning the responses to subsequent requests that share the connection.
message_body/1 in lib/mint/http1.ex selects chunked framing when chunked is the first coding listed in a response's Transfer-Encoding fields. RFC 9112 section 6.3 applies chunked framing only when chunked is the final coding, and otherwise reads the body until the server closes the connection. For a response such as Transfer-Encoding: chunked, gzip, an intermediary that follows the RFC treats every byte up to the close as the body, while Mint ends the body at the zero-length chunk and parses the remaining bytes as the response to the next request on the connection.
Mint also keeps the connection open after an HTTP/1.0 response, final or 1xx, that carries Transfer-Encoding and Connection: keep-alive. RFC 9112 section 6.1 requires treating the framing of such a message as faulty and closing the connection after it, so bytes after its chunked body are parsed as the response to the next request in the same way.
This issue affects mint: from 0.1.0 before 1.10.2.
Lifecycle
Complete event history — 3 events, chronological
| Date | Event | Detail |
|---|
| September 24, 2026 | Reserved | Reserved by EEF |
| September 28, 2026 | PATCH SHIPPED | PATCH SHIPPED — CVE-2026-94194 (elixir-mint mint). Fixed in mint 2ec8b696b5475ecbdaa87c0098957bca339e17c0. |
| September 28, 2026 | Published | Published (CNA: EEF) |
Affected
Affected products and packages — 2 rows
| Vendor | Product / Package | Ecosystem | Version introduced | Fixed |
|---|
| elixir-mint | mint | — | 0.1.0 | — |
| elixir-mint | mint | — | 60089586ec7adc9fddb09f69a2f5919ba9ac7f33 | 2ec8b696b5475ecbdaa87c0098957bca339e17c0 |
About this page
This is a reference page, not a dated page of record. It assembles the complete lifecycle of CVE-2026-94194 from the CVE Program record, NVD enrichment, the CISA KEV catalog, EPSS, and OSV advisories. The box score's numbers (CVSS, EPSS, KEV status) are current as of Saturday, October 3, 2026 UTC and are re-derived as the archive grows; only dated daily editions are immutable pages of record. The authoritative source for this identifier is cve.org.
