CVE-2026-21619: Unsafe Deserialization of Erlang Terms in hex_core
Uncontrolled Resource Consumption, Deserialization of Untrusted Data vulnerability in hexpm hex_core (hex_api modules), hexpm hex (mix_hex_api modules), erlang rebar3 (r3_hex_api modules) allows Object Injection, Excessive Allocation. This vulnerability is associated with program files src/hex_api.erl, src/mix_hex_api.erl, apps/rebar/src/vendored/r3_hex_api.erl and program routines hex_core:request/4, mix_hex_api:request/4, r3_hex_api:request/4.
This issue affects hex_core: from 0.1.0 before 0.12.1; hex: from 2.3.0 before 2.3.2; rebar3: from 3.9.1 before 3.27.0.
Security readout for executives and security teams
Plain-English summary
This is a low-severity issue in Hex/Erlang package tooling. Vulnerable components may deserialize untrusted Erlang terms in API request handling, potentially causing excessive resource allocation. The documented impact is limited availability loss, not data theft or tampering.
Executive priority
Schedule remediation through normal dependency maintenance. Prioritize build and CI environments first. Escalation is not supported by the current evidence unless vulnerable tooling is widely deployed or difficult to update.
Technical view
CVE-2026-21619 affects hex_core before 0.12.1, hex before 2.3.2, and rebar3 before 3.27.0. The affected request routines can process untrusted serialized Erlang terms, mapping to CWE-502 and CWE-400. CVSS 4.0 is 2.0, with low availability impact only.
Likely exposure
Exposure is most likely in Erlang/Elixir development, build, or automation environments using affected hex_core, hex, or rebar3 versions. Public-facing application exposure is not established by the provided sources.
Exploitation context
The bundle does not show CISA KEV listing or active exploitation. CVSS indicates network reachability but also privileges, user interaction, and additional attack requirements. Treat this as a dependency hygiene and build-system resilience issue.
Researcher notes
The public record names specific affected modules and request/4 routines, but the bundle does not provide exploit details. Analysis should focus on deserialization boundaries, resource-allocation behavior, and whether patched commits restrict unsafe term decoding.
Mitigation direction
Upgrade hex_core to 0.12.1 or later.
Upgrade hex to 2.3.2 or later.
Upgrade rebar3 to 3.27.0 or later.
Check the vendor advisory before relying on alternate mitigations.
Pin patched tooling in CI and build images.
Validation and detection
Inventory hex_core, hex, and rebar3 versions across repositories and build environments.
Review lockfiles, build containers, and developer bootstrap scripts for vulnerable versions.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-400: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-400 · source CWE mapping
Uncontrolled Resource Consumption
Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.