CVE-2026-93302
Wolfssl: authentication bypass
- Risk score
- 56/100
- CVSS
- 8.2 v3.1
- Exploit chance (30 days)
- 0.2%
- Published
- 27 Sep 2026
Open in the live forecast Today's forecast
What to know
- What it is
- MatchTrustedPeer ignores the public key used, leading to forged CA clones passing verification. Affected builds are any that enable the macro WOLFSSL_TRUST_PEER_CERT and load CA certificates with wolfSSL_CTX_trust_peer_cert() or wolfSSL_trust_peer_cert(). The peer must know the certificates being loaded to either of t…
- Affected
- Wolfssl
- Fix
- Apply the vendor's security update; see the linked advisory.
- Exploitation
- No known exploitation
Story map
At a glance
Wolfssl: Amber, patch this week. A certificate with no dNSName SAN but another SAN type present (e.g. registeredID or iPAddress) bypassed the Subject CN dNSName name-constraint check. The CN-as-DNS fallback was gated on cert->subjectCN != NULL && cert->altNames == NULL && !cert->isCA instead of "no dNSName SAN", so an out-of-scope CN was accepted. Th…
The flaws
- CVE-2026-93302: Authentication bypass (CVSS 8.2 · EPSS 0%)
- CVE-2026-89134: A certificate with no dNSName SAN but another SAN type present (e.g (CVSS 9.1 · EPSS 0%)
- CVE-2026-94418: Under WOLFSSL_SMALL_CERT_VERIFY, ProcessPeerCertParse() runs the certificate signature check… (CVSS 7.5 · EPSS 0%)
- CVE-2026-89102: In wolfSSL versions 5.7.2 through 5.9.2 there is a client-side implementation flaw in RFC 6961… (CVSS 6.5 · EPSS 0%)
The fix
Fix: Apply the vendor's security update; see the linked advisory.
Who is exposed: Wolfssl
Where it stands
- No known exploitation
Connects to
- Same weakness: CWE-295 (CWE-295). 80 other warnings in 30 days
- Same product: Earlier Wolfssl warnings. 6 in the last 90 days
Why it is Yellow
- CVSS 8.2 high
- Remotely exploitable without logging in
References
Original description
MatchTrustedPeer ignores the public key used, leading to forged CA clones passing verification. Affected builds are any that enable the macro WOLFSSL_TRUST_PEER_CERT and load CA certificates with wolfSSL_CTX_trust_peer_cert() or wolfSSL_trust_peer_cert(). The peer must know the certificates being loaded to either of those APIs to take advantage of the issue. When OPENSSL_COMPATIBLE_DEFAULTS is also defined this widens the affected API to include all CA certificate loading. Both macros are defined when using autoconf builds such as (nginx, haproxy, stunnel, wpas, apache httpd, hitch, bind, rsyslog, ffmpeg, all, distro). When the certificate is listed as a trusted peer certificate the issue previously allowed for a malicious (D)TLS server to bypass authentication once knowing which CA’s the client would accept. This also affects mutual authentication cases where the client knows which CA’s the server has loaded. If building with any of these configurations and using (D)TLS where the loaded CA’s could be known and authentication of the peer is desired, users should either: update to the latest wolfSSL version, apply the fix patch, or use the configure flag --disable-openssl-compatible-defaults and not load CA’s with wolfSSL_CTX_trust_peer_cert() or wolfSSL_trust_peer_cert() to mitigate the issue.
Last activity 27 Sep 2026. Patch Forecast updates every hour.