<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="rss.xsl"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>wolfSSL Inc. — recent CVEs</title>
    <link>https://vulnogram.org/</link>
    <atom:link href="https://vulnogram.org/rss/wolfssl" rel="self" type="application/rss+xml"/>
    <description>Most recent CVEs assigned by wolfSSL Inc. (wolfssl).</description>
    <image>
      <url>https://vulnogram.org/seaview/icons/wolfssl.png</url>
      <title>wolfSSL Inc. — recent CVEs</title>
      <link>https://vulnogram.org/</link>
    </image>
    <lastBuildDate>Wed, 21 Oct 2026 07:00:07 GMT</lastBuildDate>
    <item>
      <title>CVE-2026-84897 · 6.9 MEDIUM 🌩️ — wolfSSH server accepts server-to-client DH group exchange messages from an unauthenticated client, causing pre-authentication primality-test CPU exhaustion and key exchange role confusion</title>
      <link>https://vulnogram.org/CVE-2026-84897</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-84897</guid>
      <description>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_DH_GEX_REPLY (33) when a server receives them from an unauthenticated client. IsMessageAl…</description>
      <category>Medium</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 07 Oct 2026 02:42:28 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-83742 · 5.3 MEDIUM — wstrncat() unsigned integer underflow leads to an off-by-one null write in wolfSSH on non-Windows platforms</title>
      <link>https://vulnogram.org/CVE-2026-83742</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-83742</guid>
      <description>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 attacker to write one out-of-bounds null byte past the end of a stack buffer by sending a cr…</description>
      <category>Medium</category>
      <pubDate>Wed, 07 Oct 2026 02:41:48 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-83540 · 7.7 HIGH — wolfSSHd on Windows race condition leading to logon token reused across connections</title>
      <link>https://vulnogram.org/CVE-2026-83540</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-83540</guid>
      <description>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 released before a token is acquired for a subsequent connection, resulting in user login po…</description>
      <category>High</category>
      <pubDate>Wed, 07 Oct 2026 02:40:35 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-81535 · 6.3 MEDIUM 🌩️ — wolfSSH SSH client accepts unsolicited forwarded-tcpip channel opens without an authorization check</title>
      <link>https://vulnogram.org/CVE-2026-81535</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-81535</guid>
      <description>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. forwarded-tcpip opens are admitted without an authorization check and are not capped in num…</description>
      <category>Medium</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 07 Oct 2026 02:39:27 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-16516 · 9 CRITICAL 🌩️ — wolfSSH ECDSA host key curve not validated against negotiated algorithm</title>
      <link>https://vulnogram.org/CVE-2026-16516</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-16516</guid>
      <description>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() (src/internal.c), the blob&apos;s algorithm string is used to derive the curve via NameToId/…</description>
      <category>Critical</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 07 Oct 2026 02:38:23 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-15442 · 2.3 LOW — Heap use-after-free on read during bidirectional (D)TLS shutdown</title>
      <link>https://vulnogram.org/CVE-2026-15442</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-15442</guid>
      <description>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…</description>
      <category>Low</category>
      <pubDate>Sun, 27 Sep 2026 09:24:31 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-89102 · 8.3 HIGH 🌩️ — OCSP stapling v2 multi accepts non-CA chain certificates as issuers</title>
      <link>https://vulnogram.org/CVE-2026-89102</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-89102</guid>
      <description>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_REQUE…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Sun, 27 Sep 2026 09:22:42 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-89133 · 6.3 MEDIUM 🌩️ — NameConstraints not enforced across unconstrained intermediate CA</title>
      <link>https://vulnogram.org/CVE-2026-89133</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-89133</guid>
      <description>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 c…</description>
      <category>Medium</category>
      <category>Network Exploitable</category>
      <pubDate>Sun, 27 Sep 2026 09:18:43 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-89134 · 6.3 MEDIUM 🌩️ — Subject CN name-constraint check bypassed when non-DNS SAN present</title>
      <link>https://vulnogram.org/CVE-2026-89134</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-89134</guid>
      <description>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-&gt;subjectCN != NULL &amp;&amp; cert-&gt;altNames == NULL &amp;&amp; !cert-&gt;isC…</description>
      <category>Medium</category>
      <category>Network Exploitable</category>
      <pubDate>Sun, 27 Sep 2026 09:16:58 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-89135 · 6.3 MEDIUM 🌩️ — Failed X509_verify_cert leaves unverified CA in shared CertManager</title>
      <link>https://vulnogram.org/CVE-2026-89135</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-89135</guid>
      <description>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…</description>
      <category>Medium</category>
      <category>Network Exploitable</category>
      <pubDate>Sun, 27 Sep 2026 09:14:44 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-89136 · 8.3 HIGH 🌩️ — Client accepts unsolicited RawPublicKey server certificate type</title>
      <link>https://vulnogram.org/CVE-2026-89136</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-89136</guid>
      <description>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 allowed a malicious or misbehaving server to bypass authentication. RPK is off by default and o…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Sun, 27 Sep 2026 09:12:39 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-93302 · 8.3 HIGH 🌩️ — Trusted peer certificate match ignores public key, allowing forged CA clones</title>
      <link>https://vulnogram.org/CVE-2026-93302</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-93302</guid>
      <description>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_ce…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Sun, 27 Sep 2026 09:07:35 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-93304 · 6.3 MEDIUM 🌩️ — (D)TLS 1.2 client accepts early ChangeCipherSpec before ClientKeyExchange</title>
      <link>https://vulnogram.org/CVE-2026-93304</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-93304</guid>
      <description>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&apos;s Fin…</description>
      <category>Medium</category>
      <category>Network Exploitable</category>
      <pubDate>Sun, 27 Sep 2026 09:05:37 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-94417 · 2.3 LOW — CRL check skipped when OCSP enabled and certificate has no OCSP URL</title>
      <link>https://vulnogram.org/CVE-2026-94417</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-94417</guid>
      <description>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 loa…</description>
      <category>Low</category>
      <pubDate>Sun, 27 Sep 2026 09:00:59 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-94418 · 2.3 LOW — Signature failure masked by date error under WOLFSSL_SMALL_CERT_VERIFY</title>
      <link>https://vulnogram.org/CVE-2026-94418</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-94418</guid>
      <description>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 a…</description>
      <category>Low</category>
      <pubDate>Sun, 27 Sep 2026 08:58:56 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-94419 · 2.3 LOW — Client session cache reference poisoning allows resumption with wrong server</title>
      <link>https://vulnogram.org/CVE-2026-94419</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-94419</guid>
      <description>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…</description>
      <category>Low</category>
      <pubDate>Sun, 27 Sep 2026 08:54:18 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-81341 · 6.5 MEDIUM 🌩️ — wolfEngine reuses the AES-CCM nonce on TLS 1.2 / DTLS 1.2 records</title>
      <link>https://vulnogram.org/CVE-2026-81341</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-81341</guid>
      <description>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 carried in the additional authenticated data. Because the record layer leaves the explicit-non…</description>
      <category>Medium</category>
      <category>Network Exploitable</category>
      <pubDate>Fri, 28 Aug 2026 14:43:43 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-81020 · 7.4 HIGH 🌩️ — wolfEngine reuses the AES-GCM nonce on every TLS 1.2 / DTLS 1.2 record</title>
      <link>https://vulnogram.org/CVE-2026-81020</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-81020</guid>
      <description>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 1.2 and DTLS 1.2 AES-GCM record within a connection is encrypted under an identical key a…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Fri, 28 Aug 2026 14:42:59 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-81019 · 7.4 HIGH 🌩️ — wolfProvider reuses the AES-GCM nonce on every TLS 1.2 / DTLS 1.2 record</title>
      <link>https://vulnogram.org/CVE-2026-81019</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-81019</guid>
      <description>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 TLS 1.2 and DTLS 1.2 AES-GCM record within a connection is encrypted under an identical key…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Fri, 28 Aug 2026 14:42:01 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-7511 · 5.9 MEDIUM — PKCS7_verify signer confusion allows forged signatures to be accepted</title>
      <link>https://vulnogram.org/CVE-2026-7511</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-7511</guid>
      <description>PKCS7_verify signer confusion allows forged signatures, where the signer associated with a signature is not correctly bound, permitting a forged signature to be accepted.</description>
      <category>Medium</category>
      <pubDate>Thu, 25 Jun 2026 21:32:29 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-7532 · 5.7 MEDIUM — iPAddress name constraints not enforced when WOLFSSL_IP_ALT_NAME is undefined</title>
      <link>https://vulnogram.org/CVE-2026-7532</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-7532</guid>
      <description>iPAddress name constraints bypass when WOLFSSL_IP_ALT_NAME is not defined. IP address name constraints are not enforced in that configuration, allowing a certificate to bypass an issuing CA&apos;s IP address constraints.</description>
      <category>Medium</category>
      <pubDate>Thu, 25 Jun 2026 21:31:11 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-8720 · 5.9 MEDIUM — HMAC-BLAKE2 final discards message when key length exceeds block size</title>
      <link>https://vulnogram.org/CVE-2026-8720</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-8720</guid>
      <description>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. When the supplied key is longer than the BLAKE2 block size the key-hashing branch reinitiali…</description>
      <category>Medium</category>
      <pubDate>Thu, 25 Jun 2026 21:18:29 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-10098 · 6.3 MEDIUM 🌩️ — OCSP CertID serial-number length-confusion in wolfSSL_OCSP_resp_find_status</title>
      <link>https://vulnogram.org/CVE-2026-10098</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-10098</guid>
      <description>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 seri…</description>
      <category>Medium</category>
      <category>Network Exploitable</category>
      <pubDate>Thu, 25 Jun 2026 21:16:45 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-11703 · 6 MEDIUM — Missing SNI/ALPN binding on stateful (session-ID) TLS session resumption</title>
      <link>https://vulnogram.org/CVE-2026-11703</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-11703</guid>
      <description>Missing SNI/ALPN binding on stateful (session-ID) resumption, which previously skipped the binding check performed for ticket-based resumption. A cached session could be resumed under a different SNI/ALPN than originally negotiated and, where client-…</description>
      <category>Medium</category>
      <pubDate>Thu, 25 Jun 2026 21:15:20 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-55962 · 6 MEDIUM — TLS 1.3 post-handshake authentication: server accepts Finished without client Certificate/CertificateVerify</title>
      <link>https://vulnogram.org/CVE-2026-55962</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-55962</guid>
      <description>TLS 1.3 post-handshake authentication (PHA) issue where a server could accept a client&apos;s Finished message without the client having sent a Certificate and CertificateVerify. The post-handshake-auth exemption that allows an empty/absent peer certifica…</description>
      <category>Medium</category>
      <pubDate>Thu, 25 Jun 2026 21:12:38 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-6092 · 2.1 LOW — Encrypt-then-MAC could fall back to MAC-then-Encrypt when HAVE_ENCRYPT_THEN_MAC is configured</title>
      <link>https://vulnogram.org/CVE-2026-6092</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-6092</guid>
      <description>When HAVE_ENCRYPT_THEN_MAC is configured, the implementation could fall back to MAC-then-Encrypt rather than enforcing Encrypt-then-MAC.</description>
      <category>Low</category>
      <pubDate>Thu, 25 Jun 2026 21:06:20 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-6325 · 2 LOW — Out-of-bounds write in SetSuitesHashSigAlgo on oversized signature algorithms list</title>
      <link>https://vulnogram.org/CVE-2026-6325</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-6325</guid>
      <description>Out-of-bounds write in SetSuitesHashSigAlgo when processing an oversized signature algorithms list, allowing a write past the bounds of the destination buffer.</description>
      <category>Low</category>
      <pubDate>Thu, 25 Jun 2026 21:04:31 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-6329 · 6 MEDIUM — PKCS#12 MAC verification uses attacker-controlled comparison length</title>
      <link>https://vulnogram.org/CVE-2026-6329</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-6329</guid>
      <description>PKCS#12 MAC verification uses an attacker-controlled comparison length, weakening the integrity check on the MAC and allowing a mismatched MAC to be accepted. The PKCS#12 verify path compared the locally computed HMAC against the MAC parsed from the…</description>
      <category>Medium</category>
      <pubDate>Thu, 25 Jun 2026 21:02:45 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-6330 · 6.3 MEDIUM 🌩️ — ML-KEM ARM64 NEON ciphertext comparison only compares half of the input</title>
      <link>https://vulnogram.org/CVE-2026-6330</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-6330</guid>
      <description>The ML-KEM ARM64 NEON ciphertext comparison only compares half of the input, breaking the Fujisaki-Okamoto transform&apos;s implicit rejection and weakening IND-CCA2 security on that code path. The constant-time comparison effectively ignored part of the…</description>
      <category>Medium</category>
      <category>Network Exploitable</category>
      <pubDate>Thu, 25 Jun 2026 21:01:19 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-6331 · 2.1 LOW — HMAC zero-length tag forgery in EVP_DigestVerifyFinal</title>
      <link>https://vulnogram.org/CVE-2026-6331</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-6331</guid>
      <description>HMAC zero-length tag forgery in EVP_DigestVerifyFinal, where a zero-length tag could be accepted as valid during HMAC verification. In the OpenSSL-compatibility HMAC verify path the supplied signature length was only checked as not exceeding the MAC…</description>
      <category>Low</category>
      <pubDate>Thu, 25 Jun 2026 20:56:25 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-6412 · 2.3 LOW — Continued acceptance of SHA-1/MD5 digests in certificate processing</title>
      <link>https://vulnogram.org/CVE-2026-6412</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-6412</guid>
      <description>Certificate policy and RFC 8446 compliance concerns regarding the continued acceptance of SHA-1/MD5 in certificate processing.</description>
      <category>Low</category>
      <pubDate>Thu, 25 Jun 2026 20:38:29 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-6450 · 1 LOW — CRL critical extension bypass in ParseCRL_Extensions</title>
      <link>https://vulnogram.org/CVE-2026-6450</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-6450</guid>
      <description>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…</description>
      <category>Low</category>
      <pubDate>Thu, 25 Jun 2026 20:18:53 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-6678 · 1 LOW — Integer underflow in wc_PKCS7_DecryptOri handling crafted Other Recipient Info</title>
      <link>https://vulnogram.org/CVE-2026-6678</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-6678</guid>
      <description>Integer underflow in wc_PKCS7_DecryptOri when handling crafted Other Recipient Info, leading to incorrect length handling during decryption.</description>
      <category>Low</category>
      <pubDate>Thu, 25 Jun 2026 20:16:08 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-6679 · 8.8 HIGH 🌩️ — DTLS 1.3 ACK serialization heap buffer overflow via integer truncation</title>
      <link>https://vulnogram.org/CVE-2026-6679</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-6679</guid>
      <description>A heap buffer overflow could occur in the DTLS 1.3 ACK serialization path before the connecting peer is authenticated. The buffer overflow was due to an integer truncation when computing the length of the ACK record-number list, causing an undersized…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Thu, 25 Jun 2026 20:13:06 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-6681 · 1 LOW — PKCS#7 decode ignores caller output buffer size, writing past buffer bounds</title>
      <link>https://vulnogram.org/CVE-2026-6681</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-6681</guid>
      <description>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.</description>
      <category>Low</category>
      <pubDate>Thu, 25 Jun 2026 20:11:39 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-6731 · 6 MEDIUM — X.509 name constraint bypass via Subject CN treated as a DNS name</title>
      <link>https://vulnogram.org/CVE-2026-6731</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-6731</guid>
      <description>X.509 name constraint bypass via the Subject Common Name when treated as a DNS-type name. A certificate whose Subject CN violates an issuing CA&apos;s DNS name constraints could be accepted.</description>
      <category>Medium</category>
      <pubDate>Thu, 25 Jun 2026 20:08:13 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-7531 · 2.3 LOW 🌩️ — Use-after-free in PQC hybrid key-share handling</title>
      <link>https://vulnogram.org/CVE-2026-7531</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-7531</guid>
      <description>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 KeyShare can still trigger the error cleanup path to operate on freed…</description>
      <category>Low</category>
      <category>Network Exploitable</category>
      <pubDate>Thu, 25 Jun 2026 20:01:16 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-10097 · 8.3 HIGH 🌩️ — ML-KEM-1024 x64 AVX2 incomplete cipher text comparison enables IND-CCA2 break and static private-key recovery</title>
      <link>https://vulnogram.org/CVE-2026-10097</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-10097</guid>
      <description>wolfSSL&apos;s AVX2-optimized ML-KEM implementation (mlkem_cmp_avx2) compares only 1536 of the 1568 ciphertext bytes during the Fujisaki-Okamoto re-encryption check in ML-KEM-1024 decapsulation. Ciphertexts that differ from the expected re-encryption sole…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Thu, 25 Jun 2026 19:59:30 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-10512 · 2.3 LOW — X25519 x86_64 assembly final reduction leaves non-canonical field element</title>
      <link>https://vulnogram.org/CVE-2026-10512</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-10512</guid>
      <description>The X25519 x86_64 assembly implementation fails to clear the most significant bit during the final modular reduction, so the computed result may not be fully reduced modulo the field prime 2^255 - 19. This can leave the field element in a non-canonic…</description>
      <category>Low</category>
      <pubDate>Thu, 25 Jun 2026 19:58:16 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-10592 · 6.3 MEDIUM 🌩️ — Wildcard DNS SAN bypasses CA name-constraint checks</title>
      <link>https://vulnogram.org/CVE-2026-10592</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-10592</guid>
      <description>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&apos;s permitted/excluded DNS name constraints could be accepted.</description>
      <category>Medium</category>
      <category>Network Exploitable</category>
      <pubDate>Thu, 25 Jun 2026 19:40:11 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-11310 · 8.7 HIGH 🌩️ — X.509 trust-chain bypass in wolfSSL_X509_verify_cert() via untrusted intermediate anchoring</title>
      <link>https://vulnogram.org/CVE-2026-11310</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-11310</guid>
      <description>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 whose application validates certificates by calling X509_verify_cert() wi…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Thu, 25 Jun 2026 19:38:19 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-12340 · 6.3 MEDIUM 🌩️ — Out-of-bounds heap read in SM2/SM3 certificate Subject Key Identifier computation</title>
      <link>https://vulnogram.org/CVE-2026-12340</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-12340</guid>
      <description>Out-of-bounds heap read during SM2/SM3 certificate signature verification. When parsing a certificate with an SM3wSM2 signature, the Subject Key Identifier computation reads the trailing 65 bytes of the public key without checking that the key is at…</description>
      <category>Medium</category>
      <category>Network Exploitable</category>
      <pubDate>Thu, 25 Jun 2026 19:36:21 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-55958 · 8.3 HIGH 🌩️ — Renesas TSIP TLS 1.3 transcript buffer out-of-bounds write in tsip_StoreMessage</title>
      <link>https://vulnogram.org/CVE-2026-55958</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-55958</guid>
      <description>Out-of-bounds write in the Renesas TSIP TLS 1.3 transcript buffer. In tsip_StoreMessage() the capacity check guarding the fixed message bag (MSGBAG_SIZE) sets an error code but fails to return, so execution falls through to an XMEMCPY that writes pas…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Thu, 25 Jun 2026 19:35:21 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-55960 · 8.2 HIGH 🌩️ — Un-negotiated Raw Public Key (RFC 7250) accepted in place of X.509, bypassing chain validation</title>
      <link>https://vulnogram.org/CVE-2026-55960</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-55960</guid>
      <description>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 without performing any trust verification; it must therefore only be accep…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Thu, 25 Jun 2026 19:31:55 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-55964 · 6.3 MEDIUM 🌩️ — Chain intermediate CA:TRUE without keyCertSign accepted as a signing CA (temporary CA exemption)</title>
      <link>https://vulnogram.org/CVE-2026-55964</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-55964</guid>
      <description>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…</description>
      <category>Medium</category>
      <category>Network Exploitable</category>
      <pubDate>Thu, 25 Jun 2026 19:30:34 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-11999 · 8.2 HIGH 🌩️ — X.509 trust-chain bypass via path-depth exhaustion in wolfSSL_X509_verify_cert()</title>
      <link>https://vulnogram.org/CVE-2026-11999</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-11999</guid>
      <description>X.509 trust-chain bypass (path-depth exhaustion) in the OpenSSL compatibility certificate verifier (wolfSSL_X509_verify_cert()). This affects only builds with --enable-opensslextra whose application calls X509_verify_cert() with caller-supplied untru…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Thu, 25 Jun 2026 16:56:14 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-55967 · 2 LOW — AES-GCM streaming APIs do not reject &gt;64 GiB cumulative single messages, enabling counter wrap and keystream reuse</title>
      <link>https://vulnogram.org/CVE-2026-55967</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-55967</guid>
      <description>AES-GCM encryption/decryption with extremely large cumulative single message sizes (&gt;64 GiB) were not properly rejected by the streaming APIs, allowing counter wrap, keystream reuse, and consequent plaintext recovery.</description>
      <category>Low</category>
      <pubDate>Thu, 25 Jun 2026 16:53:14 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-55961 · 8.2 HIGH 🌩️ — wolfSSL_PKCS7_verify() reports success for degenerate (certs-only) PKCS#7 with no signer</title>
      <link>https://vulnogram.org/CVE-2026-55961</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-55961</guid>
      <description>wolfSSL_PKCS7_verify() returning success for a degenerate (certs-only) PKCS#7 object that contains no signer. Such an object has empty signerInfos, so the underlying signed-data verification succeeds without authenticating any content. The compatibil…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Thu, 25 Jun 2026 16:51:18 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-6091 · 6 MEDIUM — Partial-chain verification accepts untrusted intermediate as trust anchor</title>
      <link>https://vulnogram.org/CVE-2026-6091</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-6091</guid>
      <description>Partial-chain certificate verification may accept chains that terminate at a peer-supplied, untrusted intermediate certificate rather than a trusted anchor. An attacker could present a chain that ends at an intermediate they control and have it accep…</description>
      <category>Medium</category>
      <pubDate>Thu, 25 Jun 2026 16:46:12 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-6291 · 6 MEDIUM — Bleichenbacher padding oracle in PKCS#7 KTRI RSA PKCS#1 v1.5 decryption</title>
      <link>https://vulnogram.org/CVE-2026-6291</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-6291</guid>
      <description>Bleichenbacher padding oracle in PKCS#7 KTRI decryption. When decrypting PKCS#7 EnvelopedData using RSA PKCS#1 v1.5 key transport, wolfSSL returned distinguishable error codes depending on whether RSA padding validation failed versus whether the decr…</description>
      <category>Medium</category>
      <pubDate>Thu, 25 Jun 2026 16:41:42 GMT</pubDate>
    </item>
  </channel>
</rss>
