CVE-2026-42790

HIGHNVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 73% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 4 sources updated this week
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.1Exploit: None knownExposed: 0

A fix is available — apply it.

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 v3
8.1
EG Score
8.1(medium)
EG Risk
37(Track)
EG Risk 37/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity81% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
27%
KEV
Not listed

Published

May 27, 2026

Last Modified

August 14, 2026

Advisory Details (7)

Auto-updated Jun 3, 2026
Patch available. Sources: github_commit, github.
generic

Versions — Erlang System Documentation v29.0.1

https://www.erlang.org/doc/system/versions.html#order-of-versions
generic

OSV - Open Source Vulnerabilities

https://osv.dev/vulnerability/EEF-CVE-2026-42790
github Patch Available

Name Constraints and Subject CommonName Fallback in TLS hostname Verification · Advisory · erlang/otp · GitHub

https://github.com/erlang/otp/security/advisories/GHSA-22cw-4ph4-6447
github_commit

commit fb67c6d1836f (erlang/otp)

Fix landed in erlang/otp commit fb67c6d1836f — awaiting tagged release

https://github.com/erlang/otp/commit/fb67c6d1836f51105a96d8b769e71e4215a79457
github_commit

commit 21abed64eb20 (erlang/otp)

Fix landed in erlang/otp commit 21abed64eb20 — awaiting tagged release

https://github.com/erlang/otp/commit/21abed64eb2026b5f82f432709e4e932f9be389a
github_commit

commit 0769050c69d7 (erlang/otp)

Fix landed in erlang/otp commit 0769050c69d7 — awaiting tagged release

https://github.com/erlang/otp/commit/0769050c69d73762672b0db1347b6993a5b31759
generic

nameConstraints DNS bypass via subject CommonName fallback in public_key hostname verification | Erlang Ecosystem Foundation CNA

https://cna.erlef.org/cves/CVE-2026-42790.html

