# CVE-2026-94419: Client session cache reference poisoning allows resumption with wrong server > Attackers can hijack TLS sessions by poisoning the client cache, bypassing certificate verification and impersonating servers in wolfSSL builds with default session caching enabled. - **Severity:** Low 2.3 (`CVSS:4.0/AV:A/AC:H/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 27 Sep 2026 - **Updated:** 29 Sep 2026 - **Also known as:** AZL-105185, DEBIAN-CVE-2026-94419, GHSA-c72q-45p9-v8qh, UBUNTU-CVE-2026-94419 ## What is CVE-2026-94419? CVE-2026-94419 is a low-severity authentication bypass vulnerability in Wolfssl Wolfssl, published on 27 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description 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. Weakness: CWE-287 (Improper Authentication) ## Which versions are affected by CVE-2026-94419? It affects 1 product. Products: Wolfssl Wolfssl. ## How do I fix CVE-2026-94419? No fix has been published for CVE-2026-94419 yet. Limit exposure of the affected software until one is available. ## Is CVE-2026-94419 being exploited? There is no known exploitation of CVE-2026-94419 in the wild and no public exploit code. ## Other vulnerabilities in Wolfssl Wolfssl - [CVE-2024-5991](https://insights.sbomify.com/CVE-2024-5991/): Buffer overread in domain name matching (critical 10.0) - [CVE-2021-37155](https://insights.sbomify.com/CVE-2021-37155/): Security feature bypass in n/a (critical 9.8) - [CVE-2020-36177](https://insights.sbomify.com/CVE-2020-36177/): Memory corruption in n/a (critical 9.8) - [CVE-2014-2896](https://insights.sbomify.com/CVE-2014-2896/): Memory corruption in n/a (critical 9.8) - [CVE-2014-2897](https://insights.sbomify.com/CVE-2014-2897/): Memory corruption in n/a (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-94419 and fix it if it is affected. What it is: CVE-2026-94419 is a low-severity authentication bypass vulnerability in Wolfssl Wolfssl, published on 27 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-94419 in the wild and no public exploit code. Affected product: Wolfssl Wolfssl. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-94419/ (Markdown: https://insights.sbomify.com/CVE-2026-94419/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-94419 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-94419 - OSV: https://osv.dev/vulnerability/CVE-2026-94419 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-94419/ Summaries are generated and may contain mistakes; the official description above is the record.