CVE-2026-42789

MEDIUMNVD 4.84.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This medium-severity CVE scores 4.8 under NVD CVSS v3. EPSS exploit probability: 0.4% (32nd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2026-32272 (ENISA EUVD)Source: ENISA EUVD

4.8EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 4.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Improper Following of a Certificate's Chain of Trust vulnerability in Erlang OTP public_key (pubkey_cert module) allows a non-CA certificate to be accepted as an intermediate issuer, enabling certificate chain forgery.

In lib/public_key/src/pubkey_cert.erl, pubkey_cert:validate_extensions/7 contains two flaws that together allow a certificate with basicConstraints cA:false and no keyUsage extension to be used as an intermediate issuer in a chain passed to public_key:pkix_path_validation/3: the cA:false clause recurses into the remaining extensions without rejecting the certificate when it is in issuer position, and the keyUsage check only fires when the extension is present, so a certificate lacking keyUsage entirely bypasses the keyCertSign enforcement.

Any party holding an end-entity certificate with basicConstraints cA:false and no keyUsage extension, issued by any CA in the victim's trust store, can use that certificate's private key to sign forged leaf certificates for arbitrary identities. public_key:pkix_path_validation/3 accepts the resulting chain, and by extension every TLS or mTLS endpoint built on the OTP ssl application that relies on the default verifier is affected, including server identity verification on the client side and client certificate verification on mTLS servers.

This issue affects OTP from OTP 17.0 before OTP 27.3.4.19, OTP 28.5.0.8, and OTP 29.1.2, corresponding to public_key from 0.22 before 1.17.1.7, 1.20.3.6, and 1.21.8. Whether OTP before OTP 17.0, corresponding to public_key before 0.22, is affected is unknown.

CVSS v3
4.8
EG Score
4.8MEDIUMmedium confidence
EG Risk
22
EG Risk 22/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity48% × 45%
Impact severity (EG Severity): CVSS 4.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
32nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (4.8): severity, escalated by confirmed exploitation. This CVE's 4.8 is its impact severity (EG Severity), not escalated.

EG Severity
4.8 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-28). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 27, 2026

Last Modified

October 26, 2026

Advisory Details (6)

Auto-updated Jun 15, 2026
Patch available. Sources: github_commit, github.
Web page

Versions — Erlang System Documentation v29.0.2

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

OSV - Open Source Vulnerabilities

https://osv.dev/vulnerability/EEF-CVE-2026-42789
GitHub advisoryMentions a patch (unverified)

public_key Accepts non-CA Certificate as Intermediate Issuer, Enabling Chain Forgery · Advisory · erlang/otp · GitHub

https://github.com/erlang/otp/security/advisories/GHSA-c99q-jmpx-v8qq
GitHub commit

commit 59c8d824386b (erlang/otp)

Fix landed in erlang/otp commit 59c8d824386b — awaiting tagged release

https://github.com/erlang/otp/commit/59c8d824386b2eb1614ff9340624843ef6aca0fd
GitHub commit

commit 471cd2f66430 (erlang/otp)

Fix landed in erlang/otp commit 471cd2f66430 — awaiting tagged release

https://github.com/erlang/otp/commit/471cd2f664300a95353c467873800bbe706005db
Web page

Non-CA certificate accepted as intermediate issuer in public_key path validation | Erlang Ecosystem Foundation CNA

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhaterlang27-main-27.3.4.17-1.hum12026-09-03redhat
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 rangeFix by version rangeDependents
erlang1:23.2.6+dfsg-1 ... 1:29.0~rc3+dfsg-4 (117 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
erlang1:25.2.3+dfsg-1 ... 1:29.1.1+dfsg-1 (80 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
erlang1:27.3.4.1+dfsg-1, 1:27.3.4.1+dfsg-1+deb13u1, 1:27.3.4.1+dfsg-1+deb13u2
  • every version up to 1:27.3.4.1+dfsg-1+deb13u3: fixed in 1:27.3.4.1+dfsg-1+deb13u3
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
erlang1:27.3.4.1+dfsg-1 ... 1:27.3.4.9+dfsg-1 (14 versions)
  • every version up to 1:27.3.4.12+dfsg-1: fixed in 1:27.3.4.12+dfsg-1
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 43× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 251 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 151 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-42789?
CVE-2026-42789 is a medium-severity vulnerability; its CVE record was published on May 27, 2026. Improper Following of a Certificate's Chain of Trust vulnerability in Erlang OTP publickey (pubkeycert module) allows a non-CA certificate to be accepted as an intermediate issuer, enabling certificate chain forgery. In lib/publickey/src/pubkeycert.erl, pubkeycert:validateextensions/7 contains two…
When was CVE-2026-42789 made public?
CVE-2026-42789 was made public on May 27, 2026: that is the date its CVE record's CNA, Erlang Ecosystem Foundation, gives for when the vulnerability was made public. The CVE record itself was published on May 27, 2026. EchelonGraph's copy of the record carries a last-modified date of October 26, 2026; the record at its source may have been updated since.
Is CVE-2026-42789 actively exploited?
CVE-2026-42789 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-42789?
CVE-2026-42789 has a CVSS v3 base score of 4.8 (NVD).
How do I remediate CVE-2026-42789?
A fix for CVE-2026-42789 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-42789 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-42789?

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