CVE-2026-58227
Erlang SSL recursion bug allows remote DoS via crafted TLS/DTLS certificate chains.
Is CVE-2026-58227 being exploited?
Not confirmed. CVE-2026-58227 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.39% probability of exploitation in the next 30 days.
How severe is CVE-2026-58227?
CVE-2026-58227 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-58227?
Yes. A fix has been recorded for CVE-2026-58227. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-58227 affect?
CVE-2026-58227 affects Erlang/OTP ssl (OTP 23.2 -> <29.0.4), ssl 10.2 -> <11.7.4, 11.6.0.4, 11.2.12.11, BEAM-based apps (e.g., RabbitMQ, CouchDB) that use vulnerable ssl. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-58227?
Upgrade Erlang/OTP ssl to fixed versions; restrict untrusted TLS peers; monitor BEAM process crashes.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated remote attacker can send crafted cert chains to exhaust memory and crash the BEAM node, causing remote DoS for clients and servers.
Patch when possible
- affected>= 10.2 and < *
- affected>= 23.2 and < *
- affected>= addc42df113f8f15fc20e9dff45490b3ce0d3d6b and < *
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.