Vulnerabilities

Vulnerability · CVE-2026-58227

The Erlang/OTP ssl application does not detect cycles when reconstructing an incomplete peer certificate chain during a TLS or DTLS handshake.

Published Jul 27, 2026 · catalog updated Nov 11, 2026 · The Erlang/OTP ssl application

Last checked Nov 11, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-58227. EPSS is 0.39%. Act only if a listed version of The Erlang/OTP ssl application is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (The Erlang/OTP ssl application).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.

Same product and reporting

Severity
High8.7
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.39%
Remediation
Version ranges on file
Affected products
cpe erlang/erlang/otp · cpe erlang/erlang/ssl

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe erlang/erlang/otp< 27.3.4.15
  • cpe erlang/erlang/otp< 28.5.0.4
  • cpe erlang/erlang/otp< 29.0.4
  • cpe erlang/erlang/ssl< 11.2.12.11
  • cpe erlang/erlang/ssl< 11.6.0.4
  • cpe erlang/erlang/ssl< 11.7.4

How to fix CVE-2026-58227

  • Upgrade

    CVE-2026-58227 lists a fix boundary at 27.3.4.15. Compare the installed build with that boundary before you change production.

  • Version check

    Affected < 27.3.4.15

  • Advisory

    Open the cve_org record and follow its fix.

  • Official advisories

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-58227. EPSS is 0.39%. Act only if a listed version of The Erlang/OTP ssl application is installed.

Which versions are affected?

Compare what you have installed with < 27.3.4.15, < 28.5.0.4, < 29.0.4, < 11.2.12.11, < 11.6.0.4, < 11.7.4. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-674. EPSS 0.39%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Jul 27, 2026 · NIST NVD

    Detected

    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 su

  2. Nov 11, 2026 · NIST NVD

    Updated

    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 su

Sources

  • CVE.orgVulnerability recordCVE-2026-58227

    Official CVE identifier

    cve.org
  • NIST NVDVulnerability recordCVE-2026-58227

    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 issu

    nvd.nist.gov

References

Freshness

Last verified in this catalog Nov 11, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • CVE.orgNov 11, 2026
  • NIST NVDNov 11, 2026