CVSS 4.0
2.1 lowCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:N/VI:N/VA:L/SC:N/SI:N/SA:NLow (2.1). EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in hex_core 0.20.0.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:N/VI:N/VA:L/SC:N/SI:N/SA:Nhex_core (Hex): fixed in 0.20.0Explain CVE-2026-105274 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-105274?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-105274?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-105274 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| hexpm hex_core | from 0.1.0 before 0.20.0 |
| erlang rebar3 | from 3.9.1 before 3.27.3 |
| hexpm hex | from 2.1.0 before 2.5.2 |
| hexpm hex | 2.6.0 and later |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| EEF-CVE-2026-105274 | Hex | hex_core | >=0.1.0 <0.20.0 | 0.20.0 |
| EEF-CVE-2026-105274 | no fix published | |||
| EEF-CVE-2026-105274 | 3.27.1, 3.27.0, 3.26.0, 3.25.1, 3.25.0 and 24 more | no fix published | ||
| EEF-CVE-2026-105274 | v2.5.1, v2.5.0, v2.2.2, v2.4.2, v2.4.1 and 5 more | no fix published |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13 | rebar3 | no fix listed | DEBIAN-CVE-2026-105274 |
| Debian | 14 | erlang-hex | 2.5.3-2 | DEBIAN-CVE-2026-105274 |
| Debian | 14 | rebar3 | 3.27.3-1 | DEBIAN-CVE-2026-105274 |
| Ubuntu | 22.04:LTS | rebar3 | no fix listed | UBUNTU-CVE-2026-105274 |
| Ubuntu | 24.04:LTS, 26.04:LTS, 26.10 | rebar3, erlang-hex | no fix listed | UBUNTU-CVE-2026-105274 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.
Red Hat rates this Low.
This vulnerability is rated as Low impact because exploitation requires control of a repository mirror or man-in-the-middle network position, and the affected components run within transient build tools rather than persistent production services. Memory exhaustion crashes the Erlang VM running the build, but recovery requires only restarting the process against a trusted mirror. Red Hat Enterprise Linux does not ship hex_core or rebar3 in supported product channels; exposure is limited to Fedora community packages in developer environments.
Configure build tools to fetch packages only from trusted, official registry endpoints. Avoid configuring untrusted third-party repository mirrors.
Ensure the HEX_MIRROR_URL environment variable is unset or points to a trusted, internal mirror over verified HTTPS. Note that HTTPS protects against man-in-the-middle injection but does not protect against a compromised mirror serving malicious responses directly.
Environments that depend on third-party mirrors cannot fully mitigate this vulnerability if those mirrors are untrusted, as any mirror can craft compressed responses that trigger memory exhaustion during dependency resolution.
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-105274.