Erlang · Erlang/OTP · published 2026-10-14

CVE-2026-105236TLS 1.2 session resumption in ssl crosses SNI virtual-host client-certificate trust boundaries

Routine No exploitation evidence; EPSS 0.4%.

CVE-2026-105236 is not known to be exploited in the wild. EPSS estimates a 0.4% chance of exploitation in the next 30 days, higher than 34% of all CVEs. This Erlang/OTP vulnerability: CVSS 6.3 (v4.0). Fixed upstream in Erlang/OTP 29.1.2, 28.5.0.8, 27.3.4.19; Debian and Ubuntu still have unfixed releases. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in Erlang/OTP 29.1.2, 28.5.0.8, 27.3.4.19.

Linux distribution packages

If you run the distro’s package rather than an upstream build, this is the version to look for.

DistroReleasePackageStatus
Debian13 trixieerlangWon’t fix
12 bookwormerlangNo fix yet
Ubuntu26.04 LTSerlangNo fix yet
24.04 LTSerlangNo fix yet
22.04 LTSerlangNo fix yet

From the Debian Security Tracker, Ubuntu security notices (CC BY-SA 4.0) and Red Hat Security Data (CC BY 4.0). Check the distro link before acting.

Patch events

  1. This monthSecurity release

    Language runtimeErlang/OTP

    Erlang/OTP security releases: 29.1.2, 28.5.0.8, 27.3.4.19

    Upgrade to 29.1.228.5.0.827.3.4.19

    Why: Vendor security release for server software (most severe: CVE-2026-94200).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.4% (34th pct)FIRST EPSS v2026.06.15
CVSS base score6.3 (v4.0)
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

Improper Certificate Validation vulnerability in the ssl application in Erlang/OTP allows a client that holds a certificate trusted by one SNI virtual host to authenticate to a second SNI virtual host on the same listener by resuming its TLS 1.2 session there. A server that serves several SNI names from one listen socket through sni_fun or sni_hosts keeps one pre-TLS 1.3 session cache per listener and does not bind a cached session to the SNI name or client trust policy that established it. When an SNI option set switches to verify_peer without naming reuse_sessions, ssl_config:update_options/3 inherits the base listener's reuse_sessions value of true, so the default that disables reuse for client-authenticating servers does not apply. On an abbreviated handshake ssl_session:is_resumable/4 checks only that the cached session uses one of the current server certificates and carries some peer certificate, and never revalidates that certificate against the CA selected for the requested name. The names must share a server certificate, which is common with wildcard or multi-SAN certificates. TLS 1.3 does not use this cache and is not affected. This issue affects OTP from OTP 18.0 before OTP 27.3.4.19, OTP 28.5.0.8, and OTP 29.1.2, corresponding to ssl from 7.0 before 11.2.12.14, 11.6.0.7, and 11.7.8.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →