wolfssl

Disclosed vulnerabilities where the NVD names wolfssl as an affected vendor, highest CVSS first.

1. CRITICAL 9.1CVE-2026-89134public PoC2026-09-27

   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 …

   wolfssl

   AI risk analysis on Exploit-DB.ai →

2. HIGH 8.2CVE-2026-93302public PoC2026-09-27

   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 …

   wolfssl

   AI risk analysis on Exploit-DB.ai →

3. HIGH 7.5CVE-2026-94418public PoC2026-09-27

   Under WOLFSSL_SMALL_CERT_VERIFY, ProcessPeerCertParse() runs the certificate signature check separately from the parse to keep peak memory down, then merges the two results, but it merged the signature result back only when the parse returned 0, so any parse e…

   wolfssl

   AI risk analysis on Exploit-DB.ai →

4. MEDIUM 6.5CVE-2026-89135public PoC2026-09-27

   A failed X509_verify_cert call permanently plants an unverified attacker CA in the shared CertManager, bypassing certificate validation in every type-blind sibling consumer (native TLS, OCSP, CRL, direct CM verify). This affects version 5.8.4 through 5.9.2 of …

   wolfssl

   AI risk analysis on Exploit-DB.ai →

5. MEDIUM 6.5CVE-2026-89102public PoC2026-09-27

   In wolfSSL versions 5.7.2 through 5.9.2 there is a client-side implementation flaw in RFC 6961, multiple OCSP response stapling, which can lead to certificate forgery. When a wolfSSL client enables OCSP stapling with the HAVE_CERTIFICATE_STATUS_REQUEST_V2 feat…

   wolfssl

   AI risk analysis on Exploit-DB.ai →

6. MEDIUM 5.4CVE-2026-94419public PoC2026-09-27

   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…

   wolfssl

   AI risk analysis on Exploit-DB.ai →

7. MEDIUM 5.3CVE-2026-94417public PoC2026-09-27

   When an application enables both OCSP and CRL revocation checking on one WOLFSSL_CTX or certificate manager, wolfSSL skips the CRL check for any peer certificate that carries no Authority Information Access OCSP URL, and accepts a certificate the loaded CRL li…

   wolfssl

   AI risk analysis on Exploit-DB.ai →

8. MEDIUM 5.3CVE-2026-89133public PoC2026-09-27

   wolfSSL versions 5.9.2 and earlier contain a flaw in the X.509 certificate validation logic where it fails to properly enforce NameConstraints extensions when there is an unconstrained CA tier between a name-constrained intermediate CA and the leaf certificate…

   wolfssl

   AI risk analysis on Exploit-DB.ai →

9. MEDIUM 5.3CVE-2026-15442public PoC2026-09-27

   In all builds that make use of (D)TLS, including default builds, there is a series of conditional states during the TLS shutdown which could lead to a heap-use-after free. If an application ended up getting a partial wolfSSL_read() which is sometimes caused by…

   wolfssl

   AI risk analysis on Exploit-DB.ai →

10. LOW 3.7CVE-2026-93304public PoC2026-09-27

    A (D)TLS 1.2 client can accept a ChangeCipherSpec message before it has sent its ClientKeyExchange. No master secret has been derived at that point, so the client installs read keys derived from a known (deterministic) key and checks the server's Finished agai…

    wolfssl

    AI risk analysis on Exploit-DB.ai →