CVE-2026-58227

HIGHPre-NVD 8.78.7
EchelonGraph scoreLOW confidence

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: secondary
8.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: CVSS: 8.7Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.7
EG Score
8.7(low)
EG Risk
54(Track)
EG Risk 54/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity87% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
EPSS %ILE
KEV
Not listed

Published

July 27, 2026

Last Modified

July 27, 2026

Advisory Details (7)

Auto-updated Jul 27, 2026
Patch available. Sources: github, github_commit.
github_commit

commit 7db647201779 (erlang/otp)

Fix landed in erlang/otp commit 7db647201779 — awaiting tagged release

https://github.com/erlang/otp/commit/7db64720177961e04545681480d691c4be81c54d
github_commit

commit 241d43703989 (erlang/otp)

Fix landed in erlang/otp commit 241d43703989 — awaiting tagged release

https://github.com/erlang/otp/commit/241d43703989fec4b6bf637beaeb366d92dcc4c2
github_commit

commit 0307bff2c72b (erlang/otp)

Fix landed in erlang/otp commit 0307bff2c72b — awaiting tagged release

https://github.com/erlang/otp/commit/0307bff2c72b685c6bd952daaac6bd661c247d62
generic

Versions — Erlang System Documentation v29.0.4

https://www.erlang.org/doc/system/versions.html#order-of-versions
generic

OSV - Open Source Vulnerabilities

https://osv.dev/vulnerability/EEF-CVE-2026-58227
generic

TLS/DTLS denial of service via unbounded recursion on cross-signed peer certificate chain | Erlang Ecosystem Foundation CNA

https://cna.erlef.org/cves/CVE-2026-58227.html
github Patch Available

TLS Denial-of-Service using Invalid Cert Chains · Advisory · erlang/otp · GitHub

https://github.com/erlang/otp/security/advisories/GHSA-r5jr-mq46-vmhw

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 5× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-27 18:21 UTCEG score recompute
  2. 2026-07-27 17:36 UTCEG score recompute
  3. 2026-07-27 16:24 UTCEG score recompute
  4. 2026-07-27 15:31 UTCEG score recompute
  5. 2026-07-27 15:30 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-58227?
CVE-2026-58227 is a high vulnerability published on July 27, 2026. The Erlang/OTP ssl application does not detect cycles when reconstructing an incomplete peer certificate chain during a TLS or DTLS handshake. In sslcertificate:handleincompletechain/5, the received chain is passed to sslcertificate:buildcertificatechain/5, which walks issuer relationships via…
When was CVE-2026-58227 disclosed?
CVE-2026-58227 was first published in the National Vulnerability Database on July 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-58227?
CVE-2026-58227 has a CVSS v3 base score of 8.7 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-58227?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58227, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-58227

Explore →

Is Your Infrastructure Affected by CVE-2026-58227?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.