CVE-2026-55953: TLS 1.2 and DTLS client accepts unoffered anonymous cipher suite, bypassing server authentication

Published Jul 27, 2026
·
Updated

The Erlang/OTP ssl TLS 1.2 (and earlier) and DTLS client does not verify that the cipher suite selected by the server in ServerHello was among the suites offered by the client in ClientHello. The client-side tlshandshake:hello/5 handler validates the negotiated protocol version and the downgrade sentinel but hands the server-chosen suite directly to sslhandshake:handleserverhelloextensions/9, which installs it without a membership check. The TLS 1.3 client path performs this check (per RFC 8446), so it is not affected.

An on-path attacker between the client and the intended server can respond with a ServerHello selecting an anonymous key exchange suite such as TLSDHanon or TLSECDHanon that the client never offered. Anonymous suites do not require the server to present a certificate, so the entire verifypeer and cacerts configuration is bypassed: the attacker completes the handshake with its own ephemeral parameters, no certificate is validated, no hostname is checked, and ssl:connect returns {ok, Socket}. All subsequent application traffic is readable and modifiable by the attacker.

This issue affects OTP from OTP R13B03 before OTP 27.3.4.15, from OTP 28.0 before OTP 28.5.0.4, and from OTP 29.0 before OTP 29.0.4, corresponding to ssl from 3.10.7 before 11.2.12.11, from 11.3 before 11.6.0.4, and from 11.7 before 11.7.4. Whether OTP before OTP R13B03, corresponding to ssl before 3.10.7, is affected is unknown.

Other sources

TLS 1.2 and DTLS client accepts unoffered anonymous cipher suite, bypassing server authentication

Microsoft

Affected Software

9 affected componentsFixes available
Erlang/OTP Erlang/OTP>R13B03<=27.3.4.15, >28.0<=28.5.0.4, >29.0<=29.0.4
ssl>3.10.7<=11.2.12.11, >=11.3<11.6.0.4, >=11.7<11.7.4
Microsoft azl3 erlang 26.2.5.21-4<26.2.5.21-3
26.2.5.21-3
Erlang Erlang\/otp>=17.0<27.3.4.15
Erlang Erlang\/otp>=28.0<28.5.0.4
Erlang Erlang\/otp>=29.0<29.0.4
Erlang Erlang\/ssl>=5.3.4<11.2.12.11
Erlang Erlang\/ssl>=11.3<11.6.0.4
Erlang Erlang\/ssl>=11.7<11.7.4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 26.2.5.21-3
  2. Upgrade

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

    Fixed in 27.3.4.15
  3. Upgrade

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

    Fixed in 28.5.0.4
  4. Upgrade

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

    Fixed in 29.0.4
  5. Upgrade

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

    Fixed in 11.2.12.11
  6. Upgrade

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

    Fixed in 11.6.0.4
  7. Upgrade

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

    Fixed in 11.7.4

Event History

Jul 27, 2026
CVE Published
via MITRE·03:21 PM
Data Sourced
via MITRE·03:21 PM
DescriptionWeakness
Data Sourced
via NVD·04:17 PM
RemedyDescriptionSeverityWeaknessAffected Software
Aug 7, 2026
Data Sourced
via Microsoft·07:39 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·07:39 AM
DescriptionSeverity
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-55953?

CVE-2026-55953 has a severity score of 89, indicating a high risk of exploitation.

2

How do I fix CVE-2026-55953?

To mitigate CVE-2026-55953, ensure that your application uses a version of Erlang/OTP ssl that addresses this vulnerability.

3

What types of systems are affected by CVE-2026-55953?

CVE-2026-55953 affects applications using the Erlang/OTP ssl for TLS 1.2 and DTLS connections.

4

What is the main issue with CVE-2026-55953?

The main issue with CVE-2026-55953 is that it allows a TLS client to accept a cipher suite that was not offered by the client, compromising server authentication.

5

When was CVE-2026-55953 published?

CVE-2026-55953 was published on July 27, 2026.

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