# CVE-2026-11310: X.509 trust-chain bypass in wolfSSL_X509_verify_cert() via untrusted intermediate anchoring

> Attackers can bypass certificate verification in wolfSSL when using OpenSSL compatibility mode with untrusted intermediates, accepting malicious certificates.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/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:** Yes
- **Published:** 25 Jun 2026
- **Updated:** 26 Jun 2026
- **Also known as:** DEBIAN-CVE-2026-11310, GHSA-h4wh-367g-85gm, JLSEC-2026-697, UBUNTU-CVE-2026-11310

## What is CVE-2026-11310?

CVE-2026-11310 is a high-severity vulnerability in Wolfssl Wolfssl, published on 25 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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() with caller-supplied untrusted intermediate certificates; for those users it is critical, otherwise the library is unaffected. In particular, native wolfSSL TLS/DTLS usage is not impacted. wolfSSL's X509_verify_cert() temporarily loads each caller-supplied untrusted intermediate into the certificate manager but failed to drop them before the trusted-store check, so an untrusted intermediate could anchor the path itself. An attacker can present a chain that never reaches a configured trust anchor and have it accepted, resulting in acceptance of an attacker-controlled certificate. This is certificate verification independent of TLS (e.g. S/MIME/CMS, code/firmware signing, JWT/JWS x5c), is not specific to any key type or algorithm, and a single untrusted intermediate suffices. The default wolfSSL TLS handshake (WOLFSSL_VERIFY_PEER) is not affected; only TLS applications doing manual or deferred peer verification through this API are, which also requires --enable-sessioncerts.

Weakness: CWE-295 (Improper Certificate Validation)

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

It affects 1 product.


Products: Wolfssl Wolfssl.

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

Apply the vendor's patch.

## Is CVE-2026-11310 being exploited?

There is no known exploitation of CVE-2026-11310 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-11310 and fix it if it is affected.

What it is: CVE-2026-11310 is a high-severity vulnerability in Wolfssl Wolfssl, published on 25 Jun 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-11310 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-11310/ (Markdown: https://insights.sbomify.com/CVE-2026-11310/index.md)
```

## Sources

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

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