CVE-2026-55953: Erlang OTP · Algorithm Downgrade
Affects Erlang OTPSource CVE Database V5
Not known to be exploited · CVSS 9.1 Critical · fixed in 29.0.4 : patch Erlang OTP as a priority.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 29.0.4, 28.5.0.4, 27.3.4.15 +3
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 27 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Upgrade OTP to 29.0.4, 28.5.0.4 or 27.3.4.15; OTP and ssl to 11.7.4, 11.6.0.4 or 11.2.12.11.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| ErlangOTP | Affected
| Fixed in
|
| ErlangOTP | Affected
| Fixed in
|
| ErlangOTP | Affected
| Fixed in– |
GitHubsslpkg:github/sslOther threats | Affected
| Fixed in
|
GitHuberlang/otppkg:github/erlang/otpOther threats | Affected– | Fixed in– |
CPE configurations (1)
cpe:2.3:a:erlang:erlang\/otp:*:*:*:*:*:*:*:*
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
The vulnerability affects specific Erlang/OTP versions prior to OTP 27.3.4.15, 28.5.0.4, and 29.0.4. If you cannot patch yet, avoid using vulnerable OTP versions in environments where on-path attackers are a concern.
Description
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 tls_handshake:hello/5 handler validates the negotiated protocol version and the downgrade sentinel but hands the server-chosen suite directly to ssl_handshake:handle_server_hello_extensions/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 TLS_DH_anon_* or TLS_ECDH_anon_* that the client never offered. Anonymous suites do not require the server to present a certificate, so the entire verify_peer 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 17.0 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 5.3.4 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 17.0, corresponding to ssl before 5.3.4, is affected is unknown.
References
- github.com/erlang/otp/security/advisories/GHSA-c6cw-pr89-w882 (opens in a new tab)
- cna.erlef.org/cves/CVE-2026-55953.html (opens in a new tab)
- osv.dev/vulnerability/EEF-CVE-2026-55953 (opens in a new tab)
- erlang.org/doc/system/versions.html (opens in a new tab)
- github.com/erlang/otp/commit/064e236414614f9085cbbbd6eacf0e43c02d1b4b (opens in a new tab)
- github.com/erlang/otp/commit/0a82596d425abe43dc2e0b3d74aa1557ef74051c (opens in a new tab)
- github.com/erlang/otp/commit/e6ff938116b2872bccc478af7fefb56627285b77 (opens in a new tab)