CVE-2026-89422: TLS 1.3 client skips server authentication when ServerHello carries an unsolicited pre_shared_key extension

Published Sep 22, 2026
·
Updated

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 presharedkey 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.

tlsclientconnection13:handleserverhello/2 passes the received extension to tlsgenconnection13:handleresumption/2, which sets resumption = true on its mere presence without checking that the client offered a PSK. tlshandshake13:getpresharedkey/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 mayberesumption/1 straight to waitfinished, skipping the certificate-handling states, so certificate path validation, verifyfun, hostname verification, partialchain, 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.

Affected Software

2 affected components
Erlang Erlang/OTP>=22.2<27.3.4.18, >=28.0<28.5.0.7, >=29.0<29.1.1
Erlang ssl>=9.5<11.2.12.13, >=11.6.0<11.6.0.6, >=11.7.0<11.7.7

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Erlang/OTP to a version that resolves this vulnerability.

    Fixed in 27.3.4.18
  2. Upgrade

    Upgrade Erlang/OTP to a version that resolves this vulnerability.

    Fixed in 28.5.0.7
  3. Upgrade

    Upgrade Erlang/OTP to a version that resolves this vulnerability.

    Fixed in 29.1.1
  4. Configuration

    Restrict clients to TLS 1.2 as a mitigation; clients restricted to TLS 1.2 are not affected.

    Erlang/OTP ssl client TLS protocol version = TLS 1.2

Event History

Sep 22, 2026
CVE Published
via MITRE·08:49 AM
Data Sourced
via MITRE·08:49 AM
DescriptionWeakness
Data Sourced
via NVD·09:17 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Are clients using the default configuration exposed?

Yes. The default Erlang/OTP ssl client configuration is affected when it negotiates TLS 1.3. Clients restricted to TLS 1.2 are not affected.

2

What does an attacker need to exploit this?

The attacker must be able to answer the TLS 1.3 client connection as the purported server and include an unsolicited pre_shared_key extension in ServerHello. They do not need a server certificate, its private key, or a prior TLS session with the client.

3

Which certificate and identity checks are bypassed?

The affected handshake skips certificate handling entirely. This bypasses certificate path validation, verify_fun, hostname verification, partial_chain, CRL checking, and OCSP stapling.

4

What can be done if patching is not immediately possible?

Restrict affected clients to TLS 1.2 so they cannot negotiate the vulnerable TLS 1.3 path.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203