CVE-2026-58227
What it is
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 29.0.4, OTP 28.5.0.4 and OTP 27.3.4.15, corresponding to ssl from 10.2 before 11.7.4, 11.6.0.4 and 11.2.12.11.
At a glance
- Exploitability
- Can be exploited over the network without logging in. High risk of service disruption.
- Exploit odds
- 0.4% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.4% in the next 30 days (EPSS).
- Severity: 8.7 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.4% · EPSS, next 30 days
- Weakness
- CWE-674
- Record status
- Analyzed
Affected
- Erlang erlang\/otp < 27.3.4.15
- Erlang erlang\/otp < 28.5.0.4
- Erlang erlang\/otp < 29.0.4
- Erlang erlang\/ssl < 11.2.12.11
- Erlang erlang\/ssl < 11.6.0.4
- Erlang erlang\/ssl < 11.7.4
Attack profile CVSS 4.0 · 8.7
- Attack vector
- Network
- Complexity
- Low
- Attack requirements
- None
- Privileges needed
- None
- User interaction
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-58227.md and follow it. Check whether this project is affected by CVE-2026-58227. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://cna.erlef.org/cves/CVE-2026-58227.html
- https://github.com/erlang/otp/commit/0307bff2c72b685c6bd952daaac6bd661c247d62
- https://github.com/erlang/otp/commit/241d43703989fec4b6bf637beaeb366d92dcc4c2
- https://github.com/erlang/otp/commit/7db64720177961e04545681480d691c4be81c54d
- https://github.com/erlang/otp/security/advisories/GHSA-r5jr-mq46-vmhw
- https://osv.dev/vulnerability/EEF-CVE-2026-58227
References
- https://cna.erlef.org/cves/CVE-2026-58227.html
- https://github.com/erlang/otp/commit/0307bff2c72b685c6bd952daaac6bd661c247d62
- https://github.com/erlang/otp/commit/241d43703989fec4b6bf637beaeb366d92dcc4c2
- https://github.com/erlang/otp/commit/7db64720177961e04545681480d691c4be81c54d
- https://github.com/erlang/otp/security/advisories/GHSA-r5jr-mq46-vmhw
- https://osv.dev/vulnerability/EEF-CVE-2026-58227
- https://www.erlang.org/doc/system/versions.html#order-of-versions