{"answers":{"affected":"3 open source packages ship an affected version, including mint.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-49754 exists.","fix":"Upgrade mint to 1.9.0 or later.","what":"CVE-2026-49754 is a high-severity denial of service vulnerability in elixir-mint mint, published on 2 Jun 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-49754 and fix it if it is affected.\n\nWhat it is: CVE-2026-49754 is a high-severity denial of service vulnerability in elixir-mint mint, published on 2 Jun 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-49754 exists.\n\nAffected packages and fixed versions:\n- mint (Hex): affected all versions; fixed in 1.9.0\n- mint (Hex): affected all versions; fixed in 1.9.0\n- mint (Hex): affected from 0.1.0; fixed in 1.9.0\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-49754/ (Markdown: https://insights.sbomify.com/CVE-2026-49754/index.md)","id":"CVE-2026-49754","markdown":"https://insights.sbomify.com/CVE-2026-49754/index.md","name":"CVE-2026-49754","record":{"aliases":["EEF-CVE-2026-49754","GHSA-2p26-p43x-fhp8"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Elixir HTTP client","requires_auth":"none","summary":"A malicious HTTP/2 server can exhaust client memory via unbounded header accumulation, causing denial of service in the Mint Elixir library.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"EEF","cpe":[],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"description":"Allocation of Resources Without Limits or Throttling vulnerability in elixir-mint Mint allows attacker-controlled HTTP/2 servers to exhaust memory in a Mint client (HTTP/2 CONTINUATION flood).\n\nWhen Mint's HTTP/2 receive path observes a HEADERS frame without the END_HEADERS flag, the unparsed header-block fragment is parked in conn.headers_being_processed, and every subsequent CONTINUATION frame on that stream is appended to the accumulator. Nothing in the receive path caps the accumulator: there is no per-stream size limit, no CONTINUATION frame-count limit, and max_header_list_size is only enforced on outgoing requests, never on inbound header blocks (its default is :infinity).\n\nA malicious or compromised HTTP/2 server can stream an endless sequence of CONTINUATION frames (each up to the peer-advertised SETTINGS_MAX_FRAME_SIZE) and drive the client's iolist to arbitrary size, causing memory exhaustion and BEAM process death. A single connection to an attacker-controlled HTTP/2 endpoint is sufficient.\n\nThis issue affects mint: from 0.1.0 before 1.9.0.","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":"HTTP/2 CONTINUATION flood in Mint client via unbounded header-block accumulation","id":"CVE-2026-49754","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Hex","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"Decompression bomb DoS in Req via auto-decoded archive and compressed response bodies","id":"CVE-2026-49755"},"packages":[{"ecosystem":"Hex","fixed":["1.9.0"],"introduced":["0"],"last_affected":[],"package":"mint","purl":null,"source":"GHSA-2p26-p43x-fhp8"},{"ecosystem":"Hex","fixed":["1.9.0"],"introduced":["0"],"last_affected":[],"package":"mint","purl":"pkg:hex/mint","source":"GHSA-2p26-p43x-fhp8"},{"ecosystem":"Hex","fixed":["1.9.0"],"introduced":["0.1.0"],"last_affected":[],"package":"mint","purl":"pkg:hex/mint","source":"EEF-CVE-2026-49754"}],"prev":{"headline":"HTTP response smuggling in Mint HTTP/1 client via lenient Content-Length parsing","id":"CVE-2026-49753"},"products":["mint"],"published":"2026-06-02","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":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-02","vendors":["elixir-mint"]},"summary":"A malicious HTTP/2 server can exhaust client memory via unbounded header accumulation, causing denial of service in the Mint Elixir library.","url":"https://insights.sbomify.com/CVE-2026-49754/"}