wolfSSL

wolfSSL Inc.

CVEs, 365 days103120 all time, 0 rejected
Quality100%median 99%
CVSS by the CNA100%share of records
CWE100%share of records
Affected versions100%not n/a or unspecified
CVSS added by CISA0%lower is better
OrganisationwolfSSL Inc.
RoleCNA
TypeVendor, Open Source
Reports toicscert → CISA
ScopeTransport Layer Security (TLS) and Cryptographic issues found in wolfSSL products.
Advisorieshttps://www.wolfssl.com/docs/security-vulnerabilities/
  • CVE-2026-84897 2026-10-07 · CVSS 6.9
    src/internal.c in wolfSSL wolfSSH through 1.5.0 admits the server-to-client Diffie-Hellman group exchange messages SSH_MSG_KEX_DH_GEX_GROUP (31) and SSH_MSG_KEX
  • CVE-2026-83742 2026-10-07 · CVSS 5.3
    Unsigned integer underflow in wstrncat() in src/port.c in wolfSSL wolfSSH from v1.4.11 through v1.5.0 on non-Windows platforms allows an authenticated remote at
  • CVE-2026-83540 2026-10-07 · CVSS 7.7
    When password or public key authentication is used with the Windows port of wolfSSHd, the Windows logon token acquired for one authenticated connection is not r
  • CVE-2026-81535 2026-10-07 · CVSS 6.3
    In wolfSSH through 1.5.0 built with --enable-fwd, DoChannelOpen() in src/internal.c gates only direct-tcpip channel opens with the forwarding policy callback. f
  • CVE-2026-16516 2026-10-07 · CVSS 9.0
    wolfSSH does not validate that the ECDSA curve identifier in a KEXDH_REPLY host key blob matches the algorithm negotiated during key exchange. In ParseECCPubKey
  • CVE-2026-15442 2026-09-27 · CVSS 2.3
    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-
  • CVE-2026-89102 2026-09-27 · CVSS 8.3
    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 f
  • CVE-2026-89133 2026-09-27 · CVSS 6.3
    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 t
  • CVE-2026-89134 2026-09-27 · CVSS 6.3
    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
  • CVE-2026-89135 2026-09-27 · CVSS 6.3
    A failed X509_verify_cert call permanently plants an unverified attacker CA in the shared CertManager, bypassing certificate validation in every type-blind sibl
  • CVE-2026-89136 2026-09-27 · CVSS 8.3
    When using RPK (Raw Public Key), the client side of a TLS 1.2, 1.3 and DTLS 1.2 connection could accept an unsolicited server_cert_type=RawPublicKey which allow
  • CVE-2026-93302 2026-09-27 · CVSS 8.3
    MatchTrustedPeer ignores the public key used, leading to forged CA clones passing verification. Affected builds are any that enable the macro WOLFSSL_TRUST_PEER
  • CVE-2026-93304 2026-09-27 · CVSS 6.3
    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 clie
  • CVE-2026-94417 2026-09-27 · CVSS 2.3
    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 certificat
  • CVE-2026-94418 2026-09-27 · CVSS 2.3
    Under WOLFSSL_SMALL_CERT_VERIFY, ProcessPeerCertParse() runs the certificate signature check separately from the parse to keep peak memory down, then merges the
  • CVE-2026-94419 2026-09-27 · CVSS 2.3
    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)} int
  • CVE-2026-81341 2026-08-28 · CVSS 6.5
    wolfEngine before 1.4.1 sources the explicit AES-CCM nonce for TLS 1.2 and DTLS 1.2 records from the record input buffer instead of the TLS sequence number carr
  • CVE-2026-81020 2026-08-28 · CVSS 7.4
    wolfEngine before 1.4.1 generates the 8-byte explicit AES-GCM nonce once when the TLS write key is set and never increments it per record. As a result every TLS
  • CVE-2026-81019 2026-08-28 · CVSS 7.4
    wolfProvider before 1.2.2 generates the 8-byte explicit AES-GCM nonce once when the TLS write key is set and never increments it per record. As a result every T
  • CVE-2026-7511 2026-06-25 · CVSS 5.9
    PKCS7_verify signer confusion allows forged signatures, where the signer associated with a signature is not correctly bound, permitting a forged signature to be
  • CVE-2026-7532 2026-06-25 · CVSS 5.7
    iPAddress name constraints bypass when WOLFSSL_IP_ALT_NAME is not defined. IP address name constraints are not enforced in that configuration, allowing a certif
  • CVE-2026-8720 2026-06-25 · CVSS 5.9
    wc_Blake2bHmacFinal and wc_Blake2sHmacFinal discard the message when the key length exceeds the block size, producing a MAC that is independent of the input. Wh
  • CVE-2026-10098 2026-06-25 · CVSS 6.3
    OCSP CertID serial-number length-confusion in wolfSSL_OCSP_resp_find_status allows a same-issuer SingleResponse whose serial is a prefix of the target serial to
  • CVE-2026-11703 2026-06-25 · CVSS 6.0
    Missing SNI/ALPN binding on stateful (session-ID) resumption, which previously skipped the binding check performed for ticket-based resumption. A cached session
  • CVE-2026-55962 2026-06-25 · CVSS 6.0
    TLS 1.3 post-handshake authentication (PHA) issue where a server could accept a client's Finished message without the client having sent a Certificate and Certi

All CVE Program partners