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.
CVE-2026-11310
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-25. NVD baseline CVSS 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(high)
- EPSS
- 4.1%
- KEV
- Not listed
Published
June 25, 2026
Last Modified
June 26, 2026
Advisory Details (2)
Auto-updated Jun 26, 2026wolfSSL Security Vulnerabilities | Documentation - wolfSSL
https://www.wolfssl.com/docs/security-vulnerabilities/Fixes for OpenSSL compatibility layer
Fix merged in wolfSSL/wolfssl PR #10674 on 2026-06-12 — awaiting tagged release
https://github.com/wolfSSL/wolfssl/pull/10674Vendor Advisories for CVE-2026-11310(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 35× in last 7d / 57× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-07 00:01 UTCEG score recompute
- 2026-07-07 00:01 UTCGHSA enrichment
- 2026-07-06 11:37 UTCEG score recompute
- 2026-07-06 11:37 UTCGHSA enrichment
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 23:10 UTCEG score recompute
- 2026-07-05 23:10 UTCGHSA enrichment
- 2026-07-05 10:40 UTCEG score recompute
- 2026-07-05 10:39 UTCGHSA enrichment
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 22:15 UTCEG score recompute
- 2026-07-04 22:15 UTCGHSA enrichment
- 2026-07-04 09:52 UTCEG score recompute
- 2026-07-04 09:51 UTCGHSA enrichment
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-03 21:26 UTCEG score recompute
- 2026-07-03 21:26 UTCGHSA enrichment
- 2026-07-03 09:03 UTCEG score recompute
- 2026-07-03 09:03 UTCGHSA enrichment
- 2026-07-02 20:39 UTCEG score recompute
- 2026-07-02 20:39 UTCGHSA enrichment
- 2026-07-02 08:15 UTCEG score recompute
- 2026-07-02 08:15 UTCGHSA enrichment
- 2026-07-01 19:51 UTCEG score recompute
Show 32 moreShow fewer
- 2026-07-01 19:51 UTCGHSA enrichment
- 2026-07-01 15:06 UTCEPSS rescore
- 2026-07-01 15:06 UTCEPSS rescore
- 2026-07-01 07:26 UTCEG score recompute
- 2026-07-01 07:26 UTCGHSA enrichment
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 19:02 UTCEG score recompute
- 2026-06-30 19:02 UTCGHSA enrichment
- 2026-06-30 06:37 UTCEG score recompute
- 2026-06-30 06:37 UTCGHSA enrichment
- 2026-06-29 18:12 UTCEG score recompute
- 2026-06-29 18:12 UTCGHSA enrichment
- 2026-06-29 05:43 UTCEG score recompute
- 2026-06-29 05:43 UTCGHSA enrichment
- 2026-06-28 17:19 UTCEG score recompute
- 2026-06-28 17:19 UTCGHSA enrichment
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:55 UTCEG score recompute
- 2026-06-28 04:55 UTCGHSA enrichment
- 2026-06-27 16:32 UTCEG score recompute
- 2026-06-27 16:32 UTCGHSA enrichment
- 2026-06-27 04:08 UTCEG score recompute▼ 1.20
- 2026-06-27 04:08 UTCGHSA enrichment
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-26 19:41 UTCNVD updateCVSS v3 → 7.5
- 2026-06-26 15:45 UTCEG score recompute▲ 8.70
- 2026-06-26 15:44 UTCGHSA enrichment
- 2026-06-26 15:40 UTCNVD updateCVSS v3 → 8.7 · CVSS v4 → 8.7
- 2026-06-25 21:46 UTCEG score recompute
- 2026-06-25 21:46 UTCGHSA enrichment
Frequently asked(5)
What is CVE-2026-11310?
When was CVE-2026-11310 disclosed?
Is CVE-2026-11310 actively exploited?
What is the CVSS score of CVE-2026-11310?
How do I remediate CVE-2026-11310?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-11310
Is Your Infrastructure Affected by CVE-2026-11310?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.