Skip to main content
CVE-2026-103503VulnerabilityPublished Updated

Erlang hex: Improper Certificate Validation vulnerability

Affects erlang-hexSource GCVE Database

0
Authoritative record:CVE-2026-103503· Medium 5.9

Not known to be exploited · CVSS 5.9 Medium.

Data as of 28 Oct 2026, 22:31 UTC

CVSS 4.0 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Ubuntu 26.10erlang-hexpkg:deb/ubuntu/erlang-hex?arch=source&distro=stonkingOther threatsAffected
  • =2.0.6-2build1
  • =2.5.1-2
Fixed in–
Ubuntu 26.04 LTSerlang-hexpkg:deb/ubuntu/erlang-hex?arch=source&distro=resoluteOther threatsAffected
  • =2.0.6-2
  • =2.0.6-2build1
Fixed in–
Ubuntu 24.04 LTSerlang-hexpkg:deb/ubuntu/erlang-hex?arch=source&distro=nobleOther threatsAffected
  • =2.0.5-1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

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.

References

Community reviews

Loading reviews…