Node crash via cyclic certificate-chain recursion
Published Jul 27, 2026 · Updated Jul 27, 2026
Uncontrolled recursion in Erlang/OTP ssl allows remote attackers to crash a BEAM node with a crafted TLS or DTLS certificate chain. ssl_certificate:handle_incomplete_chain/5 passes an incomplete peer chain to build_certificate_chain/5, whose issuer walk revisits mutually cross-signed certificates without cycle detection or a depth limit. Only a network connection and partial handshake are required; recursion exhausts memory and terminates the node before authentication or handshake completion.
Summary
What happened
Uncontrolled recursion in Erlang/OTP ssl allows remote attackers to crash a BEAM node with a crafted TLS or DTLS certificate chain. ssl_certificate:handle_incomplete_chain/5 passes an incomplete peer chain to build_certificate_chain/5, whose issuer walk revisits mutually cross-signed certificates without cycle detection or a depth limit. Only a network connection and partial handshake are required; recursion exhausts memory and terminates the node before authentication or handshake completion.
The record
- CVE
- CVE-2026-58227
- Published
- Jul 27, 2026
- Updated
- Jul 27, 2026
- Vendor
- Erlang
- Product
- Erlang/OTP
- Classifications
- CWE-674, CAPEC-130, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 27, 2026CVE publishedPublication date reported by the CVE source.
- Jul 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=10.2 <* changes=[{"at":"11.7.4","status":"unaffected"},{"at":"11.6.0.4","status":"unaffected"},{"at":"11.2.12.11","status":"unaffected"}]
- Affected versionversion=23.2 <* changes=[{"at":"29.0.4","status":"unaffected"},{"at":"28.5.0.4","status":"unaffected"},{"at":"27.3.4.15","status":"unaffected"}]
- Affected versionversion=addc42df113f8f15fc20e9dff45490b3ce0d3d6b <* changes=[{"at":"7db64720177961e04545681480d691c4be81c54d","status":"unaffected"},{"at":"241d43703989fec4b6bf637beaeb366d92dcc4c2","status":"unaffected"},{"at":"0307bff2c72b685c6bd952daaac6bd661c247d62","status":"unaffected"}]
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo