# CVE-2026-94194: Other in mint > A malicious server can desynchronize the Mint HTTP client and intermediaries via response smuggling, poisoning subsequent responses on pooled connections. - **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 28 Sep 2026 - **Updated:** 30 Sep 2026 - **Also known as:** EEF-CVE-2026-94194, GHSA-gvrc-75rc-7gj9 ## What is CVE-2026-94194? CVE-2026-94194 is a medium-severity vulnerability in elixir-mint mint, published on 28 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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. Weakness: CWE-444 (Inconsistent Interpretation of HTTP Requests) ## Which versions are affected by CVE-2026-94194? 1 open source package ship an affected version, including mint. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `mint` | Hex | From 0.1.0 | 1.10.2 | ## How do I fix CVE-2026-94194? Upgrade mint to 1.10.2 or later. ## Is CVE-2026-94194 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-94194 exists. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-94194 and fix it if it is affected. What it is: CVE-2026-94194 is a medium-severity vulnerability in elixir-mint mint, published on 28 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-94194 exists. Affected packages and fixed versions: - mint (Hex): affected from 0.1.0; fixed in 1.10.2 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-94194/ (Markdown: https://insights.sbomify.com/CVE-2026-94194/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-94194 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-94194 - OSV: https://osv.dev/vulnerability/CVE-2026-94194 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-94194/ Summaries are generated and may contain mistakes; the official description above is the record.