CVE-2026-105274

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). hex_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. hex_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. This 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.

• CWE-409

• https://cna.erlef.org/cves/CVE-2026-105274.html
• https://github.com/erlang/rebar3/commit/209c02ec57c2cc3207ee0174c3af3675b8dc8f79
• https://github.com/erlang/rebar3/commit/360838a22f5b3a88c0358207f2923059bcbb3afb
• https://github.com/hexpm/hex/commit/671f695ac548ed01f5828c2a739ecaa942b21007
• https://github.com/hexpm/hex/commit/d8b60eee97abb119d525306f048969a217d793a5
• https://github.com/hexpm/hex_core/commit/ebe25d110717f6a3addba5232cd4a7dc1c76b628
• https://github.com/hexpm/hex_core/commit/fbb6d9de472e5edb8d6fb6b32a91cb266137892e
• https://github.com/hexpm/hex_core/security/advisories/GHSA-7c4r-cgf9-9jmq
• https://osv.dev/vulnerability/EEF-CVE-2026-105274

Published

Oct 12, 2026

Last Modified

Oct 15, 2026

Status

Deferred

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-105267The Gitea web route for deleting tags (`POST /{owner}/{repo}…8.1
• CVE-2026-105268The Gitea API routes for issue attachments (`/api/v1/repos/{…4.3
• CVE-2026-105269Satel Netco Design versions prior to v2.1.7 contains a store…6.8
• CVE-2026-10527Mattermost versions 11.7.x <= 11.7.6, 10.11.x <= 10.11.21, 1…6.3
• CVE-2026-105271"ゲオアプリ" provided by GEO CORPORATION contains an issue with c…5.1
• CVE-2026-105273MP4Parser does not adequately validate MP4 box sizes. A malf…7.5
• CVE-2026-105275Satel Netco Design versions prior to v2.1.7 contains a relat…4.3
• CVE-2026-105278The published Docker image for openPDC includes a fixed admi…9.8
• CVE-2026-105279In the default configuration, the archive accepts DICOM asso…9.1
• CVE-2026-10528A security flaw has been discovered in Orthanc DICOM Server …3.3
• CVE-2026-105280Improper Validation of Integrity Check Value vulnerability i…6.9
• CVE-2026-105281The internal data publisher on openPDC accepts network conne…7.5