{"answers":{"affected":"1 open source package ship an affected version, including hex_core.","exploited":"There is no known exploitation of CVE-2026-105274 in the wild and no public exploit code.","fix":"Upgrade hex_core to 0.20.0 or later.","what":"CVE-2026-105274 is a low-severity denial of service vulnerability in erlang hex, published on 12 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-105274 and fix it if it is affected.\n\nWhat it is: CVE-2026-105274 is a low-severity denial of service vulnerability in erlang hex, published on 12 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-105274 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- hex_core (Hex): affected from 0.1.0; fixed in 0.20.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-105274/ (Markdown: https://insights.sbomify.com/CVE-2026-105274/index.md)","id":"CVE-2026-105274","markdown":"https://insights.sbomify.com/CVE-2026-105274/index.md","name":"CVE-2026-105274","record":{"aliases":["DEBIAN-CVE-2026-105274","EEF-CVE-2026-105274","GHSA-7c4r-cgf9-9jmq","UBUNTU-CVE-2026-105274"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Erlang package manager","requires_auth":"none","summary":"A malicious repository mirror can exhaust Erlang VM memory by sending highly compressed data, causing a denial of service in hex_core, hex, and rebar3.","user_interaction":"required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"EEF","cpe":[],"cvss":{"score":2.1,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-409","name":"Improper Handling of Highly Compressed Data (Data Amplification)"}],"description":"Improper Handling of Highly Compressed Data (Data Amplification) vulnerability in hexpm hex_core allows an untrusted repository mirror, or a server answering hex_core's API requests, to exhaust the memory of the Erlang VM running hex_core. The same code is vendored in Hex (mix_hex_repo, mix_hex_api) and rebar3 (r3_hex_repo, r3_hex_api).\n\nhex_repo:get_names/1, hex_repo:get_versions/1, hex_repo:get_package/2 and hex_repo:get_policy/2 decompress the registry response with zlib:gunzip/1 and decode the signed envelope before verifying its signature. A mirror doesn't have the repository's private key, but it chooses the compressed bytes, so a small response decompresses into an envelope of any size before the signature check rejects it.\n\nhex_api decodes responses with the application/vnd.hex+erlang content type through hex_safe_binary_to_term:safe_binary_to_term/1, which calls binary_to_term(Binary, [safe]). The safe option prevents atom creation, but it accepts compressed terms and doesn't limit the size of the decoded term, and the check that rejects functions and ports runs after the term has been built. The fix for CVE-2026-21619 added the safe option and that check without bounding the decoded size.\n\nThis issue affects rebar3: from 3.9.1 before 3.27.3; hex: from 2.1.0 before 2.5.2; hex_core: from 0.1.0 before 0.20.0.","ecosystems":["Hex"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"hex_core decompresses registry and Erlang term API responses without size limits","id":"CVE-2026-105274","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Hex","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":1,"n_references":9,"next":{"headline":"Satel Netco Design Relative Path Traversal","id":"CVE-2026-105275"},"packages":[{"ecosystem":"Hex","fixed":["0.20.0"],"introduced":["0.1.0"],"last_affected":[],"package":"hex_core","purl":"pkg:hex/hex_core","source":"EEF-CVE-2026-105274"}],"prev":{"headline":"J4Care dcm4che Loop with Unreachable Exit Condition","id":"CVE-2026-105273"},"products":["hex","hex_core","rebar3"],"published":"2026-10-12","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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-15","vendors":["erlang","hexpm"]},"summary":"A malicious repository mirror can exhaust Erlang VM memory by sending highly compressed data, causing a denial of service in hex_core, hex, and rebar3.","url":"https://insights.sbomify.com/CVE-2026-105274/"}