CVE-2026-89102

MEDIUMNVD 6.56.5—
EchelonGraph scoreHIGH confidence

Score 6.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-27. NVD baseline CVSS 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 5 sources updated this week
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 6.5Exploit: None knownExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

In wolfSSL versions 5.7.2 through 5.9.2 there is a client-side implementation flaw in RFC 6961, multiple OCSP response stapling, which can lead to certificate forgery. When a wolfSSL client enables OCSP stapling with the HAVE_CERTIFICATE_STATUS_REQUEST_V2 feature and calls wolfSSL_UseOCSPStaplingV2(ssl, WOLFSSL_CSR2_OCSP_MULTI, options), the client accepts any certificate in the peer's chain as a certificate authority without verifying that the certificate is actually authorized to act as one. This means that an attacker who possesses any certificate that chains to a CA trusted by the client (along with its private key) can forge certificates for arbitrary identities that will be accepted as valid by the client. The end entity certificate of the server is stored in the persistent trust store, affecting subsequent connections that reuse the context even when OCSP multi usage is not employed. Found by internal wolfSSL testing.

CVSS v3
6.5
EG Score
6.5MEDIUMhigh confidence
EG Risk
29
EG Risk 29/100CISA SSVC

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
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.
EPSS PROB
0.2%
EPSS %ILE
6th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 27, 2026

Last Modified

September 30, 2026

Advisory Details (1)

Auto-updated Sep 27, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr.
github_pr

Fixes for OCSP stapling, cert manager, and certificate_status_request_v2 handling

Fix merged in wolfSSL/wolfssl PR #11027 on 2026-08-04 — awaiting tagged release

https://github.com/wolfSSL/wolfssl/pull/11027

Vendor Advisories for CVE-2026-89102(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 31× in last 7d / 34× 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-10-03 14:35 UTCEG score recompute
  2. 2026-10-03 14:35 UTCVendor advisory
  3. 2026-10-03 14:34 UTCGHSA enrichment
  4. 2026-10-02 15:45 UTCEG score recompute
  5. 2026-10-02 15:45 UTCVendor advisory
  6. 2026-10-02 15:45 UTCGHSA enrichment
  7. 2026-10-01 19:51 UTCEPSS rescore
  8. 2026-10-01 17:00 UTCEG score recompute
  9. 2026-10-01 17:00 UTCVendor advisory
  10. 2026-10-01 17:00 UTCGHSA enrichment
  11. 2026-09-30 17:47 UTCEG score recompute▼ 1.80
  12. 2026-09-30 17:47 UTCGHSA enrichment
  13. 2026-09-30 17:44 UTCNVD updateCVSS v3 → 6.5 · severity → MEDIUM
  14. 2026-09-30 16:17 UTCEG score recompute
  15. 2026-09-30 16:17 UTCGHSA enrichment
  16. 2026-09-30 15:04 UTCEPSS rescore
  17. 2026-09-30 04:37 UTCGHSA enrichment
  18. 2026-09-29 17:36 UTCEG score recompute
  19. 2026-09-29 17:36 UTCGHSA enrichment
  20. 2026-09-29 16:45 UTCEG score recompute
  21. 2026-09-29 16:45 UTCGHSA enrichment
  22. 2026-09-29 07:48 UTCEG score recompute
  23. 2026-09-29 07:48 UTCGHSA enrichment
  24. 2026-09-28 20:50 UTCGHSA enrichment
  25. 2026-09-28 19:17 UTCEG score recompute
Show 9 more
  1. 2026-09-28 19:17 UTCGHSA enrichment
  2. 2026-09-28 13:52 UTCEPSS rescore
  3. 2026-09-28 08:16 UTCGHSA enrichment
  4. 2026-09-27 21:18 UTCEG score recompute
  5. 2026-09-27 21:18 UTCGHSA enrichment
  6. 2026-09-27 13:48 UTCEPSS rescore
  7. 2026-09-27 10:20 UTCEG score recompute
  8. 2026-09-27 09:35 UTCEG score recompute
  9. 2026-09-27 09:35 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-89102?
CVE-2026-89102 is a medium vulnerability published on September 27, 2026. In wolfSSL versions 5.7.2 through 5.9.2 there is a client-side implementation flaw in RFC 6961, multiple OCSP response stapling, which can lead to certificate forgery. When a wolfSSL client enables OCSP stapling with the HAVECERTIFICATESTATUSREQUESTV2 feature and calls wolfSSLUseOCSPStaplingV2(ssl,…
When was CVE-2026-89102 disclosed?
CVE-2026-89102 was first published on September 27, 2026, with the most recent update on September 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-89102 actively exploited?
CVE-2026-89102 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-89102?
CVE-2026-89102 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-89102?
An upstream fix for CVE-2026-89102 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-89102 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-89102?

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

Book a Demo →Browse All CVEs