Skip to content
major vulnerability· requires attention

Affects wolfSSL used by many popular servers/clients and distro autoconf builds; auth bypass in TLS can broadly undermine secure connections.

Cryptography

CVE-2026-93302

8.3
High
EPSS n/aPatch availableSep 27, 2026

wolfSSL TLS auth bypass: trusted-peer CA verification ignored, enabling forged CA acceptance

common questions

Is CVE-2026-93302 being exploited?

Not confirmed. CVE-2026-93302 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.

How severe is CVE-2026-93302?

CVE-2026-93302 is rated High with a CVSS score of 8.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-93302?

Yes. A fix has been recorded for CVE-2026-93302. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-93302 affect?

CVE-2026-93302 affects wolfSSL (autoconf builds), nginx, haproxy, stunnel, and 7 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-93302?

Update wolfSSL to the fixed release or apply patch; avoid using trust_peer_cert or disable openssl-compatible-defaults.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
wolfSSL (autoconf builds)nginxhaproxystunnelwpa_supplicantApache httpdhitchbindrsyslogffmpegLinux distros
impact

Authentication bypass in (D)TLS: attacker knowing loaded CA list can impersonate peers, bypass TLS auth, enable MITM or unauthorized connections.

action required

Immediate action required

affected versions
wolfSSL wolfSSL
  • affected>= 5.3.0 and <= 5.9.2

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free