CVE-2026-11703: WolfSSL Session Resumption SNI/ALPN Bypass

Technical summary

CVE-2026-11703 addresses a session resumption vulnerability in WolfSSL affecting stateful session-ID resumption. The library previously bound SNI and ALPN parameters only during ticket-based resumption but omitted this check for session-ID based resumption. This allowed a peer-authentication state cached during one SNI/ALPN context to be carried into a different virtual-host context where the authentication policy was not established. The vulnerability stems from inconsistent validation logic across two resumption code paths. The patch unifies validation by requiring SNI/ALPN binding verification for all session resumption paths; mismatches trigger a decline and force a full TLS handshake.

Business impact

This vulnerability poses a direct risk to multi-tenant or virtual-host TLS deployments where different security policies apply per domain. If client certificates or authentication requirements vary by virtual host, an attacker could authenticate to one host and reuse that session to access another, bypassing second-factor or certificate-pinning checks. For organizations running WolfSSL in edge gateways, API servers, or IoT platforms that host multiple secure endpoints, a successful exploit could enable unauthorized access or lateral movement within the infrastructure.

Affected systems

WolfSSL (all versions prior to the patch) is affected. WolfSSL is a lightweight, embedded TLS library used in IoT devices, embedded systems, automotive, and industrial applications. Organizations should inventory WolfSSL usage in production systems, particularly those supporting multi-tenant or virtual-host configurations where different authentication policies apply per endpoint.

Exploitability

Exploitability requires an attacker to establish an authenticated TLS session with the library under one SNI/ALPN context, then reuse that cached session identifier under a different SNI/ALPN on the same or related server. No user interaction is needed; the attack operates at the network and TLS protocol level. However, the practical attack surface depends on deployment: a single-tenant system with uniform authentication policies across SNI values is lower-risk than multi-tenant or policy-segregated deployments. The attack is network-accessible and requires no special privileges, supporting the HIGH severity rating.

Remediation

Upgrade WolfSSL to a patched version. Verify the exact version with your WolfSSL vendor release notes or advisory (referenced at https://www.wolfssl.com for official security bulletins). As an interim control, restrict session caching if SNI/ALPN policies differ across virtual hosts, or disable session resumption entirely if the performance impact is acceptable. Review TLS configuration to confirm that authentication policies are correctly tied to SNI/ALPN and not inadvertently shared across unrelated contexts.

Patch guidance

Contact WolfSSL or consult their security advisory page for the patch version number and release date. Apply patches in order of priority to production systems hosting multi-tenant or policy-segregated virtual hosts. Test patched binaries in a staging environment to confirm compatibility with your application and that session resumption still functions as expected. Validate that SNI/ALPN mismatches now correctly trigger fallback to full handshakes rather than enabling session reuse.

Detection guidance

Monitor TLS handshakes for suspicious session resumption patterns: a single session identifier being resumed under multiple SNI or ALPN values in a short time window may indicate exploitation. Enable debug-level logging in WolfSSL (if available in your build) to observe session resumption decisions. Review TLS session cache metrics and cross-correlate with access logs to identify clients reusing session IDs across unexpected virtual-host boundaries. Intrusion detection systems can flag rapid SNI switching on a single session identifier as a potential indicator.

Why prioritize this

This vulnerability scores HIGH (7.5) due to its high integrity impact and network-accessible, low-complexity attack path. While exploitation requires a specific multi-host deployment pattern, the consequence—bypassing authentication or authorization policy boundaries—is severe. Organizations with WolfSSL in multi-tenant, policy-segregated, or defense-in-depth edge environments should patch urgently. Single-tenant or uniform-policy deployments face lower risk but should still plan patching within standard change windows.

Risk score, explained

The CVSS 3.1 score of 7.5 (HIGH) reflects an attack vector that is network-based, requires no privileges or user interaction, and results in high integrity impact (CWE-287: Improper Authentication). Scope is unchanged, and there is no direct confidentiality or availability impact in the base score. The score appropriately captures the risk of authentication and authorization bypass through a protocol-layer flaw. Contextual risk may be higher in zero-trust or policy-enforcement architectures where authentication state is critical; it may be lower in monolithic single-tenant systems.

Frequently asked questions