cve.bz

CVE-2026-103503 Hex trusts its bundled CA certificates when cacerts_path is set

5.9 mediumEPSS 0.2%

Medium (5.9) in hexpm hex. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
Improper Certificate Validation vulnerability in hexpm hex allows an attacker who can intercept HTTPS connections, and holds a certificate for a Hex host issued by a CA in Hex's bundled CA store, to impersonate that host to users who set cacerts_path to a CA store that leaves that CA out. cacerts_path (HEX_CACERTS_PATH) is documented as the path to the CA certificate store, used instead of the CA bundle that ships with Hex. Hex.HTTP.SSL.ssl_opts/1 passes the configured store as the cacerts option, but builds the partial_chain callback from the bundled store whether cacerts_path is set or not. Hex.HTTP.SSL.partial_chain/2 accepts a server chain when any certificate in it has the same public key as a bundled CA certificate, so a chain that leads to a bundled CA passes verification although the configured store doesn't contain that CA. Hostname verification still applies. This issue affects hex: from 0.20.2 before 2.5.2.

Severity

CVSS 4.0

5.9 medium
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:A/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 11th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-295 Improper Certificate Validation
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
Assigned by
EEF (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-103503 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-103503?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-103503?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-103503 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.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
hexpm hexfrom 0.20.2 before 2.5.2

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian13erlang-hexno fix listedDEBIAN-CVE-2026-103503
Debian14erlang-hex2.5.3-2DEBIAN-CVE-2026-103503
Ubuntu24.04:LTS, 26.04:LTS, 26.10erlang-hexno fix listedUBUNTU-CVE-2026-103503

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

Red Hat rates this Moderate.

Red Hat's statement

hex, the package manager for the Erlang/Elixir ecosystem, is affected by a moderate-impact improper certificate validation vulnerability in Red Hat's community offerings. When a custom CA certificate store is configured via cacerts_path (HEX_CACERTS_PATH) to restrict which certificate authorities are trusted, Hex continues to validate server certificate chains against the CA bundle that ships with Hex, because the partial_chain callback is built from the bundled store regardless of the configuration. As a result, a network attacker who can intercept HTTPS connections and who holds a certificate for a Hex host issued by one of the bundled CAs can impersonate that host to clients whose custom store omits that CA; hostname verification still applies. Successful impersonation allows the attacker to capture the API keys, OAuth tokens, and repository keys that Hex transmits and to alter API responses, although registry signatures and package checksums continue to prevent changes to registry contents and packages. Only users who set cacerts_path to a store that leaves out some of the bundled CAs are exposed; users who rely on the default bundled store are not affected. Red Hat and upstream both rate this flaw moderate severity (Red Hat CVSS 6.8, upstream 5.9). This flaw is recorded as affecting Red Hat community offerings (Fedora and EPEL streams) and a fix is being pursued through the community delegation process.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

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-103503.

Attack patterns (CAPEC)

  • CAPEC-459 Creating a Rogue Certification Authority Certificate Likelihood: Medium · Severity: Very High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON