CVE-2026-105236
Medium 6.3No known exploitationFix availableTLS 1.2 session resumption in ssl crosses SNI virtual-host client-certificate trust boundaries
Record last updated
CVSS score
Medium on a 0 to 10 scale
EPSS, chance of exploitation in 30 days
Higher than 34% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
Description
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.
Weakness: CWE-295
Patching and mitigation
- Patch status
- Fix available (source: Microsoft MSRC)
- Fix documented (source date)
- Mitigation
- * Set {reuse_sessions, false} in each SNI service's option set, or in the base listener options. The reporter's proof of concept confirmed that this blocks the cross-name resumption. * Serve distinct SNI trust domains on separate listen sockets, which gives each its own session cache. * Restrict the listener to TLS 1.3 with {versions, ['tlsv1.3']}. TLS 1.3 does not use the session-ID cache. Source (opens in a new tab)
- Vendor guidance
- github.com (opens in a new tab)
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| Erlang | OTP | 18.0 | Not documented | CVE Program |
| Erlang | OTP | 4fe38c4b8b2c8024afb60990e598ff823743fd54 | Not documented | CVE Program |
| Erlang | OTP | 7.0 | Not documented | CVE Program |
| Microsoft | azl3 erlang 26.2.5.21-6 on Azure Linux 3.0 | Not documented | 26.2.5.21-8 | Microsoft MSRC |
| Microsoft | azl4 erlang 26.2.5.21-14.azl4 on Azure Linux 4.0 | Not documented | 0:26.2.5.21-18.azl4 | Microsoft MSRC |
Timeline
Disclosure
CVE record published by EEF
Source: CVE Program (opens in a new tab)
Advisory
Microsoft advisory published
Advisory change
Microsoft advisory revised (2.0): Information published.
Advisory change
Microsoft advisory revised (3.0): Information published.
Advisory change
Microsoft advisory revised (4.0): Information published.
Patch
Fix documented by Microsoft MSRC
Vendor guidance and references
- Fix commit 0c20f36 in erlang/otp (opens in a new tab)patch
- Fix commit 10ee925 in erlang/otp (opens in a new tab)patch
- Fix commit 4d76adb in erlang/otp (opens in a new tab)patch
- GitHub Advisory (opens in a new tab)related, vendor-advisory
- Microsoft Security Update Guide (opens in a new tab)vendor-advisory
- EEF CNA record for CVE-2026-105236 (opens in a new tab)related
- Introducing commit 4fe38c4 in erlang/otp (opens in a new tab)related
- OSV record EEF-CVE-2026-105236 (opens in a new tab)related
- Erlang/OTP version ordering (opens in a new tab)x_version-scheme