CVE Hunter
›
CVE-2026-94419

CWE-287

MEDIUM CVSS 5.4 NVD

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.

Yayınlanma 27.09.2026
ISO Tarih 2026-09-27
CVSS Sürüm v3.1
Kaynak NVD
CVSS v3.1 Metrikleri
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Attack Vector Network AV:N
Attack Complexity Low AC:L
Privileges Req. Low PR:L
User Interaction None UI:N
Scope Unchanged S:U
Confidentiality Low C:L
Integrity Low I:L
Availability None A:N
AI Güvenlik Analizi
🤖 Yapay Zeka Güvenlik Analizi Hazırlanıyor…
CVSS vektörü ve CWE zayıflık yapısı inceleniyor…
Hedef Keşif Sorguları

FOFA Sorgusu

app="nginx"
CVSS Skoru
5.4 / 10 · CVSS MEDIUM
Zayıflık Türleri (CWE)
CWE-287
Etkilenen Ürünler (1)
wolfssl:wolfssl (tüm sürümler)
Referanslar (1)
github.com patch
İlgili CVE'ler
9.8
CVE-2026-110009
The Unzer Payments plugin for WordPress is vulnerable to Authentication Bypass leading to Account Takeover in
9.8
CVE-2026-110811
The Trust Payments Gateway for WooCommerce (JavaScript Library) plugin for WordPress is vulnerable to Authenti
9.3
CVE-2026-130730
NocoDB before 2026.10.1 contains an authentication bypass vulnerability that allows OAuth token holders to act
7.4
CVE-2026-107644
The Bizuno Accounting – ERP/Accounting/CRM (for WordPress) plugin for WordPress is vulnerable to Authenticat
0.0
CVE-2026-128981
** UNSUPPORTED WHEN ASSIGNED **  Improper Authentication in Apache SeaTunnel Web 1.0.2 allows a user whose
8.7
CVE-2026-110782
## Summary CVE-2026-49283 / GHSA-6929-8p9f-26jx ("HTTP-Artifact TLS validator confusion allows cross-IdP authe