CVE-2026-21619: Unsafe Deserialization of Erlang Terms in hex_core

Published Feb 27, 2026
·
Updated

### Impact The Hex client (`hex_core`) deserializes Erlang terms received from the Hex API using `binary_to_term/1` without sufficient restrictions. If an attacker can control the HTTP response body returned by the Hex API, this allows denial-of-service attacks such as **atom table exhaustion**, leading to a VM crash. No released versions are known to allow remote code execution. ### Patches * https://github.com/hexpm/hex_core/commit/cdf726095bca85ad2549d146df1e831ae93c2b13 * https://github.com/hexpm/hex/commit/636739f3322514e9303ca335fb630696fcbb3c95 * https://github.com/erlang/rebar3/commit/1d4478f527e373de0b225951e53115450e0d9b9d ### Workarounds Ensure that the Hex API URL (`HEX_API_URL`) points only to trusted endpoints. There is no client-side workaround that fully mitigates this issue without applying the patch. ### Resources * hex_core Module: https://github.com/hexpm/hex_core/blob/main/src/hex_api.erl * Hex Vendored Module: https://github.com/hexpm/hex/blob/main/src/mix_hex_api.erl * Rebar3 Vendored Module: https://github.com/erlang/rebar3/blob/main/apps/rebar/src/vendored/r3_hex_api.erl * hex_core Patch: https://github.com/hexpm/hex_core/commit/cdf726095bca85ad2549d146df1e831ae93c2b13 * Hex Vendored Patch: https://github.com/hexpm/hex/commit/636739f3322514e9303ca335fb630696fcbb3c95 * Rebar3 Vendored Patch: https://github.com/erlang/rebar3/commit/1d4478f527e373de0b225951e53115450e0d9b9d

Affected Software

7 affected componentsFixes available
hexpm/hex_core>=0.1.0<0.12.1
hexpm/hex>=2.3.0<2.3.2
erlang/rebar3>=3.9.1<3.27.0
erlang/hex_core<0.12.1
0.12.1
Erlang Rebar3>=3.9.1<3.27.0
Hex Hex>=2.3.0<2.3.2
Hex Hex Core>=0.1.0<0.12.1

Event History

Feb 27, 2026
CVE Published
via MITRE·05:57 PM
Data Sourced
via MITRE·05:57 PM
DescriptionWeakness
Data Sourced
via NVD·06:16 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:16 PM
RemedyAffected Software
Mar 1, 2026
Advisory Published
via GitHub·01:25 AM
Data Sourced
via GitHub·01:25 AM
DescriptionWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-21619?

CVE-2026-21619 is categorized as a critical vulnerability due to its potential for object injection and excessive resource consumption.

2

How do I fix CVE-2026-21619?

To mitigate CVE-2026-21619, update hex_core to version 0.12.1 or later, hex to version 2.3.2 or later, and rebar3 to version 3.27.0 or later.

3

What types of attacks can exploit CVE-2026-21619?

CVE-2026-21619 can be exploited to perform object injection attacks and cause uncontrolled resource consumption.

4

Which software is affected by CVE-2026-21619?

CVE-2026-21619 affects hex_core, hex, and rebar3 across specific version ranges.

5

What is the nature of the vulnerability in CVE-2026-21619?

CVE-2026-21619 is caused by unsafe deserialization of Erlang terms, allowing untrusted data to affect the application.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203