CVE-2026-94419

Without NO_SESSION_CACHE_REF, wolfSSL_get_session() does not return a session object but a ClientSession reference of the form {row, index, hash(sessionID)} into the process-global SessionCache, and ClientSessionToSession() validates it against that hash alone. Because the TLS 1.2 session ID is chosen by the server and sent in clear, AddSessionToCache() matches any other server's session on the same ID and overwrites the client-side entry with that server's master secret, cipher suite and version, while the handle continues to resolve; nothing on the write path compares the peer, the application's server ID or the WOLFSSL_CTX. Resuming through the handle then produces an abbreviated handshake in which no Certificate message is sent, so neither chain verification nor wolfSSL_check_domain_name() runs, and the attacker is accepted as the original server for the whole of that connection. Affected builds are those leaving NO_SESSION_CACHE_REF, NO_SESSION_CACHE, NO_CLIENT_CACHE and TITAN_SESSION_CACHE all undefined, which includes a plain ./configure, --enable-opensslextra and --enable-opensslall; fifteen integration options define NO_SESSION_CACHE_REF and are therefore not affected, among them --enable-all, --enable-distro, --enable-curl, --enable-nginx, --enable-haproxy, --enable-stunnel, --enable-wpas and the rest of the OPENSSL_COMPATIBLE_DEFAULTS family, and --enable-leanpsk, --enable-leantls, --enable-lowresource and --enable-tinytls13 disable the cache outright. The application must use the legacy reference flow, wolfSSL_get_session() or SSL_get_session() followed by wolfSSL_set_session(); wolfSSL_get1_session() returns the session object itself and is not affected, nor are wolfSSL_SetServerID() lookups. Only TLS 1.2 and below and DTLS 1.2 and below are reachable, since TLS 1.3 and ticket resumption with an empty ServerHello session ID both use a client-chosen cache key. The poisoned entry lives in the process-global cache, so it crosses WOLFSSL_CTX boundaries and persists until the entry is evicted or the session times out, 500 seconds by default. Releases v5.3.0 through v5.9.2 are affected; the fix adds a per-write generation counter to the cache and raises WOLFSSL_CACHE_VERSION from 2 to 3, so a cache persisted by an older build is rejected by a fixed one.

• CWE-287

• https://github.com/wolfSSL/wolfssl/pull/11500Issue Tracking, Patch

Published

Sep 27, 2026

Last Modified

Sep 30, 2026

Status

Analyzed

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-94413jshERP through 3.6 fails to redact password hashes in the /u…6.5
• CVE-2026-94414jshERP through 3.6 is missing an authorization check on the …5.4
• CVE-2026-94415Improper Neutralization of Input During Web Page Generation …7.1
• CVE-2026-94416An authorization bypass was found in the Ansible Automation …6.8
• CVE-2026-94417When an application enables both OCSP and CRL revocation che…5.3
• CVE-2026-94418Under WOLFSSL_SMALL_CERT_VERIFY, ProcessPeerCertParse() runs…7.5
• CVE-2026-9442A weakness has been identified in Edimax BR-6478AC 1.23. Thi…8.8
• CVE-2026-94421The Church Admin plugin for WordPress is vulnerable to Store…6.4
• CVE-2026-94422An incorrect implementation of message filtering in xdg-dbus…8.8
• CVE-2026-94423Net::LibSSH versions before 0.004 for Perl authenticate to a…9.1
• CVE-2026-94424A vulnerability has been found in Moore Threads MTT S80 Driv…8.8
• CVE-2026-94425A vulnerability was found in Moore Threads MTT S80 Driver Pa…8.8