wolfSSL Inc. maintains cryptographic and TLS libraries widely embedded in embedded systems, IoT devices, and resource-constrained applications, giving its products outsized impact despite a narrow portfolio. Despite the focused product line—centered on wolfSSL itself, wolfMQTT, and yaSSL—the vendor ranks among the most prominent in the vulnerability landscape because cryptographic libraries occupy a critical position in the software supply chain and reach countless downstream deployments. Vulnerabilities affecting the vendor skew strongly toward critical-severity outcomes and recur through weakness classes including out-of-bounds writes and reads, heap-based buffer overflows, and improper certificate validation that reflect the low-level parsing and cryptographic-protocol demands of TLS implementations. Defenders should prioritize inventory of products embedding these libraries, as remediation often depends on downstream vendors rebuilding and releasing patches; live severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by wolfSSL Inc. over time
Of all the CVEs published by wolfSSL Inc. as a CNA, 92.1% affect products that wolfSSL Inc. develops as a vendor.
Of all the CVEs published that affect products developed by wolfSSL Inc., 61.6% are self-published by wolfSSL Inc. as a CNA.
Signals from CVEs in this vendor scope (151 CVEs).
151 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2009-4484HIGH Multiple stack-based buffer overflows in the CertDecoder::GetName function in src/asn.cpp in TaoCrypt in yaSSL before 1.9.9, as used in mysqld in MySQL 5.0.x before 5.0.90, MySQL 5 | Dec 30, 2009 | 7.5 | 79 | NO | YES |
CVE-2017-2800CRITICAL A specially crafted x509 certificate can cause a single out of bounds byte overwrite in wolfSSL through 3.10.2 resulting in potential certificate validation vulnerabilities, denial | May 24, 2017 | 9.8 | 46 | NO | YES |
CVE-2017-13099MEDIUM wolfSSL prior to version 3.12.2 provides a weak Bleichenbacher oracle when any TLS cipher suite using RSA key exchange is negotiated. An attacker can recover the private key from a | Dec 13, 2017 | 5.9 | 44 | NO | YES |
CVE-2026-6094CRITICAL Heap buffer overread in wc_PKCS7_DecodeEnvelopedData when parsing crafted PKCS7 EnvelopedData. This could theoretically be triggered by attacker-supplied data delivered via S/MIME | Jun 25, 2026 | 9.1 | 38 | NO | NO |
CVE-2026-7531CRITICAL Use-after-free in PQC hybrid key-share handling. This is an incomplete-fix follow-up to CVE-2026-5460 (released in 5.9.1): a malicious TLS 1.3 server sending a truncated PQC hybrid | Jun 25, 2026 | 9.8 | 36 | NO | NO |
CVE-2026-11310HIGH X.509 trust-chain bypass in the OpenSSL compatibility certificate verifier (wolfSSL_X509_verify_cert()). This affects only builds with --enable-opensslextra (OPENSSL_EXTRA) and who | Jun 25, 2026 | 7.5 | 36 | NO | NO |
CVE-2026-55960HIGH Un-negotiated Raw Public Key (RFC 7250) accepted in place of an X.509 certificate, bypassing chain validation. A raw public key has no chain, so ParseCertRelative() accepts it with | Jun 25, 2026 | 7.5 | 36 | NO | NO |
CVE-2026-5194CRITICAL Missing hash/digest size and OID checks allow digests smaller than allowed when verifying ECDSA certificates, or smaller than is appropriate for the relevant key type, to be accept | Apr 9, 2026 | 9.1 | 36 | NO | NO |
CVE-2026-5187CRITICAL Two potential heap out-of-bounds write locations existed in DecodeObjectId() in wolfcrypt/src/asn.c. First, a bounds check only validates one available slot before writing two OID | Apr 9, 2026 | 9.8 | 35 | NO | NO |
CVE-2019-11873CRITICAL wolfSSL 4.0.0 has a Buffer Overflow in DoPreSharedKeys in tls13.c when a current identity size is greater than a client identity size. An attacker sends a crafted hello client pack | May 23, 2019 | 9.8 | 35 | NO | NO |
Signals from CVEs in this vendor scope (151 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by wolfSSL Inc..
Media articles that mention a CVE ID that affects a product developed by wolfSSL Inc. — matched by CVE ID, not by vendor name.