CVE-2026-55952
TLS 1.3 server denial of service via malformed ClientHello pre-shared key extension
The Erlang/OTP ssl application does not validate that the PSK identity list and binder list carried in a TLS 1.3 ClientHello pre-shared key extension have equal length before passing them to the session ticket handler. In tls_handshake_1_3:handle_pre_shared_key/3, an OfferedPreSharedKeys record with a mismatched number of identities and binders is forwarded directly to tls_server_session_ticket:use/4, which crashes the session ticket handler process. An unauthenticated remote attacker can send a single crafted ClientHello to a TLS 1.3 server with session tickets enabled (stateful or stateless mode) and permanently disrupt session ticket handling on that listener. New TLS 1.3 handshakes complete but subsequently crash when the server attempts to issue a session ticket, effectively making TLS 1.3 unusable on the affected listener until the ssl application is restarted. TLS 1.2 connections are not affected. This issue affects OTP from OTP 22.2 before OTP 27.3.4.14, OTP 28.5.0.3, and OTP 29.0.3, corresponding to ssl from 9.5 before 11.2.12.10, 11.6.0.3, and 11.7.3.
Fixes and workarounds
Workaround
* Disable session tickets on TLS 1.3 servers by setting session_tickets to disabled in the server's ssl options. * Restrict the server to TLS 1.2 by setting versions to ['tlsv1.2'] in the server's ssl options.
Source: CNA: EEFFix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: CNA: EEFFix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: CNA: EEFFix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: CNA: EEFFix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: CNA: EEFAffected products and versions
| Product | Versions | Authority |
|---|---|---|
| OTP Erlang otp
software-id |
≥ 22.2; < * (affected, otp); unaffected at 27.3.4.14; unaffected at 28.5.0.3; unaffected at 29.0.3
Other versions: unaffected |
CNA: EEF |
| OTP Erlang ssl
otp |
≥ 9.5; < * (affected, otp); unaffected at 11.2.12.10; unaffected at 11.6.0.3; unaffected at 11.7.3
Other versions: unaffected |
CNA: EEF |
| OTP Erlang erlang/otp
github |
≥ 339a279f02ce38a7b23010e56000613e19abb21f; < * (affected, git); unaffected at 095f744713c325acdbd18c23e397f04593c06275; unaffected at e77823e6d980b2ec0b4fe4ea3f2d098ca239e3ce; unaffected at 2c3e599797644310e5d4aa39c7193420e59dadff; unaffected at 9b5437c72fa3403a75c1aba28e5c532bc191c662
Other versions: unaffected |
CNA: EEF |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 4.0 / 8.2 high |
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N | CNA: EEF |
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://github.com/erlang/otp/security/advisories/GHSA-8c57-44c9-pc59CNA: EEF · vendor-advisory, related
- https://cna.erlef.org/cves/CVE-2026-55952.htmlCNA: EEF · related
- https://osv.dev/vulnerability/EEF-CVE-2026-55952CNA: EEF · related
- https://www.erlang.org/doc/system/versions.html#order-of-versionsCNA: EEF · x_version-scheme
- https://github.com/erlang/otp/commit/339a279f02ce38a7b23010e56000613e19abb21fCNA: EEF · related
- https://github.com/erlang/otp/commit/095f744713c325acdbd18c23e397f04593c06275CNA: EEF · patch
- https://github.com/erlang/otp/commit/e77823e6d980b2ec0b4fe4ea3f2d098ca239e3ceCNA: EEF · patch
- https://github.com/erlang/otp/commit/2c3e599797644310e5d4aa39c7193420e59dadffCNA: EEF · patch
- https://github.com/erlang/otp/commit/9b5437c72fa3403a75c1aba28e5c532bc191c662CNA: EEF · patch
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.