CVE-2026-11310
Last modified
CVE-2026-11310 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. 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. EPSS estimates a 0.19% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Wolfssl | Wolfssl | >= 5.8.4, < 5.9.2 |
References
- https://github.com/wolfSSL/wolfssl/pull/10674Issue Tracking, Patch
- https://www.wolfssl.com/docs/security-vulnerabilities/Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-11310?
How severe is CVE-2026-11310?
How do I fix CVE-2026-11310?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-113095Use after free in Focus in Google Chrome prior to 156.0.8078…8.8
- CVE-2026-113096UI misrepresentation in Text in Google Chrome on on Android …8.8
- CVE-2026-113097Missing authorization in FileSystem in Google Chrome prior t…8.8
- CVE-2026-113098Type confusion in CacheStorage in Google Chrome prior to 156…6.5
- CVE-2026-113099Confused deputy in Omnibox in Google Chrome on on Android pr…8.8
- CVE-2026-1131A vulnerability has been found in Yonyou KSOA 9.0. Impacted …9.8
- CVE-2026-113100Use of uninitialized variable in Audio in Google Chrome prio…8.8
- CVE-2026-113101Incorrect authorization in SiteIsolation in Google Chrome pr…8.8
- CVE-2026-113102Incorrect reference resolution in FileSystem in Google Chrom…6.5
- CVE-2026-113103Race condition in WebProtect in Google Chrome prior to 156.0…8.8
- CVE-2026-113104Use after free in Frames in Google Chrome prior to 156.0.807…8.8
- CVE-2026-113105Incorrect authorization in Extensions in Google Chrome prior…8.8
Are you affected by CVE-2026-11310?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
