{"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-82672 exists.","fix":"Upgrade mint to 1.10.1 or later.","what":"CVE-2026-82672 is a medium-severity vulnerability in elixir-mint mint, published on 19 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-82672 and fix it if it is affected.\n\nWhat it is: CVE-2026-82672 is a medium-severity vulnerability in elixir-mint mint, published on 19 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-82672 exists.\n\nAffected packages and fixed versions:\n- mint (Hex): affected from 0.1.0; fixed in 1.10.1\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-82672/ (Markdown: https://insights.sbomify.com/CVE-2026-82672/index.md)","id":"CVE-2026-82672","markdown":"https://insights.sbomify.com/CVE-2026-82672/index.md","name":"CVE-2026-82672","record":{"aliases":["EEF-CVE-2026-82672","GHSA-rj5m-69wp-cxq9"],"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 requests 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 a strict intermediary and the Mint client on a pooled connection, enabling response-queue poisoning against subsequent requests that share the connection.\n\nMint.HTTP1.Parse.chunk_size/1 in lib/mint/http1/parse.ex stops at the first non-hexadecimal byte of a chunked response's chunk-size line and returns the remainder unexamined. Mint.HTTP1.decode_body/5 in lib/mint/http1.ex then discards every byte up to the CRLF with Parse.ignore_until_crlf/1, so the accepted grammar is a run of hex digits followed by arbitrary bytes, where RFC 9112 permits only a ;-introduced chunk extension. Lines such as 5ZZZZZ and 5 9 are accepted as chunk size 5, and 0ZZZZ is accepted as the terminating chunk that ends the message body. An RFC-strict intermediary rejects such a line while Mint accepts it, so the two disagree on chunk boundaries and on where the response ends.\n\nThis issue affects mint: from 0.1.0 before 1.10.1.","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-82672","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Hex","product":null,"products":[],"type":"other","year":"2026"},"n_packages":1,"n_references":5,"next":{"headline":"Path traversal in AshAdmin file uploads via unsanitized client filename","id":"CVE-2026-82673"},"packages":[{"ecosystem":"Hex","fixed":["1.10.1"],"introduced":["0.1.0"],"last_affected":[],"package":"mint","purl":"pkg:hex/mint","source":"EEF-CVE-2026-82672"}],"prev":{"headline":"IObit Unlocker IRP_MJ_DEVICE_CONTROL IObitUnlocker.sys ZwTerminateProcess privileges management","id":"CVE-2026-82671"},"products":["mint"],"published":"2026-09-19","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-21","vendors":["elixir-mint"]},"summary":"A malicious server can desynchronize the Mint HTTP client and intermediaries via response smuggling, poisoning subsequent requests on pooled connections.","url":"https://insights.sbomify.com/CVE-2026-82672/"}