CVE-2026-89422

CRITICALPre-NVD 9.39.3
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (40th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

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

9.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Key Exchange without Entity Authentication vulnerability in Erlang/OTP ssl allows a peer that answers a TLS 1.3 client connection to impersonate the intended server. A pre_shared_key extension in the ServerHello that the client never offered causes the client to complete the handshake without validating the server's certificate, so ssl:connect returns {ok, Socket} against a peer holding no certificate, no private key and no prior session.

tls_client_connection_1_3:handle_server_hello/2 passes the received extension to tls_gen_connection_1_3:handle_resumption/2, which sets resumption = true on its mere presence without checking that the client offered a PSK. tls_handshake_1_3:get_pre_shared_key/4 meanwhile falls back to the all-zero "no PSK" value and keys the handshake with the ordinary non-PSK schedule, so the attacker's own ephemeral key suffices. The resumption flag then routes maybe_resumption/1 straight to wait_finished, skipping the certificate-handling states, so certificate path validation, verify_fun, hostname verification, partial_chain, CRL checking and OCSP stapling are all bypassed. The default client configuration is affected; clients restricted to TLS 1.2 are not.

This issue affects OTP from OTP 22.2 before OTP 27.3.4.18, OTP 28.5.0.7, and OTP 29.1.1, corresponding to ssl from 9.5 before 11.2.12.13, 11.6.0.6, and 11.7.7.

CVSS
9.3
EG Score
9.3CRITICALmedium confidence
EG Risk
57
EG Risk 57/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)
Severity93% × 45%
Impact severity (EG Severity): CVSS 9.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
40th
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 (9.3): severity, escalated by confirmed exploitation. This CVE's 9.3 is its impact severity (EG Severity), not escalated.

EG Severity
9.3 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). 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 low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (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

September 22, 2026

Last Modified

November 20, 2026

Advisory Details (8)

Auto-updated Oct 3, 2026
Patch available. Sources: github_commit, github.
Web page

Versions — Erlang System Documentation v29.1.1

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

OSV - Open Source Vulnerabilities

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

TLS 1.3 Client Skips Server Authentication on Unsolicited PSK · Advisory · erlang/otp · GitHub

https://github.com/erlang/otp/security/advisories/GHSA-rgxr-4g4w-j875
GitHub commit

commit fd1d9d07fc92 (erlang/otp)

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

https://github.com/erlang/otp/commit/fd1d9d07fc92ec0d59f96dfb66182195882bb7dd
GitHub commit

commit afec5156361b (erlang/otp)

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

https://github.com/erlang/otp/commit/afec5156361bb50d3607c7c1a453c19b9149b324
GitHub commit

commit 98c66c858113 (erlang/otp)

Fix landed in erlang/otp commit 98c66c858113 — awaiting tagged release

https://github.com/erlang/otp/commit/98c66c858113949c4262d26cd7d426c4b09d2b35
GitHub commit

commit 21b8a1b0ad0a (erlang/otp)

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

https://github.com/erlang/otp/commit/21b8a1b0ad0adf200682b3854bc50114ab2b8c62

Vendor Advisories for CVE-2026-89422(1)

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

Affected Packages

(3 across 3 ecosystems)
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, 1:27.3.4.1+dfsg-1+deb13u3
  • every version up to 1:27.3.4.1+dfsg-1+deb13u4: fixed in 1:27.3.4.1+dfsg-1+deb13u4
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
erlang1:27.3.4.1+dfsg-1 ... 1:29.0~rc3+dfsg-4 (37 versions)
  • every version up to 1:29.1.1+dfsg-1: fixed in 1:29.1.1+dfsg-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 49× 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 its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 246 rows 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 146 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-89422?
CVE-2026-89422 is a critical-severity vulnerability; its CVE record was published on September 22, 2026. Key Exchange without Entity Authentication vulnerability in Erlang/OTP ssl allows a peer that answers a TLS 1.3 client connection to impersonate the intended server. A pre_shared_key extension in the ServerHello that the client never offered causes the client to complete the handshake without…
When was CVE-2026-89422 made public?
CVE-2026-89422 was made public on September 22, 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 September 22, 2026. EchelonGraph's copy of the record carries a last-modified date of November 20, 2026; the record at its source may have been updated since.
Is CVE-2026-89422 actively exploited?
CVE-2026-89422 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (40th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-89422?
CVE-2026-89422 has a CVSS base score of 9.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-89422?
A fix for CVE-2026-89422 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-89422 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-89422

Explore →

Is Your Infrastructure Affected by CVE-2026-89422?

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