{"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-49753 exists.","fix":"Upgrade mint to 1.9.0 or later.","what":"CVE-2026-49753 is a medium-severity 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-49753 and fix it if it is affected.\n\nWhat it is: CVE-2026-49753 is a medium-severity 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-49753 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-49753/ (Markdown: https://insights.sbomify.com/CVE-2026-49753/index.md)","id":"CVE-2026-49753","markdown":"https://insights.sbomify.com/CVE-2026-49753/index.md","name":"CVE-2026-49753","record":{"aliases":["EEF-CVE-2026-49753","GHSA-mjqx-c6f6-7rc2"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Elixir HTTP client","requires_auth":"none","summary":"An attacker-controlled server can desynchronize HTTP response framing in the Mint Elixir client, potentially leaking data across shared 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:N/VI:L/VA:N/SC:L/SI:L/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 attacker-controlled HTTP/1 servers to desynchronise response framing on shared connections.\n\nMint's HTTP/1 Content-Length parser, Mint.HTTP1.Parse.content_length_header/1 in lib/mint/http1/parse.ex, parses the header value with Integer.parse/1, which accepts an optional + or - sign prefix. The length \u003e= 0 guard rejects negatives, but inputs such as +0 or +123 are returned as valid lengths. RFC 7230 specifies Content-Length = 1*DIGIT, with no sign character permitted.\n\nA fronting proxy or load balancer that strictly enforces the grammar will reject or reframe a header like Content-Length: +0, while Mint silently treats it as zero. When Mint reuses the socket (keep-alive, pipelining, or any pooled connection shared across requesters), the parser disagreement is a response-smuggling primitive: the proxy delimits the body one way, Mint another, and bytes from one response get attributed to the next. Where the same Mint connection is shared across trust boundaries, an attacker-controlled upstream can leak bytes into a different consumer's response stream.\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 response smuggling in Mint HTTP/1 client via lenient Content-Length parsing","id":"CVE-2026-49753","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Hex","product":null,"products":[],"type":"other","year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"HTTP/2 CONTINUATION flood in Mint client via unbounded header-block accumulation","id":"CVE-2026-49754"},"packages":[{"ecosystem":"Hex","fixed":["1.9.0"],"introduced":["0"],"last_affected":[],"package":"mint","purl":null,"source":"GHSA-mjqx-c6f6-7rc2"},{"ecosystem":"Hex","fixed":["1.9.0"],"introduced":["0"],"last_affected":[],"package":"mint","purl":"pkg:hex/mint","source":"GHSA-mjqx-c6f6-7rc2"},{"ecosystem":"Hex","fixed":["1.9.0"],"introduced":["0.1.0"],"last_affected":[],"package":"mint","purl":"pkg:hex/mint","source":"EEF-CVE-2026-49753"}],"prev":{"headline":"GPU DDK - Dimension Mismatch and Integer Truncation in PMRDevPhysAddrOSMem","id":"CVE-2026-49746"},"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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-02","vendors":["elixir-mint"]},"summary":"An attacker-controlled server can desynchronize HTTP response framing in the Mint Elixir client, potentially leaking data across shared connections.","url":"https://insights.sbomify.com/CVE-2026-49753/"}