Quick answers
- Is CVE-2026-81581 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-81581 being exploited in the wild.
- How severe is CVE-2026-81581?
- High severity, with a CVSS score of 8.8, published 27 August 2026.
- Which products and versions are affected?
- Wibu-Systems WibuKey up to 6.70.
- Is there a fix for CVE-2026-81581?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-81581 attacked?
- It is attacked with local access, in device firmware.
- Am I affected by CVE-2026-81581?
- Check whether you run Wibu-Systems WibuKey at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an improper validation of memory boundaries in the WibuKey64.sys kernel driver affecting WibuKey up to version 6.70 on Windows. An attacker can exploit this by setting pointers outside the allocated program scope, leading to out-of-bounds memory access. The attack vector is local and does not require elevated privileges to trigger. While the immediate impact is denial of service, the driver's system-level execution context creates potential for privilege escalation and remote code execution. Patches are expected from Wibu-Systems for affected versions.
Affected products
- Wibu-Systems WibuKey up to 6.70
Timeline
- 2026-08-27: disclosed