wolfSSL · weakness class
Input Validation and Logic
12 CVEs
Every dot is a CVE in what this vendor ships; the named ones are the most at risk.
Every one of the 12 is a mark on the map. Named now: 1 to 12, most at risk first.
- An issue was discovered in wolfSSL before 5.5.0. When a TLS 1.3 client connects to a wolfSSL server and SSL_clear is called on its session, the server crashes with a segmentation…
- TLS 1.3 client issue handling malicious server when not including a KSE and PSK extension
- Improper (D)TLS key boundary enforcement
- Improper Validation of AES-GCM Authentication Tag Length in PKCS#7 Envelope Allows Authentication Bypass
- Potential DoS Vulnerability through Multiple KeyShareEntry with Same Group in TLS 1.3 ClientHello
- X25519 x86_64 assembly final reduction leaves non-canonical field element
- Encrypt-then-MAC could fall back to MAC-then-Encrypt when HAVE_ENCRYPT_THEN_MAC is configured
- ML-KEM-1024 x64 AVX2 incomplete cipher text comparison enables IND-CCA2 break and static private-key recovery
- Improper key_share validation in TLS 1.3 HelloRetryRequest
- Improper Validation of Signature Algorithm Used in TLS 1.3 CertificateVerify
- (D)TLS 1.2 client accepts early ChangeCipherSpec before ClientKeyExchange
- TLS 1.2 Client Can Downgrade Digest Used
exploited in the wildcheck availableringed, named or not: CyberSIXT has reported on it
Zoom in on the map and the dots under the middle of it are named where they are.
Data as of 2026-11-15. CVE List through 2026-11-15 · EPSS of 2026-11-15 · CISA KEV checked 2026-11-15. Sources: the CVE List, CISA KEV, EPSS, NVD, nuclei templates and public bug bounty data.