Vulnary
← back to the feed
Critical· 9.1official fix available

CVE-2026-55953

Erlang/OTP’s SSL/TLS client can accept a server‑chosen cipher suite that the client never offered, allowing an attacker to use an anonymous cipher and bypass certificate checks. This flaw lets an on‑path attacker read and modify all traffic after the handshake.

publishedJul 27, 2026
last modifiedJul 30, 2026
sourcesNVD
severity · cvss
9.1
critical · how bad it is
exploitation · epss
<1%
16th percentile · chance of exploitation in 30 days
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
auto-deletes from the system
counting…on Aug 26, 2026

An official fix is available, so this entry is kept for 30 days and then removed automatically.

01

Who is affected

Erlang/OTP SSL/TLS client versions before OTP 29.0.4, OTP 28.5.0.4, and OTP 27.3.4.15 (corresponding to ssl 5.3.4 before 11.7.4, 11.6.0.4, and 11.2.12.11).

02

Real-world impact

An attacker between the client and server can complete the TLS handshake with an anonymous cipher suite, bypassing all certificate verification. The attacker then gains full read/write access to the encrypted traffic.

03

Why this severity

The CVSS score of 9.1 reflects the high impact on confidentiality (the attacker can read all data) and the lack of authentication or integrity checks, combined with low attack complexity and no user interaction.

04

What to do about it

official fix available
recommended steps
  1. 01Identify the current Erlang/OTP version you are running.
  2. 02Upgrade to OTP 29.0.4 or later, OTP 28.5.0.4 or later, or OTP 27.3.4.15 or later, which contain the patch that validates the server‑chosen cipher suite.

NVD description

05

Timeline

  1. Jul 27, 2026 · 4d ago
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Jul 27, 2026 · 4d ago
    Official fix available
    A vendor patch or mitigation now exists — see the remediation steps above.
  3. Jul 30, 2026 · 1d ago
    Advisory updated
    The NVD record was last revised.
06

How it’s attacked

Attack vectorNetwork (remote)
Attack complexityLow
Attack requirementsPresent
Privileges requiredNone
User interactionNone needed
Confidentiality impactHigh
Integrity impactHigh
Availability impactNone
07

References & advisories

(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →