Security Advisory

CVE-2026-93302: wolfSSL Trusted Peer CA Forgery

Last updated:
  • CVE-2026-93302

CVE-2026-93302 is a certificate-verification flaw in the wolfSSL embedded TLS library: MatchTrustedPeer ignores the public key, so a forged clone of a trusted CA certificate passes verification and a (D)TLS peer that knows the loaded CAs can bypass authentication. NVD scores it 8.2, versions 5.3.0 to 5.9.2 are affected and 5.9.4 fixes it. OpenWrt's stock libwolfssl build enables the affected macros.

Vulnerability summary

CVSS base score

8.2

High severity

EPSS score (FIRST)

0.2%

Probability of exploitation in the wild in the next 30 days

CISA KEV catalog

No

Not listed

Published

Vulnerability ID: CVE-2026-93302 · Source: NVD

Affected components

ComponentCPEVersion range
wolfSSL (trusted peer certificate matching)cpe:2.3:a:wolfssl:wolfssl:*:*:*:*:*:*:*:*NVD: 5.3.0 through 5.9.2; fixed in 5.9.4 (commit 22bcd51d)
OpenWrt libwolfssl package—built with --enable-stunnel and, by default, --enable-wpas; 5.7.6 or 5.9.1 in OpenWrt 24.10.0-24.10.8, 5.8.4 or 5.9.1 in 25.12.0-25.12.5; 5.9.4 in 25.12.6

What does this mean for affected devices?

CVE-2026-93302 is an improper certificate validation flaw (CWE-295, per wolfSSL as CNA) that wolfSSL rates High. The 5.9.4 section of the wolfSSL ChangeLog (25 September 2026) says "MatchTrustedPeer ignores the public key used, leading to forged CA clones passing verification". Affected builds enable WOLFSSL_TRUST_PEER_CERT and load CAs with wolfSSL_CTX_trust_peer_cert() or wolfSSL_trust_peer_cert(); when OPENSSL_COMPATIBLE_DEFAULTS is also defined, the affected API widens "to include all CA certificate loading". wolfSSL says both macros are defined by autoconf builds "such as (nginx, haproxy, stunnel, wpas, apache httpd, hitch, bind, rsyslog, ffmpeg, all, distro)" and that a malicious (D)TLS server could bypass authentication "once knowing which CA's the client would accept", with mutual authentication exposed the same way. The fix is commit 22bcd51d, found via the Anthropic OSS program.

NVD gives it a Primary CVSS v3.1 score of 8.2 with vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N and lists wolfSSL 5.3.0 through 5.9.2 as affected; wolfSSL's CVSS v4.0 score is 8.3 (NVD).

OpenWrt's stock build meets the configuration condition. Its wolfSSL package Makefile passes --enable-stunnel unconditionally, with the comment that it is "needed for OpenSSL API compatibility bits", and passes --enable-wpas when WOLFSSL_HAS_WPAS is set, which the package's Config.in enables by default. In wolfSSL's configure.ac the stunnel option adds -DOPENSSL_COMPATIBLE_DEFAULTS, and that macro in turn adds -DWOLFSSL_TRUST_PEER_CERT. The same libwolfssl serves OpenWrt's wolfSSL variants of hostapd and wpad and the libustream-wolfssl TLS wrapper. OpenWrt 24.10.0 to 24.10.8 ship libwolfssl 5.7.6 or 5.9.1 and 25.12.0 to 25.12.5 ship 5.8.4 or 5.9.1, all inside the affected range; OpenWrt 25.12.6 ships 5.9.4, and the openwrt-24.10 branch moved to 5.9.4 on 2026-10-27, after the 24.10.8 tag.

Whether a given device is exploitable depends on whether the peer can know which CA certificates it trusts, which is often the case for a device that trusts a public or vendor CA. Where an upgrade must wait, wolfSSL's mitigation is to build with --disable-openssl-compatible-defaults and not load CAs through the trusted-peer APIs. Debian fixed it in sid with 5.9.2-1.1; trixie is marked as a minor issue and bookworm's wolfssl package as end-of-life (Debian security tracker).

CVE-2026-93302 is not in the CISA KEV catalog as of 2026-11-16 (catalog version 2026.11.13), and FIRST EPSS gives it 0.0024, the 14.8th percentile, in the 2026-11-15 dataset (CISA KEV, FIRST EPSS).

Our Mbed TLS and wolfSSL firmware guide explains how to read a wolfSSL configure line, and our hostapd and wpa_supplicant guide covers the Wi-Fi daemons that link it on OpenWrt. Related wolfSSL certificate flaws are CVE-2026-5194 and CVE-2026-94418.

How to fix this class of issueThis advisory's weakness class is Authentication bypass. Our practical guide covers how to detect, fix, verify and disclose it: How to fix authentication bypass in embedded firmware.

Evidence

  • MatchTrustedPeer ignores the public key; WOLFSSL_TRUST_PEER_CERT and OPENSSL_COMPATIBLE_DEFAULTS conditions; macros defined by stunnel, wpas and other autoconf builds; affected 5.3.0 to 5.9.2; mitigation --disable-openssl-compatible-defaults; fixed in commit 22bcd51d; released in 5.9.4 (25 September 2026). — wolfSSL ChangeLog (5.9.4)
  • High rating, fixed in 5.9.4. — wolfSSL security vulnerabilities page
  • NVD Primary CVSS v3.1 8.2 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N); CNA CVSS v4.0 8.3; CPE range 5.3.0 through 5.9.2. — NVD
  • OpenWrt passes --enable-stunnel unconditionally and --enable-wpas when WOLFSSL_HAS_WPAS is set; libwolfssl 5.9.1 at v24.10.8. — OpenWrt wolfSSL Makefile (v24.10.8)
  • WOLFSSL_HAS_WPAS defaults to y. — OpenWrt wolfSSL Config.in (v24.10.8)
  • --enable-stunnel adds -DOPENSSL_COMPATIBLE_DEFAULTS, which adds -DWOLFSSL_TRUST_PEER_CERT. — wolfSSL configure.ac (v5.9.2-stable)
  • OpenWrt 25.12 branch updated to wolfSSL 5.9.4 (in tag v25.12.6). — OpenWrt commit 66673aad
  • Debian: sid fixed in 5.9.2-1.1; trixie no-dsa; bookworm end-of-life. — Debian security tracker
  • Not in the CISA KEV catalog as of 2026-11-16 (catalog version 2026.11.13). — CISA KEV
  • EPSS 0.00237 (14.8th percentile), dataset 2026-11-15, read 2026-11-16. — FIRST EPSS

Related advisories

Sources

  1. NVD
  2. wolfSSL: Security Vulnerabilities
  3. wolfSSL ChangeLog.md (release 5.9.4)
  4. wolfSSL commit 22bcd51d (fix)
  5. OpenWrt wolfSSL package Makefile (v24.10.8)
  6. OpenWrt wolfSSL package Config.in (v24.10.8)
  7. wolfSSL configure.ac (v5.9.2-stable)
  8. OpenWrt commit: wolfssl update to 5.9.4 (openwrt-25.12)
  9. Debian security tracker
  10. CISA KEV
  11. FIRST EPSS

Frequently asked questions

Which wolfSSL builds are affected by CVE-2026-93302?

Builds that define WOLFSSL_TRUST_PEER_CERT and load CAs through wolfSSL_CTX_trust_peer_cert() or wolfSSL_trust_peer_cert(), and every CA load once OPENSSL_COMPATIBLE_DEFAULTS is also defined. wolfSSL says autoconf builds such as stunnel, wpas, nginx, all and distro define both, in versions 5.3.0 to 5.9.2 (per the wolfSSL ChangeLog).

Does the OpenWrt libwolfssl build meet the condition?

Yes. OpenWrt's Makefile passes --enable-stunnel unconditionally and --enable-wpas by default, and in wolfSSL's configure.ac the stunnel option defines OPENSSL_COMPATIBLE_DEFAULTS, which defines WOLFSSL_TRUST_PEER_CERT. OpenWrt 25.12.6 ships the fixed 5.9.4; 24.10.8 ships 5.9.1 (per the OpenWrt Makefile and wolfSSL configure.ac).

How can CVE-2026-93302 be mitigated without upgrading?

wolfSSL's mitigation is to build with --disable-openssl-compatible-defaults and not load CAs with wolfSSL_CTX_trust_peer_cert() or wolfSSL_trust_peer_cert(); otherwise update to 5.9.4 or apply the fix commit (per the wolfSSL ChangeLog).

Is CVE-2026-93302 in the CISA KEV catalog?

No, not as of 2026-11-16 (catalog version 2026.11.13). FIRST EPSS gives it 0.0024, the 14.8th percentile, in the 2026-11-15 dataset (per CISA KEV and FIRST EPSS).