Skip to content
EXYS
Back to the CVEs

CVE-2026-93302

8.2, high

MatchTrustedPeer ignores the public key used, leading to forged CA clones passing verification

NVD (opens in a new tab) CVE.org (opens in a new tab)
CVSS
8.2, high high CVSS v3.1
EPSS, next 30 days
0.2% higher than 9.3% of scored CVEs
Exploitation
No public evidence
Published
27 Sept 202621 days ago

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_cert(). The peer must know the certificates being loaded to either of those APIs to take advantage of the issue. When OPENSSL_COMPATIBLE_DEFAULTS is also defined this widens the affected API to include all CA certificate loading. Both macros are defined when using autoconf builds such as (nginx, haproxy, stunnel, wpas, apache httpd, hitch, bind, rsyslog, ffmpeg, all, distro). When the certificate is listed as a trusted peer certificate the issue previously allowed for a malicious (D)TLS server to bypass authentication once knowing which CA’s the client would accept. This also affects mutual authentication cases where the client knows which CA’s the server has loaded. If building with any of these configurations and using (D)TLS where the loaded CA’s could be known and authentication of the peer is desired, users should either: update to the latest wolfSSL version, apply the fix patch, or use the configure flag --disable-openssl-compatible-defaults and not load CA’s with wolfSSL_CTX_trust_peer_cert() or wolfSSL_trust_peer_cert() to mitigate the issue.

Details

Vendor
wolfSSL
Product
wolfSSL
Weakness
CWE-295 (opens in a new tab)
Status
Analyzed
Updated
2 Oct 2026
Assigner
facts@wolfssl.com

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N

References 1

Patches and fixes 1

The kind is read from NVD's tags where present and from the shape of the URL otherwise, so treat it as a hint.

Other wolfSSL CVEs

Every wolfSSL CVE we hold

Same vendor in what we hold, not a known link between the flaws.

  • CVE-2026-83540 wolfSSL wolfSSH Improper Authentication Vulnerability EPSS 0.4% 8.8, high
  • CVE-2026-89134 A certificate with no dNSName SAN but another SAN type present (e.g EPSS 0.2% 9.1, critical
  • CVE-2026-94418 Under WOLFSSL_SMALL_CERT_VERIFY, ProcessPeerCertParse() runs the certificate signature check separately from the parse to keep peak… EPSS <0.1% 7.5, high

Beyond this page

Is CVE-2026-93302 in your network?

This page tells you how dangerous CVE-2026-93302 is out there. Whether it sits on one of your devices, only a scan of your own network can tell. That is what our systems do, every day, for the companies we protect.

  • EXYS7600 OCELOT

    Find it before attackers do

    Ocelot scans your network on a schedule and reports every vulnerability it finds by its CVE identifier, with its CVSS score and how many of your hosts are affected. A finding like CVE-2026-93302 comes with the devices to patch.

    Learn more about EXYS7600 OCELOT

  • EXYS7950 KONDRA

    Detect it if it's exploited

    Until the patch is applied, Kondra monitors your network, events and endpoints in real time. It keeps an inventory of the software installed on every endpoint, and its anomaly detection rules flag what an attacker does once inside.

    Learn more about EXYS7950 KONDRA
Check your exposure

Assembled from the NVD 2.0 API, the CISA Known Exploited Vulnerabilities Catalog and FIRST EPSS. Scores are as of our last collection on 18 Oct 2026, not the live upstream state.