Is CVE-2026-93302 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-93302 being exploited in the wild.

How severe is CVE-2026-93302?

Informational severity, published 27 September 2026.

Which products and versions are affected?

Wolfssl Versions built with WOLFSSL_TRUST_PEER_CERT enabled.

Is there a fix for CVE-2026-93302?

A patch was published on 2026-09-17: Fix committed to repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-93302 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-93302?

Check whether you run Wolfssl at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-93302: wolfSSL MatchTrustedPeer public key validation bypass

CVE-2026-93302 · Severity: info · Published 2026-09-27

wolfSSL is a cryptographic library used in TLS/DTLS implementations across web servers, proxies, and network services. The trusted peer certificate verification logic fails to validate the public key, allowing an attacker who knows which Certificate Authorities a client trusts to forge a certificate that passes authentication checks. This enables attackers to impersonate legitimate servers or clients in mutual authentication scenarios.

Technologies: Wolfssl. Vendors: Wolfssl.

Quick answers

Is CVE-2026-93302 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-93302 being exploited in the wild.
How severe is CVE-2026-93302?: Informational severity, published 27 September 2026.
Which products and versions are affected?: Wolfssl Versions built with WOLFSSL_TRUST_PEER_CERT enabled.
Is there a fix for CVE-2026-93302?: A patch was published on 2026-09-17: Fix committed to repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-93302 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-93302?: Check whether you run Wolfssl at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The MatchTrustedPeer() function in wolfSSL's trusted peer certificate verification (WOLFSSL_TRUST_PEER_CERT) only compares certificate metadata (subject name hash, issuer hash, SKID, signature) rather than validating the actual public key or full certificate bytes. An attacker can craft a certificate with matching metadata but a different public key to bypass peer authentication. The vulnerability is widened when OPENSSL_COMPATIBLE_DEFAULTS is enabled, affecting all CA certificate loading APIs. The fix replaces field-by-field comparison with full DER certificate hash validation.

Affected products

wolfSSL wolfSSL Versions built with WOLFSSL_TRUST_PEER_CERT enabled

Timeline

2026-09-27: disclosed: CVE-2026-93302 published
2026-09-17: patched: Fix committed to repository

References

https://github.com/wolfSSL/wolfssl/commit/22bcd51d553eaac1de37bee91fdac80cc47961e1

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.