PoC Monitor
← All CVEs
CVE-2026-89422published 22 Sep 2026 08:49 UTCData: JSON · API

Erlang OTP

TLS 1.3 client skips server authentication when ServerHello carries an unsolicited pre_shared_key extension

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.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS9.3critical · scored by CNA · CWE-322
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Erlang OTP
  • >= 9.5, < *

Fixed in *, 11.2.12.13, 11.6.0.6, 11.7.7

Erlang OTP
  • >= 22.2, < *

Fixed in *, 27.3.4.18, 28.5.0.7, 29.1.1

Erlang OTP
  • >= 21b8a1b0ad0adf200682b3854bc50114ab2b8c62, < *

Fixed in *, 98c66c858113949c4262d26cd7d426c4b09d2b35, afec5156361bb50d3607c7c1a453c19b9149b324, fd1d9d07fc92ec0d59f96dfb66182195882bb7dd

Mitigation

Upgrade OTP to * or 11.2.12.13 or 11.6.0.6 or 11.7.7 or later.

Upgrade OTP to * or 27.3.4.18 or 28.5.0.7 or 29.1.1 or later.

Upgrade OTP to * or 98c66c858113949c4262d26cd7d426c4b09d2b35 or afec5156361bb50d3607c7c1a453c19b9149b324 or fd1d9d07fc92ec0d59f96dfb66182195882bb7dd or later.

Workaround

Restrict affected clients to TLS 1.2 by setting {versions, ['tlsv1.2']} in the client's ssl options. This avoids the vulnerable code path at the cost of losing TLS 1.3. No configuration both keeps TLS 1.3 and mitigates the issue.

References

2 more

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published22 Sep 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.