CVE-2026-81579

HIGHPre-NVD 8.88.8
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-27. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

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

In WibuKey for Windows before version 6.71, an untrusted pointer dereference in the WibuKey2_64.sys kernel driver for 64-bit Windows allows an attacker to exploit a write-what-where primitive, enabling local privilege escalation. This can be leveraged to execute arbitrary code, run an administrator shell, or gain full control over the system.

CVSS v3
8.8
EG Score
8.8(high)
EG Risk
40(Track)
EG Risk 40/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
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

August 27, 2026

Last Modified

August 28, 2026

Advisory Details (1)

Auto-updated Aug 27, 2026
No patch confirmed yet.

Vendor Advisories for CVE-2026-81579(1)

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 18× in last 7d / 18× 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-08-30 01:22 UTCEPSS rescore
  2. 2026-08-29 17:57 UTCGHSA enrichment
  3. 2026-08-29 05:48 UTCEG score recompute
  4. 2026-08-29 05:48 UTCGHSA enrichment
  5. 2026-08-28 21:42 UTCEPSS rescore
  6. 2026-08-28 17:38 UTCGHSA enrichment
  7. 2026-08-28 05:26 UTCEG score recompute
  8. 2026-08-28 05:26 UTCGHSA enrichment
  9. 2026-08-28 04:59 UTCEG score recompute
  10. 2026-08-28 04:59 UTCGHSA enrichment
  11. 2026-08-27 17:27 UTCEG score recompute
  12. 2026-08-27 17:27 UTCGHSA enrichment
  13. 2026-08-27 17:03 UTCEG score recompute
  14. 2026-08-27 17:02 UTCGHSA enrichment
  15. 2026-08-27 14:25 UTCEPSS rescore
  16. 2026-08-27 10:27 UTCEG score recompute
  17. 2026-08-27 09:24 UTCEG score recompute
  18. 2026-08-27 09:23 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-81579?
CVE-2026-81579 is a high vulnerability published on August 27, 2026. In WibuKey for Windows before version 6.71, an untrusted pointer dereference in the WibuKey2_64.sys kernel driver for 64-bit Windows allows an attacker to exploit a write-what-where primitive, enabling local privilege escalation. This can be leveraged to execute arbitrary code, run an administrator…
When was CVE-2026-81579 disclosed?
CVE-2026-81579 was first published in the National Vulnerability Database on August 27, 2026, with the most recent update on August 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-81579 actively exploited?
CVE-2026-81579 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 95.0% of all scored CVEs.
What is the CVSS score of CVE-2026-81579?
CVE-2026-81579 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-81579?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-81579, 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-81579

Explore →

Is Your Infrastructure Affected by CVE-2026-81579?

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