Skip to main content
CVE-2026-42790VulnerabilityPublished Updated

Erlang OTP public_key (pubkey_cert · Improper Certificate Validation Vulnerability

Affects erlangSource GCVE Database

0
Compare
Authoritative record:CVE-2026-42790· High 7.6

Not known to be exploited · CVSS 7.6 High · fixed in 1:20.2.2+dfsg-1ubuntu2+esm4 : patch erlang soon.

Data as of 18 Nov 2026, 15:19 UTC

CVSS 4.0 base score
7.6High
How severe the flaw is on the 0–10 CVSS scale.

Sources agree

CVSS scores by source
CNA (EEF)CVSS 4.07.6
ADP (redhat-SADP)CVSS 3.17.4
Patch
Available – fixed in 1:20.2.2+dfsg-1ubuntu2+esm4, 1:22.2.7+dfsg-1ubuntu0.5+esm3, 1:24.2.1+dfsg-1ubuntu0.8 +2
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 17 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
Ubuntu 26.04 LTSerlangpkg:deb/ubuntu/erlang?arch=source&distro=resoluteOther threatsAffected
  • <1:27.3.4.6+dfsg-1ubuntu0.2
Fixed in
  • 1:27.3.4.6+dfsg-1ubuntu0.2
Ubuntu 25.10erlangpkg:deb/ubuntu/erlang?arch=source&distro=questingOther threatsAffected
  • 1:27.3.4.1+dfsg-1 – 1:27.3+dfsg-1ubuntu1.1
5 affected builds
Fixed in–
Ubuntu 24.04 LTSerlangpkg:deb/ubuntu/erlang?arch=source&distro=nobleOther threatsAffected
  • <1:25.3.2.8+dfsg-1ubuntu4.8
Fixed in
  • 1:25.3.2.8+dfsg-1ubuntu4.8
Ubuntu 22.04 LTSerlangpkg:deb/ubuntu/erlang?arch=source&distro=jammyOther threatsAffected
  • <1:24.2.1+dfsg-1ubuntu0.8
  • =1:24.2+dfsg-1
Fixed in
  • 1:24.2.1+dfsg-1ubuntu0.8
Ubuntu Pro 20.04 LTSerlangpkg:deb/ubuntu/erlang?arch=source&distro=esm-infra/focalOther threatsAffected
  • <1:22.2.7+dfsg-1ubuntu0.5+esm3
  • =1:22.2+dfsg-1
Fixed in
  • 1:22.2.7+dfsg-1ubuntu0.5+esm3
Ubuntu Pro 18.04 LTSerlangpkg:deb/ubuntu/erlang?arch=source&distro=esm-infra/bionicOther threatsAffected
  • <1:20.2.2+dfsg-1ubuntu2+esm4
Fixed in
  • 1:20.2.2+dfsg-1ubuntu2+esm4

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 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 26.2.5.21, OTP 27.3.4.12, OTP 28.5.0.1, and OTP 29.0.1, corresponding to public_key from 1.4 before 1.15.1.7, 1.17.1.3, 1.20.3.1, and 1.21.1.

References

Community reviews

Loading reviews…