CVE-2026-89136

HIGHPre-NVD 8.38.3—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6% (44th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 4 sources updated this week
8.3EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 8.3Exploit: 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.

When using RPK (Raw Public Key), the client side of a TLS 1.2, 1.3 and DTLS 1.2 connection could accept an unsolicited server_cert_type=RawPublicKey which allowed a malicious or misbehaving server to bypass authentication. RPK is off by default and only enabled in --enable-rpk OR --enable-all OR --enable-distro AKA HAVE_RPK builds.

CVSS v3
8.3
EG Score
8.3HIGHmedium confidence
EG Risk
38
EG Risk 38/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
Severity83% × 45%
Exploitation1% × 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.6%
EPSS %ILE
44th
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 29, 2026

Advisory Details (1)

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

Fix multiple reported issues.

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

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

Vendor Advisories for CVE-2026-89136(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 33× in last 7d / 36× 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-04 02:44 UTCEG score recompute
  2. 2026-10-04 02:44 UTCVendor advisory
  3. 2026-10-04 02:44 UTCGHSA enrichment
  4. 2026-10-03 13:37 UTCVendor advisory
  5. 2026-10-03 13:37 UTCGHSA enrichment
  6. 2026-10-03 00:29 UTCEG score recompute
  7. 2026-10-03 00:29 UTCVendor advisory
  8. 2026-10-03 00:29 UTCGHSA enrichment
  9. 2026-10-02 11:21 UTCVendor advisory
  10. 2026-10-02 11:21 UTCGHSA enrichment
  11. 2026-10-01 22:11 UTCEG score recompute
  12. 2026-10-01 22:11 UTCVendor advisory
  13. 2026-10-01 22:11 UTCGHSA enrichment
  14. 2026-10-01 19:51 UTCEPSS rescore
  15. 2026-10-01 08:59 UTCVendor advisory
  16. 2026-10-01 08:59 UTCGHSA enrichment
  17. 2026-09-30 19:51 UTCEG score recompute
  18. 2026-09-30 19:51 UTCGHSA enrichment
  19. 2026-09-30 15:04 UTCEPSS rescore
  20. 2026-09-30 06:44 UTCGHSA enrichment
  21. 2026-09-29 17:36 UTCEG score recompute
  22. 2026-09-29 17:36 UTCGHSA enrichment
  23. 2026-09-29 16:45 UTCEG score recompute
  24. 2026-09-29 16:45 UTCGHSA enrichment
  25. 2026-09-29 09:59 UTCEG score recompute
Show 11 more
  1. 2026-09-29 09:58 UTCGHSA enrichment
  2. 2026-09-28 20:50 UTCEG score recompute
  3. 2026-09-28 20:50 UTCGHSA enrichment
  4. 2026-09-28 13:52 UTCEPSS rescore
  5. 2026-09-28 12:36 UTCGHSA enrichment
  6. 2026-09-27 23:28 UTCEG score recompute
  7. 2026-09-27 23:28 UTCGHSA enrichment
  8. 2026-09-27 13:48 UTCEPSS rescore
  9. 2026-09-27 10:20 UTCEG score recompute
  10. 2026-09-27 09:20 UTCEG score recompute
  11. 2026-09-27 09:20 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-89136?
CVE-2026-89136 is a high vulnerability published on September 27, 2026. When using RPK (Raw Public Key), the client side of a TLS 1.2, 1.3 and DTLS 1.2 connection could accept an unsolicited servercerttype=RawPublicKey which allowed a malicious or misbehaving server to bypass authentication. RPK is off by default and only enabled in --enable-rpk OR --enable-all OR…
When was CVE-2026-89136 disclosed?
CVE-2026-89136 was first published on September 27, 2026, with the most recent update on September 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-89136 actively exploited?
CVE-2026-89136 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-89136?
CVE-2026-89136 has a CVSS base score of 8.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-89136?
An upstream fix for CVE-2026-89136 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-89136 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-89136?

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

Book a Demo →Browse All CVEs