CVE-2026-11310

HIGHNVD 7.57.5
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-25. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
12.6%
KEV
Not listed

Published

June 25, 2026

Last Modified

June 26, 2026

Advisory Details (2)

Auto-updated Jun 26, 2026
Patch available. Sources: github_pr.
generic Patch Available

wolfSSL Security Vulnerabilities | Documentation - wolfSSL

https://www.wolfssl.com/docs/security-vulnerabilities/
github_pr

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/10674

Vendor 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 8× in last 7d / 76× 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.

  1. 2026-07-25 14:17 UTCEPSS rescore
  2. 2026-07-24 14:17 UTCEPSS rescore
  3. 2026-07-23 14:18 UTCEPSS rescore
  4. 2026-07-23 03:04 UTCEG score recompute
  5. 2026-07-22 14:08 UTCEPSS rescore
  6. 2026-07-21 15:24 UTCEPSS rescore
  7. 2026-07-20 17:08 UTCEPSS rescore
  8. 2026-07-19 14:30 UTCEPSS rescore
  9. 2026-07-18 10:04 UTCEPSS rescore
  10. 2026-07-16 20:08 UTCGHSA enrichment
  11. 2026-07-16 17:02 UTCEPSS rescore
  12. 2026-07-16 07:44 UTCGHSA enrichment
  13. 2026-07-15 19:20 UTCGHSA enrichment
  14. 2026-07-15 16:57 UTCEPSS rescore
  15. 2026-07-15 06:56 UTCGHSA enrichment
  16. 2026-07-15 02:00 UTCEPSS rescore
  17. 2026-07-14 18:32 UTCGHSA enrichment
  18. 2026-07-14 06:08 UTCGHSA enrichment
  19. 2026-07-13 17:44 UTCGHSA enrichment
  20. 2026-07-13 06:12 UTCEPSS rescore
  21. 2026-07-13 05:20 UTCGHSA enrichment
  22. 2026-07-12 16:51 UTCGHSA enrichment
  23. 2026-07-12 05:46 UTCEPSS rescore
  24. 2026-07-12 04:26 UTCGHSA enrichment
  25. 2026-07-11 16:01 UTCGHSA enrichment
Show 51 more
  1. 2026-07-11 08:27 UTCEPSS rescore
  2. 2026-07-11 03:37 UTCGHSA enrichment
  3. 2026-07-10 15:13 UTCGHSA enrichment
  4. 2026-07-10 02:48 UTCGHSA enrichment
  5. 2026-07-09 19:10 UTCEPSS rescore
  6. 2026-07-09 14:07 UTCGHSA enrichment
  7. 2026-07-09 01:43 UTCGHSA enrichment
  8. 2026-07-08 15:15 UTCEPSS rescore
  9. 2026-07-08 15:15 UTCEPSS rescore
  10. 2026-07-08 13:17 UTCGHSA enrichment
  11. 2026-07-08 00:52 UTCGHSA enrichment
  12. 2026-07-07 13:46 UTCEPSS rescore
  13. 2026-07-07 12:28 UTCGHSA enrichment
  14. 2026-07-07 00:01 UTCGHSA enrichment
  15. 2026-07-06 11:37 UTCGHSA enrichment
  16. 2026-07-06 02:23 UTCEPSS rescore
  17. 2026-07-05 23:10 UTCGHSA enrichment
  18. 2026-07-05 10:39 UTCGHSA enrichment
  19. 2026-07-05 02:30 UTCEPSS rescore
  20. 2026-07-05 02:30 UTCEPSS rescore
  21. 2026-07-04 22:15 UTCGHSA enrichment
  22. 2026-07-04 09:51 UTCGHSA enrichment
  23. 2026-07-04 06:31 UTCEPSS rescore
  24. 2026-07-03 21:26 UTCGHSA enrichment
  25. 2026-07-03 09:03 UTCGHSA enrichment
  26. 2026-07-02 20:39 UTCGHSA enrichment
  27. 2026-07-02 08:15 UTCGHSA enrichment
  28. 2026-07-01 19:51 UTCGHSA enrichment
  29. 2026-07-01 15:06 UTCEPSS rescore
  30. 2026-07-01 15:06 UTCEPSS rescore
  31. 2026-07-01 07:26 UTCGHSA enrichment
  32. 2026-06-30 23:22 UTCEPSS rescore
  33. 2026-06-30 19:02 UTCGHSA enrichment
  34. 2026-06-30 06:37 UTCGHSA enrichment
  35. 2026-06-29 18:12 UTCGHSA enrichment
  36. 2026-06-29 05:43 UTCGHSA enrichment
  37. 2026-06-28 17:19 UTCGHSA enrichment
  38. 2026-06-28 14:07 UTCEPSS rescore
  39. 2026-06-28 04:56 UTCEPSS rescore
  40. 2026-06-28 04:56 UTCEPSS rescore
  41. 2026-06-28 04:55 UTCGHSA enrichment
  42. 2026-06-27 16:32 UTCGHSA enrichment
  43. 2026-06-27 04:08 UTCEG score recompute 1.20
  44. 2026-06-27 04:08 UTCGHSA enrichment
  45. 2026-06-27 03:08 UTCEPSS rescore
  46. 2026-06-26 19:41 UTCNVD updateCVSS v3 → 7.5
  47. 2026-06-26 15:45 UTCEG score recompute 8.70
  48. 2026-06-26 15:44 UTCGHSA enrichment
  49. 2026-06-26 15:40 UTCNVD updateCVSS v3 → 8.7 · CVSS v4 → 8.7
  50. 2026-06-25 21:46 UTCEG score recompute
  51. 2026-06-25 21:46 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-11310?
CVE-2026-11310 is a high vulnerability published on June 25, 2026. X.509 trust-chain bypass in the OpenSSL compatibility certificate verifier (wolfSSLX509verifycert()). This affects only builds with --enable-opensslextra (OPENSSLEXTRA) and whose application validates certificates by calling X509verifycert() with caller-supplied untrusted intermediate certificates;…
When was CVE-2026-11310 disclosed?
CVE-2026-11310 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-11310 actively exploited?
CVE-2026-11310 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 12.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-11310?
CVE-2026-11310 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-11310?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-11310, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-11310

Explore →

Is Your Infrastructure Affected by CVE-2026-11310?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.