8.1

CVE-2026-42790: erlang erlang\/otp Improper Certificate Validation

CVSS: 8.1v3.1HighModified
AliasesUBUNTU-CVE-2026-42790DEBIAN-CVE-2026-42790
Published 27-05-2026Last modified 18-09-2026

Vulnerability summary

CVE-2026-42790 is a high (CVSS 8.1) Improper Certificate Validation vulnerability in erlang erlang\/otp. EPSS estimates a 0.47% chance of exploitation in the next 30 days, higher than 39.1% of scored vulnerabilities.

Overall risk
32/100
0100
Medium · default modelHow is this calculated?
CVSS score
8.1/10
010
High · v3.1 (NVD)
EPSS score
0.47%
0%100%
Low · +0.13 pp in 30 days
KEVNot listedIn no KEV catalog
RansomwareNone recordedNo known use recorded
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 10 · Related 7

Timeline

  1. 27-05-2026
    PublishedVulnerability first disclosed.
  2. 18-09-2026
    Last modifiedVulnerability information updated.

Description

Improper Certificate Validation vulnerability in Erlang OTP public_key (pubkey_cert and public_key modules) allows a DNS nameConstraints bypass via subject CommonName fallback in TLS hostname verification. Two flaws combine to allow a subordinate CA whose DNS nameConstraints are restricted (e.g. permitted;DNS:allowed.example.com) to issue a leaf certificate that an OTP TLS client accepts as a valid identity for an out-of-scope hostname (e.g. victim.example.com): First, pubkey_cert:validate_names/6 in lib/public_key/src/pubkey_cert.erl only checks SAN DNS entries against nameConstraints. Per RFC 5280, a permitted DNS subtree only restricts certificates that contain a DNS-typed name. A leaf with no subjectAltName therefore trivially satisfies any permitted;DNS:... constraint regardless of its subject commonName. Second, public_key:pkix_verify_hostname/3 in lib/public_key/src/public_key.erl falls back to the subject commonName when no subjectAltName is present, extracting id-at-commonName attributes as presented IDs and matching them against the reference hostname. The strict pkix_verify_hostname_match_fun(https) matcher does not suppress this fallback. The result is that path validation accepts a CN-only leaf under a DNS-constrained intermediate (no SAN means the nameConstraints are not triggered), and hostname verification then accepts it via the CN fallback. The bypass is reachable from stock ssl:connect with verify_peer, a trusted CA, SNI, and the canonical strict https hostname matcher. This issue affects OTP from OTP 19.3 before OTP 29.0.1, OTP 28.5.0.1, OTP 27.3.4.12 and OTP 26.2.5.21, corresponding to public_key from 1.4 before 1.21.1, 1.20.3.1, 1.17.1.3 and 1.15.1.7.

CVSS metrics

7 scores · 4 sources · 2 versions

EPSS trend

Probability

0.47%

Chance of exploitation in the next 30 days

Percentile

39%

Versus all other CVEs

30-day change

+0.13 pp

From 0.34% on 18-09-2026

18-09-202618-10-2026
EPSS score
0.47%

Known exploited

Compare KEV catalogs

Not in any of the 3 tracked catalogs.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Erlang2 products
  • erlang\/otp≥ 19.3, < 26.2.5.21 | ≥ 27.0, < 27.3.4.12 | ≥ 28.0, < 28.5.0.1 | ≥ 29.0, < 29.0.1
  • otp≥ 1.4 (No fix recorded) | ≥ 19.3 (No fix recorded) | ≥ b0c245e8132bb13171e277b1af59c0cec00c9459 (No fix recorded)
Debian1 product
  • erlangAll versions (No fix recorded) | < 1:27.3.4.1+dfsg-1+deb13u3 | < 1:27.3.4.12+dfsg-1
Ubuntu1 product
  • erlang< 1:20.2.2+dfsg-1ubuntu2+esm4 | < 1:22.2.7+dfsg-1ubuntu0.5+esm3 | < 1:24.2.1+dfsg-1ubuntu0.8 | < 1:25.3.2.8+dfsg-1ubuntu4.8 | All versions (No fix recorded) | < 1:27.3.4.6+dfsg-1ubuntu0.2

3 vendors · 4 products

References

17 links
Show all 17 references