CVE-2026-81579
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-81579 is a high-severity Write-what-where Condition (CWE-123) vulnerability in Wibu (inferred from references). Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 5th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SI-16 (Memory Protection) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-66984
Vulnerability Data
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…
more
an administrator shell, or gain full control over the system.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 3 hardening rules · 3 OS baselines
—
Mitigating Controls (NIST 800-53 r5) AI
Memory-protection mechanisms block unauthorized writes to arbitrary locations even if a write-what-where primitive exists.
Secure engineering principles require memory-safe coding and bounds checking that eliminate the root cause of write-what-where flaws.
Process isolation confines the blast radius of an arbitrary write so it cannot affect other domains.
Input validation directly stops malformed data from triggering buffer overflows that produce arbitrary write-what-where conditions.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly prevent arbitrary write conditions via safe coding, bounds checking, and memory-safe constructs.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure development lifecycle practices directly reduce the likelihood of write-what-where flaws such as buffer overflows.
Application security requirements can mandate input validation and bounds checking that mitigate arbitrary write conditions.
Secure architecture and engineering principles discourage unsafe memory handling that leads to write-what-where vulnerabilities.
Secure coding standards explicitly forbid unsafe buffer operations that enable arbitrary memory writes.
Security testing in development and acceptance can detect write-what-where conditions before deployment.
Change management processes help ensure security fixes for such weaknesses are properly deployed.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (higher-evidence rows only; rows rated `none` are excluded).
Oracle Linux 8 (1 rule)
- V-248592 OL 8 must clear memory when it is freed to prevent use-after-free attacks. prevents CWE-123
RHEL 8 (1 rule)
- V-230279 RHEL 8 must clear memory when it is freed to prevent use-after-free attacks. prevents CWE-123
Windows 10 (1 rule)
- V-220727 Structured Exception Handling Overwrite Protection (SEHOP) must be enabled. prevents CWE-123