CVSS 4.0
5.9 mediumCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:L/VA:N/SC:N/SI:N/SA:NMedium (5.9) in hexpm hex core. EPSS 0.2% 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:H/VI:L/VA:N/SC:N/SI:N/SA:Nhex_core (Hex): fixed in 0.20.0Explain CVE-2026-103502 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-103502?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-103502?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-103502 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 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| EEF-CVE-2026-103502 | Hex | hex_core | >=0.1.0 <0.20.0 | 0.20.0 |
| EEF-CVE-2026-103502 | no fix published |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 13 | erlang-hex | no fix listed | DEBIAN-CVE-2026-103502 |
| Debian | 14 | erlang-hex | 2.5.3-2 | DEBIAN-CVE-2026-103502 |
| Ubuntu | 22.04:LTS | rebar3 | no fix listed | UBUNTU-CVE-2026-103502 |
| Ubuntu | 24.04:LTS, 26.04:LTS, 26.10 | rebar3, erlang-hex | no fix listed | UBUNTU-CVE-2026-103502 |
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 Moderate.
A moderate-impact vulnerability was found in hex_core, the Erlang/Elixir client library for the Hex package repository. hex_core's default HTTP adapter, hex_http_httpc, does not verify TLS server certificates when running on Erlang/OTP 24, or on OTP 25 when the operating system's CA certificates cannot be loaded: when the adapter cannot build certificate-verification options, it falls back to the ssl application's insecure connection defaults rather than aborting the request. A network attacker able to intercept HTTPS connections could exploit this to impersonate hex.pm or other repository and API servers, capture sensitive information sent by client programs such as API keys, OAuth tokens, and repository keys, and alter API requests and responses. Registry signatures, which hex_core verifies by default, still prevent changes to registry package contents, so package contents cannot be tampered with. Red Hat rates this flaw as Moderate severity, consistent with the upstream Medium rating. No Red Hat products are currently listed as affected by this flaw.
Users of the default hex_http_httpc adapter can work around this issue by configuring SSL options that verify the server certificate (for example, verify_peer with a trusted CA certificate store) in the adapter's http_options, such as {hex_http_httpc, #{http_options => [{ssl, SslOpts}]}}, by using an alternative HTTP adapter that performs certificate verification, or by running on Erlang/OTP 26 or later, where the ssl application verifies server certificates by default. Upgrading hex_core to version 0.20.0 or later, where HTTPS requests fail rather than fall back to insecure defaults when CA certificates are unavailable, resolves the issue.
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-103502.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.