# CVE-2026-93302: Trusted peer certificate match ignores public key, allowing forged CA clones

> Attackers can bypass TLS authentication by forging CA clones if specific trusted peer certificate macros are enabled in wolfSSL builds.

- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Sep 2026
- **Updated:** 29 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-93302, GHSA-22fm-4q7r-f7w4, UBUNTU-CVE-2026-93302

## What is CVE-2026-93302?

CVE-2026-93302 is a high-severity authentication bypass vulnerability in Wolfssl Wolfssl, published on 27 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2026-93302?

It affects 1 product.


Products: Wolfssl Wolfssl.

## How do I fix CVE-2026-93302?

No fix has been published for CVE-2026-93302 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-93302 being exploited?

There is no known exploitation of CVE-2026-93302 in the wild and no public exploit code.

## Other vulnerabilities in Wolfssl Wolfssl

- [CVE-2024-5991](https://insights.sbomify.com/CVE-2024-5991/): Buffer overread in domain name matching (critical 10.0)
- [CVE-2021-37155](https://insights.sbomify.com/CVE-2021-37155/): Security feature bypass in n/a (critical 9.8)
- [CVE-2020-36177](https://insights.sbomify.com/CVE-2020-36177/): Memory corruption in n/a (critical 9.8)
- [CVE-2014-2896](https://insights.sbomify.com/CVE-2014-2896/): Memory corruption in n/a (critical 9.8)
- [CVE-2014-2897](https://insights.sbomify.com/CVE-2014-2897/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93302 and fix it if it is affected.

What it is: CVE-2026-93302 is a high-severity authentication bypass vulnerability in Wolfssl Wolfssl, published on 27 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93302 in the wild and no public exploit code.

Affected product: Wolfssl Wolfssl. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93302/ (Markdown: https://insights.sbomify.com/CVE-2026-93302/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93302
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93302
- OSV: https://osv.dev/vulnerability/CVE-2026-93302

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93302/
Summaries are generated and may contain mistakes; the official description above is the record.