{"answers":{"affected":"1 open source package ship an affected version, including mint.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-94194 exists.","fix":"Upgrade mint to 1.10.2 or later.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-94194 and fix it if it is affected.\n\nWhat 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-94194 exists.\n\nAffected packages and fixed versions:\n- mint (Hex): affected from 0.1.0; fixed in 1.10.2\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-94194/ (Markdown: https://insights.sbomify.com/CVE-2026-94194/index.md)","id":"CVE-2026-94194","markdown":"https://insights.sbomify.com/CVE-2026-94194/index.md","name":"CVE-2026-94194","record":{"aliases":["EEF-CVE-2026-94194","GHSA-gvrc-75rc-7gj9"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Elixir HTTP client","requires_auth":"none","summary":"A malicious server can desynchronize the Mint HTTP client and intermediaries via response smuggling, poisoning subsequent responses on pooled connections.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"EEF","cpe":[],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-444","name":"Inconsistent Interpretation of HTTP Requests"}],"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.\n\nmessage_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.\n\nMint 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.\n\nThis issue affects mint: from 0.1.0 before 1.10.2.","ecosystems":["Hex"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Other in mint","id":"CVE-2026-94194","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Hex","product":null,"products":[],"type":"other","year":"2026"},"n_packages":1,"n_references":6,"next":{"headline":"NGINX Ingress Controller vulnerability","id":"CVE-2026-94197"},"packages":[{"ecosystem":"Hex","fixed":["1.10.2"],"introduced":["0.1.0"],"last_affected":[],"package":"mint","purl":"pkg:hex/mint","source":"EEF-CVE-2026-94194"}],"prev":{"headline":"Module object deallocation can free a live ThreadX kernel object","id":"CVE-2026-94192"},"products":["mint"],"published":"2026-09-28","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"Erlang Ecosystem Foundation","prefix":"EEF"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-30","vendors":["elixir-mint"]},"summary":"A malicious server can desynchronize the Mint HTTP client and intermediaries via response smuggling, poisoning subsequent responses on pooled connections.","url":"https://insights.sbomify.com/CVE-2026-94194/"}