CVE-2026-58227
TLS/DTLS denial of service via unbounded recursion on cross-signed peer certificate chain
The Erlang/OTP ssl application does not detect cycles when reconstructing an incomplete peer certificate chain during a TLS or DTLS handshake. In ssl_certificate:handle_incomplete_chain/5, the received chain is passed to ssl_certificate:build_certificate_chain/5, which walks issuer relationships via ssl_certificate:do_certificate_chain/7 with no cycle detection and no depth limit. When the peer supplies two mutually cross-signed certificates in unordered form (A issues B, B issues A), the issuer lookup alternates between the two certificates and the pair of functions recurses indefinitely, growing the call stack and chain accumulator without bound. An unauthenticated remote attacker can send a crafted certificate chain in a TLS or DTLS Certificate handshake message to exhaust available memory and crash the BEAM node. Only a TCP connection and a partial handshake are required; no authentication or completed handshake is needed, and both TLS/DTLS servers and clients are affected when processing peer certificate messages. This issue affects OTP from OTP 23.2 before OTP 27.3.4.15, OTP 28.5.0.4, and OTP 29.0.4, corresponding to ssl from 10.2 before 11.2.12.11, 11.6.0.4, and 11.7.4.
Fixes and workarounds
Fix
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 |
≥ 23.2; < * (affected, otp); unaffected at 27.3.4.15; unaffected at 28.5.0.4; unaffected at 29.0.4
Other versions: unaffected |
CNA: EEF |
| OTP Erlang ssl
otp |
≥ 10.2; < * (affected, otp); unaffected at 11.2.12.11; unaffected at 11.6.0.4; unaffected at 11.7.4
Other versions: unaffected |
CNA: EEF |
| OTP Erlang erlang/otp
github |
≥ addc42df113f8f15fc20e9dff45490b3ce0d3d6b; < * (affected, git); unaffected at 7db64720177961e04545681480d691c4be81c54d; unaffected at 241d43703989fec4b6bf637beaeb366d92dcc4c2; unaffected at 0307bff2c72b685c6bd952daaac6bd661c247d62
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.7 high |
CVSS:4.0/AV:N/AC:L/AT:N/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-r5jr-mq46-vmhwCNA: EEF · vendor-advisory, related
- https://cna.erlef.org/cves/CVE-2026-58227.htmlCNA: EEF · related
- https://osv.dev/vulnerability/EEF-CVE-2026-58227CNA: EEF · related
- https://www.erlang.org/doc/system/versions.html#order-of-versionsCNA: EEF · x_version-scheme
- https://github.com/erlang/otp/commit/addc42df113f8f15fc20e9dff45490b3ce0d3d6bCNA: EEF · related
- https://github.com/erlang/otp/commit/7db64720177961e04545681480d691c4be81c54dCNA: EEF · patch
- https://github.com/erlang/otp/commit/241d43703989fec4b6bf637beaeb366d92dcc4c2CNA: EEF · patch
- https://github.com/erlang/otp/commit/0307bff2c72b685c6bd952daaac6bd661c247d62CNA: 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.