---
id: CVE-2026-105274
title: >-
  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_cor…
summary: >-
  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_cor…
severity: none
cwe:
  - CWE-409
published: '2026-10-12'
updated: '2026-10-12'
sourceUpdated: '2026-10-12T19:16:37.157'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-105274'
references:
  - url: 'https://cna.erlef.org/cves/CVE-2026-105274.html'
    label: 6b3ad84c-e1a6-4bf7-a703-f496b71e49db
  - url: >-
      https://github.com/erlang/rebar3/commit/209c02ec57c2cc3207ee0174c3af3675b8dc8f79
    label: 6b3ad84c-e1a6-4bf7-a703-f496b71e49db
  - url: >-
      https://github.com/erlang/rebar3/commit/360838a22f5b3a88c0358207f2923059bcbb3afb
    label: 6b3ad84c-e1a6-4bf7-a703-f496b71e49db
  - url: >-
      https://github.com/hexpm/hex/commit/671f695ac548ed01f5828c2a739ecaa942b21007
    label: 6b3ad84c-e1a6-4bf7-a703-f496b71e49db
  - url: >-
      https://github.com/hexpm/hex/commit/d8b60eee97abb119d525306f048969a217d793a5
    label: 6b3ad84c-e1a6-4bf7-a703-f496b71e49db
  - url: >-
      https://github.com/hexpm/hex_core/commit/ebe25d110717f6a3addba5232cd4a7dc1c76b628
    label: 6b3ad84c-e1a6-4bf7-a703-f496b71e49db
  - url: >-
      https://github.com/hexpm/hex_core/commit/fbb6d9de472e5edb8d6fb6b32a91cb266137892e
    label: 6b3ad84c-e1a6-4bf7-a703-f496b71e49db
  - url: 'https://github.com/hexpm/hex_core/security/advisories/GHSA-7c4r-cgf9-9jmq'
    label: 6b3ad84c-e1a6-4bf7-a703-f496b71e49db
  - url: 'https://osv.dev/vulnerability/EEF-CVE-2026-105274'
    label: 6b3ad84c-e1a6-4bf7-a703-f496b71e49db
tags:
  - nvd
ingestedAt: '2026-10-12T18:00:08.167Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.