CVE-2026-89422: CWE-322 Key Exchange without Entity Authentication in Erlang OTP
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.
AI Analysis
Technical Summary
The vulnerability arises because the TLS 1.3 client connection handler in Erlang/OTP ssl incorrectly processes a pre_shared_key extension in the ServerHello message that the client never offered. This sets a resumption flag without verifying the client's PSK offer, causing the handshake to proceed without proper certificate validation. As a result, the client accepts a server that presents no certificate, private key, or prior session, enabling impersonation. The flaw affects default client configurations that support TLS 1.3, but not clients restricted to TLS 1.2. Affected versions include OTP from 22.2 before 27.3.4.18 and ssl from 9.5 before 11.2.12.13, among others.
Potential Impact
An attacker can impersonate the intended server during a TLS 1.3 handshake, bypassing all certificate validation steps including certificate path validation, hostname verification, and revocation checks. This undermines the authenticity guarantees of TLS connections, potentially exposing clients to man-in-the-middle attacks without any user interaction or prior authentication.
Mitigation Recommendations
A fix is available in Erlang/OTP versions 27.3.4.18, 28.5.0.7, and 29.1.1, and corresponding ssl versions 11.2.12.13, 11.6.0.6, and 11.7.7. Users should upgrade to these or later versions to remediate the vulnerability. There is no indication that the vulnerability is mitigated by configuration changes alone. Patch status is confirmed by the vendor advisory information.
CVE-2026-89422: CWE-322 Key Exchange without Entity Authentication in Erlang OTP
Description
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 v4.0
Score 9.3critical
Affected software
Erlang
OTP
Erlang
OTP
Erlang
OTP
cpe:2.3:a:erlang:erlang\/otp:*:*:*:*:*:*:*:*Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability arises because the TLS 1.3 client connection handler in Erlang/OTP ssl incorrectly processes a pre_shared_key extension in the ServerHello message that the client never offered. This sets a resumption flag without verifying the client's PSK offer, causing the handshake to proceed without proper certificate validation. As a result, the client accepts a server that presents no certificate, private key, or prior session, enabling impersonation. The flaw affects default client configurations that support TLS 1.3, but not clients restricted to TLS 1.2. Affected versions include OTP from 22.2 before 27.3.4.18 and ssl from 9.5 before 11.2.12.13, among others.
Potential Impact
An attacker can impersonate the intended server during a TLS 1.3 handshake, bypassing all certificate validation steps including certificate path validation, hostname verification, and revocation checks. This undermines the authenticity guarantees of TLS connections, potentially exposing clients to man-in-the-middle attacks without any user interaction or prior authentication.
Mitigation Recommendations
A fix is available in Erlang/OTP versions 27.3.4.18, 28.5.0.7, and 29.1.1, and corresponding ssl versions 11.2.12.13, 11.6.0.6, and 11.7.7. Users should upgrade to these or later versions to remediate the vulnerability. There is no indication that the vulnerability is mitigated by configuration changes alone. Patch status is confirmed by the vendor advisory information.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- EEF
- Date Reserved
- 2026-09-11T18:45:01.480Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6ab24461f7a7c54106f3e60d
Added to database: 09/22/2026, 09:03:29 UTC
Last enriched: 09/22/2026, 09:17:40 UTC
Last updated: 09/23/2026, 02:01:18 UTC
Views: 40
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.