Vendor Advisories for CVE-2026-42790(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhaterlang-0:23.3.4.18-2.el8ost2026-08-13redhat
redhaterlang-0:26.2.5.21-2.el9ost2026-07-15redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
erlang1:23.2.6+dfsg-1 ... 1:29.0~rc3+dfsg-4 (117 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
erlang1:25.2.3+dfsg-1 ... 1:29.0~rc3+dfsg-4 (78 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
erlang1:27.3.4.1+dfsg-1, 1:27.3.4.1+dfsg-1+deb13u1, 1:27.3.4.1+dfsg-1+deb13u21:27.3.4.1+dfsg-1+deb13u3—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
erlang1:27.3.4.1+dfsg-1 ... 1:27.3.4.9+dfsg-1 (14 versions)1:27.3.4.12+dfsg-1—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 9× in last 7d / 37× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 221 total refreshes for this CVE.

  1. 2026-09-16 05:15 UTCEPSS rescore
  2. 2026-09-14 07:38 UTCEG score recompute
  3. 2026-09-14 07:38 UTCVendor advisory
  4. 2026-09-13 16:47 UTCEPSS rescore
  5. 2026-09-13 03:09 UTCOSV refresh
  6. 2026-09-12 15:01 UTCEPSS rescore
  7. 2026-09-11 14:53 UTCEPSS rescore
  8. 2026-09-11 09:37 UTCEPSS rescore
  9. 2026-09-10 09:34 UTCEPSS rescore
  10. 2026-09-08 22:00 UTCEPSS rescore
  11. 2026-09-07 16:01 UTCEPSS rescore
  12. 2026-09-06 13:47 UTCEPSS rescore
  13. 2026-09-04 05:06 UTCEPSS rescore
  14. 2026-09-02 14:12 UTCEPSS rescore
  15. 2026-09-01 13:54 UTCEPSS rescore
  16. 2026-08-30 19:17 UTCEPSS rescore
  17. 2026-08-30 01:22 UTCEPSS rescore
  18. 2026-08-28 21:41 UTCEPSS rescore
  19. 2026-08-27 14:25 UTCEPSS rescore
  20. 2026-08-26 14:46 UTCEPSS rescore
  21. 2026-08-25 13:49 UTCEPSS rescore
  22. 2026-08-25 05:15 UTCEG score recompute
  23. 2026-08-25 05:15 UTCVendor advisory
  24. 2026-08-23 14:59 UTCEG score recompute
  25. 2026-08-23 14:59 UTCVendor advisory
Show 75 more
  1. 2026-08-23 00:19 UTCEPSS rescore
  2. 2026-08-21 23:49 UTCEPSS rescore
  3. 2026-08-21 20:32 UTCVendor advisory
  4. 2026-08-21 01:29 UTCEG score recompute
  5. 2026-08-21 01:29 UTCVendor advisory
  6. 2026-08-20 22:55 UTCEPSS rescore
  7. 2026-08-20 11:17 UTCEG score recompute
  8. 2026-08-20 11:17 UTCVendor advisory
  9. 2026-08-19 17:03 UTCEPSS rescore
  10. 2026-08-18 13:48 UTCEPSS rescore
  11. 2026-08-17 13:47 UTCEPSS rescore
  12. 2026-08-17 09:15 UTCVendor advisory
  13. 2026-08-16 15:13 UTCEG score recompute
  14. 2026-08-16 15:13 UTCVendor advisory
  15. 2026-08-16 14:56 UTCEPSS rescore
  16. 2026-08-16 02:48 UTCEG score recompute
  17. 2026-08-16 02:48 UTCVendor advisory
  18. 2026-08-16 02:14 UTCEPSS rescore
  19. 2026-08-15 01:30 UTCEPSS rescore
  20. 2026-08-15 01:09 UTCVendor advisory
  21. 2026-08-14 13:27 UTCVendor advisory
  22. 2026-08-14 12:29 UTCVendor advisory
  23. 2026-08-14 01:25 UTCEG score recompute
  24. 2026-08-14 01:25 UTCVendor advisory
  25. 2026-08-13 22:00 UTCEPSS rescore
  26. 2026-08-13 01:35 UTCVendor advisory
  27. 2026-08-12 13:53 UTCEG score recompute
  28. 2026-08-12 13:53 UTCVendor advisory
  29. 2026-08-12 13:51 UTCEPSS rescore
  30. 2026-08-12 01:17 UTCEG score recompute
  31. 2026-08-12 01:17 UTCVendor advisory
  32. 2026-08-11 13:43 UTCEPSS rescore
  33. 2026-08-11 13:34 UTCVendor advisory
  34. 2026-08-11 00:11 UTCEG score recompute
  35. 2026-08-11 00:11 UTCVendor advisory
  36. 2026-08-11 00:00 UTCEPSS rescore
  37. 2026-08-10 08:22 UTCVendor advisory
  38. 2026-08-09 20:39 UTCEG score recompute
  39. 2026-08-09 20:39 UTCVendor advisory
  40. 2026-08-09 13:46 UTCEPSS rescore
  41. 2026-08-09 08:57 UTCVendor advisory
  42. 2026-08-08 21:15 UTCEG score recompute
  43. 2026-08-08 21:15 UTCVendor advisory
  44. 2026-08-08 16:37 UTCEPSS rescore
  45. 2026-08-08 07:23 UTCVendor advisory
  46. 2026-08-07 19:41 UTCEG score recompute
  47. 2026-08-07 19:41 UTCVendor advisory
  48. 2026-08-07 07:59 UTCVendor advisory
  49. 2026-08-06 20:16 UTCEG score recompute
  50. 2026-08-06 20:16 UTCVendor advisory
  51. 2026-08-06 13:46 UTCEPSS rescore
  52. 2026-08-06 08:34 UTCVendor advisory
  53. 2026-08-05 20:52 UTCEG score recompute
  54. 2026-08-05 20:52 UTCVendor advisory
  55. 2026-08-05 19:17 UTCEPSS rescore
  56. 2026-08-04 15:10 UTCEPSS rescore
  57. 2026-08-04 10:38 UTCEPSS rescore
  58. 2026-08-04 04:08 UTCVendor advisory
  59. 2026-08-03 16:26 UTCEG score recompute
  60. 2026-08-03 16:26 UTCVendor advisory
  61. 2026-08-03 10:36 UTCEPSS rescore
  62. 2026-08-03 02:18 UTCVendor advisory
  63. 2026-08-02 14:36 UTCVendor advisory
  64. 2026-08-02 02:53 UTCEG score recompute
  65. 2026-08-02 02:53 UTCVendor advisory
  66. 2026-08-02 02:27 UTCEPSS rescore
  67. 2026-08-01 15:10 UTCEG score recompute
  68. 2026-08-01 15:10 UTCVendor advisory
  69. 2026-08-01 04:16 UTCEPSS rescore
  70. 2026-07-31 07:29 UTCEG score recompute
  71. 2026-07-31 07:29 UTCVendor advisory
  72. 2026-07-30 16:28 UTCEPSS rescore
  73. 2026-07-30 01:30 UTCEPSS rescore
  74. 2026-07-29 15:03 UTCEG score recompute
  75. 2026-07-29 15:03 UTCVendor advisory

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-42790?
CVE-2026-42790 is a high vulnerability published on May 27, 2026. Improper Certificate Validation vulnerability in Erlang OTP publickey (pubkeycert 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.…
When was CVE-2026-42790 disclosed?
CVE-2026-42790 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on August 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-42790 actively exploited?
CVE-2026-42790 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 73.0% of all scored CVEs.
What is the CVSS score of CVE-2026-42790?
CVE-2026-42790 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-42790?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42790, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-42790

Explore →

Is Your Infrastructure Affected by CVE-2026-42790?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs