VYPR

Wolfssl

by WolfSSL

Source repositories

CVEs (154)

  • CVE-2025-11932MedNov 21, 2025
    risk 0.28cvss 4.3epss 0.00

    The server previously verified the TLS 1.3 PSK binder using a non-constant time method which could potentially leak information about the PSK binder

  • CVE-2026-94417MedSep 27, 2026
    risk 0.27cvss 5.3epss 0.00

    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 lists as revoked. The…

  • CVE-2026-89133MedSep 27, 2026
    risk 0.27cvss 5.3epss 0.00

    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…

  • CVE-2026-15442MedSep 27, 2026
    risk 0.27cvss 5.3epss 0.00

    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 a small user…

  • CVE-2026-6092MedJun 25, 2026
    risk 0.27cvss 5.3epss 0.00

    When HAVE_ENCRYPT_THEN_MAC is configured, the implementation could fall back to MAC-then-Encrypt rather than enforcing Encrypt-then-MAC.

  • CVE-2026-10098MedJun 25, 2026
    risk 0.27cvss 5.3epss 0.00

    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 be reported as the revocation status of a different certificate. The lookup compared serial-number bytes without first…

  • CVE-2026-6681MedJun 25, 2026
    risk 0.27cvss 5.3epss 0.00

    The PKCS#7 decode path ignores the caller-supplied output buffer size (outputSz), allowing decoded content to be written past the bounds of the provided buffer. This affects wolfSSL 5.9.0 and earlier and was fixed in the 5.9.1 release.

  • CVE-2026-6678MedJun 25, 2026
    risk 0.27cvss 5.3epss 0.00

    Integer underflow in wc_PKCS7_DecryptOri when handling crafted Other Recipient Info, leading to incorrect length handling during decryption.

  • CVE-2026-6450MedJun 25, 2026
    risk 0.27cvss 5.3epss 0.00

    A CRL critical extension bypass exists in ParseCRL_Extensions where critical extensions are not properly enforced, allowing a crafted CRL with an unhandled critical extension to be accepted. This only affects builds with CRL support enabled and where a crafted CRL had a trusted…

  • CVE-2026-55964MedJun 25, 2026
    risk 0.27cvss 5.3epss 0.00

    Chain intermediate CA:TRUE without keyCertSign accepted as a signing CA. Intermediate CA certificates are required to have the keyCertSign key usage when a Key Usage extension is present, but chain-supplied temporary CAs (WOLFSSL_TEMP_CA) added while building a certificate path…

  • CVE-2026-10592MedJun 25, 2026
    risk 0.27cvss 5.3epss 0.00

    Certificates with wildcard DNS SANs (e.g. *.example.com) bypassed CA name-constraint checks. A certificate with a wildcard DNS SAN that should be rejected by the issuing CA's permitted/excluded DNS name constraints could be accepted.

  • CVE-2026-5504MedApr 9, 2026
    risk 0.27cvss 5.3epss 0.00

    A padding oracle exists in wolfSSL's PKCS7 CBC decryption that could allow an attacker to recover plaintext through repeated decryption queries with modified ciphertext. In previous versions of wolfSSL the interior padding bytes are not validated.

  • CVE-2026-5772MedApr 9, 2026
    risk 0.27cvss 5.3epss 0.00

    A 1-byte stack buffer over-read was identified in the MatchDomainName function (src/internal.c) during wildcard hostname validation when the LEFT_MOST_WILDCARD_ONLY flag is active. If a wildcard * exhausts the entire hostname string, the function reads one byte past the buffer…

  • CVE-2026-3503MedMar 19, 2026
    risk 0.27cvss 5.2epss 0.00

    Protection mechanism failure in wolfCrypt post-quantum implementations (ML-KEM and ML-DSA) in wolfSSL on ARM Cortex-M microcontrollers allows a physical attacker to compromise key material and/or cryptographic outcomes via induced transient faults that corrupt or redirect…

  • CVE-2026-1005MedMar 19, 2026
    risk 0.27cvss 5.3epss 0.00

    Integer underflow in wolfSSL packet sniffer <= 5.8.4 allows an attacker to cause a buffer overflow in the AEAD decryption path by injecting a TLS record shorter than the explicit IV plus authentication tag into traffic inspected by ssl_DecodePacket. The underflow wraps a 16-bit…

  • CVE-2024-1543MedAug 29, 2024
    risk 0.27cvss 4.1epss 0.00

    The side-channel protected T-Table implementation in wolfSSL up to version 5.6.5 protects against a side-channel attacker with cache-line resolution. In a controlled environment such as Intel SGX, an attacker can gain a per instruction sub-cache-line resolution allowing them to…

  • CVE-2026-3580MedMar 19, 2026
    risk 0.24cvss 4.7epss 0.00

    In wolfSSL 5.8.4, constant-time masking logic in sp_256_get_entry_256_9 is optimized into conditional branches (bnez) by GCC when targeting RISC-V RV32I with -O3. This transformation breaks the side-channel resistance of ECC scalar multiplication, potentially allowing a local…

  • CVE-2026-6412MedJun 25, 2026
    risk 0.21cvss 4.3epss 0.00

    Certificate policy and RFC 8446 compliance concerns regarding the continued acceptance of SHA-1/MD5 in certificate processing.

  • CVE-2026-5448MedApr 10, 2026
    risk 0.21cvss 4.3epss 0.00

    X.509 date buffer overflow in wolfSSL_X509_notAfter / wolfSSL_X509_notBefore. A buffer overflow may occur when parsing date fields from a crafted X.509 certificate via the compatibility layer API. This is only triggered when calling these two APIs directly from an application,…

  • CVE-2026-5507MedApr 9, 2026
    risk 0.19cvss 4.0epss 0.00

    When restoring a session from cache, a pointer from the serialized session data is used in a free operation without validation. An attacker who can poison the session cache could trigger an arbitrary free. Exploitation requires the ability to inject a crafted session into the…

Page 7 of 8