CVE-2026-58227

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 67% of all CVEs by exploit prediction. 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: epss, nvd
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: 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
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/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
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
33%
KEV
Not listed

Published

July 27, 2026

Last Modified

August 10, 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

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
erlang1:23.2.6+dfsg-1 ... 1:29.0~rc3+dfsg-4 (117 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
erlang1:25.2.3+dfsg-1 ... 1:29.0~rc3+dfsg-4 (78 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
erlang1:27.3.4.1+dfsg-1, 1:27.3.4.1+dfsg-1+deb13u1, 1:27.3.4.1+dfsg-1+deb13u21:27.3.4.1+dfsg-1+deb13u3—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
erlang1:27.3.4.1+dfsg-1 ... 1:29.0~rc3+dfsg-4 (35 versions)1:29.0.4+dfsg-1—

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 22× in last 7d / 88× 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.

Showing the most recent 100 of 161 total refreshes for this CVE.

  1. 2026-09-19 08:17 UTCEG score recompute
  2. 2026-09-19 08:17 UTCVendor advisory
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 18:54 UTCVendor advisory
  5. 2026-09-18 02:24 UTCEG score recompute
  6. 2026-09-18 02:24 UTCVendor advisory
  7. 2026-09-17 19:31 UTCEPSS rescore
  8. 2026-09-17 01:47 UTCEG score recompute
  9. 2026-09-17 01:47 UTCVendor advisory
  10. 2026-09-16 14:08 UTCEPSS rescore
  11. 2026-09-16 06:17 UTCEG score recompute
  12. 2026-09-16 06:17 UTCVendor advisory
  13. 2026-09-16 05:15 UTCEPSS rescore
  14. 2026-09-15 09:10 UTCEG score recompute
  15. 2026-09-15 09:10 UTCVendor advisory
  16. 2026-09-15 03:11 UTCEPSS rescore
  17. 2026-09-14 15:42 UTCVendor advisory
  18. 2026-09-14 04:18 UTCVendor advisory
  19. 2026-09-13 16:58 UTCEG score recompute
  20. 2026-09-13 16:58 UTCVendor advisory
  21. 2026-09-13 16:47 UTCEPSS rescore
  22. 2026-09-13 05:37 UTCVendor advisory
  23. 2026-09-12 18:16 UTCEG score recompute
  24. 2026-09-12 18:16 UTCVendor advisory
  25. 2026-09-12 06:53 UTCVendor advisory
Show 75 more
  1. 2026-09-11 19:32 UTCEG score recompute
  2. 2026-09-11 19:32 UTCVendor advisory
  3. 2026-09-11 14:53 UTCEPSS rescore
  4. 2026-09-10 20:48 UTCEG score recompute
  5. 2026-09-10 09:35 UTCEPSS rescore
  6. 2026-09-09 08:21 UTCEG score recompute
  7. 2026-09-08 22:01 UTCEPSS rescore
  8. 2026-09-07 21:03 UTCEG score recompute
  9. 2026-09-07 21:03 UTCVendor advisory
  10. 2026-09-07 16:01 UTCEPSS rescore
  11. 2026-09-06 19:12 UTCEG score recompute
  12. 2026-09-06 19:12 UTCVendor advisory
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-05 19:15 UTCEG score recompute
  15. 2026-09-05 19:15 UTCVendor advisory
  16. 2026-09-05 05:45 UTCEG score recompute
  17. 2026-09-05 05:45 UTCVendor advisory
  18. 2026-09-04 12:32 UTCEG score recompute
  19. 2026-09-04 12:32 UTCVendor advisory
  20. 2026-09-04 05:07 UTCEPSS rescore
  21. 2026-09-02 14:12 UTCEPSS rescore
  22. 2026-09-01 22:59 UTCEG score recompute
  23. 2026-09-01 22:59 UTCVendor advisory
  24. 2026-09-01 13:54 UTCEPSS rescore
  25. 2026-09-01 04:40 UTCEPSS rescore
  26. 2026-08-30 22:33 UTCEG score recompute
  27. 2026-08-30 22:33 UTCVendor advisory
  28. 2026-08-30 19:17 UTCEPSS rescore
  29. 2026-08-30 11:13 UTCEG score recompute
  30. 2026-08-30 11:13 UTCVendor advisory
  31. 2026-08-30 01:22 UTCEPSS rescore
  32. 2026-08-29 23:52 UTCEG score recompute
  33. 2026-08-29 23:52 UTCVendor advisory
  34. 2026-08-28 21:42 UTCEPSS rescore
  35. 2026-08-27 21:31 UTCEG score recompute
  36. 2026-08-27 21:31 UTCVendor advisory
  37. 2026-08-27 14:25 UTCEPSS rescore
  38. 2026-08-27 10:11 UTCVendor advisory
  39. 2026-08-26 22:50 UTCEG score recompute
  40. 2026-08-26 22:50 UTCVendor advisory
  41. 2026-08-26 14:46 UTCEPSS rescore
  42. 2026-08-26 11:29 UTCVendor advisory
  43. 2026-08-25 23:47 UTCEG score recompute
  44. 2026-08-25 23:47 UTCVendor advisory
  45. 2026-08-25 13:49 UTCEPSS rescore
  46. 2026-08-25 12:28 UTCVendor advisory
  47. 2026-08-25 01:06 UTCEG score recompute
  48. 2026-08-25 01:06 UTCVendor advisory
  49. 2026-08-24 13:46 UTCEG score recompute
  50. 2026-08-24 13:46 UTCVendor advisory
  51. 2026-08-24 02:26 UTCVendor advisory
  52. 2026-08-23 14:38 UTCVendor advisory
  53. 2026-08-23 03:18 UTCEG score recompute
  54. 2026-08-23 03:18 UTCVendor advisory
  55. 2026-08-23 00:19 UTCEPSS rescore
  56. 2026-08-22 15:58 UTCVendor advisory
  57. 2026-08-22 04:38 UTCEG score recompute
  58. 2026-08-22 04:38 UTCVendor advisory
  59. 2026-08-21 23:49 UTCEPSS rescore
  60. 2026-08-21 05:58 UTCEG score recompute
  61. 2026-08-21 05:58 UTCVendor advisory
  62. 2026-08-20 22:55 UTCEPSS rescore
  63. 2026-08-20 18:38 UTCVendor advisory
  64. 2026-08-20 07:17 UTCVendor advisory
  65. 2026-08-19 19:57 UTCEG score recompute
  66. 2026-08-19 19:57 UTCVendor advisory
  67. 2026-08-19 17:04 UTCEPSS rescore
  68. 2026-08-19 06:29 UTCVendor advisory
  69. 2026-08-18 19:09 UTCEG score recompute
  70. 2026-08-18 19:09 UTCVendor advisory
  71. 2026-08-18 13:48 UTCEPSS rescore
  72. 2026-08-17 20:16 UTCEG score recompute
  73. 2026-08-17 20:16 UTCVendor advisory
  74. 2026-08-17 13:47 UTCEPSS rescore
  75. 2026-08-17 06:47 UTCVendor advisory

Related CVEs(same vendor + same CWE)

Frequently asked(5)

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, with the most recent update on August 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-58227 actively exploited?
CVE-2026-58227 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 67.3% of all scored CVEs.
What is the CVSS score of CVE-2026-58227?
CVE-2026-58227 has a CVSS v3 base score of 7.5 (NVD).
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

See which npm, PyPI, Go, and Maven packages are affected by 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.

Start Free Scan →Browse All CVEs