Skip to content
Threat Brief

← All advisories

CVE-2026-103503

Medium 5.9No known exploitationFix available

Hex trusts its bundled CA certificates when cacerts_path is set

Record last updated

CVSS score

5.9

Medium on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.2%

Higher than 11% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

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.

Weakness: CWE-295

Patching and mitigation

Patch status
Fix available (source: CVE record (EEF))
Fix documented (source date)
Vendor solution
Upgrade Hex to 2.5.2 or later, for example with mix local.hex. With cacerts_path (HEX_CACERTS_PATH) set, Hex then only accepts server certificates that chain to a CA in that file, and it doesn't trust copies of CA certificates sent by the server.
Mitigation
There's no Hex configuration that stops the bundled CAs from being trusted. Source (opens in a new tab)
Vendor guidance
github.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
hexpmhexfrom 0.20.2 before 2.5.22.5.2CVE Program
hexpmhexc9b26a46928bfcd546773571e09c1d05f4cd9fb7Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by EEF

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (EEF)

    Source: CVE record (EEF) (opens in a new tab)

Vendor guidance and references