wibukey: Write-what-where Condition
CVE-2026-81579 is a high-severity write-what-where condition vulnerability in wibukey from Wibu-systems-ag, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists version 6.71 as the first without the flaw, so updating wibukey to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.17% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update wibukey to 6.71 or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Wibu-systems-ag | wibukey | before 6.71 | 6.71 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H. Scored by CNA.
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Write-what-where Condition
Any condition where the attacker has the ability to write an arbitrary value to an arbitrary location, often as the result of a buffer overflow.
How developers prevent this class of flaw
- Use a language that provides appropriate memory abstractions.
- Use OS-level preventative functionality integrated after the fact. Not a complete solution.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in wibukey
- 7.0 High severity
- 8.8 High severity
Recent Write-what-where Condition vulnerabilities
- 7.4 High severity
- 7.8 High severity
- 8.8 High severity
- 7.8 High severity
- 9.8 Critical severity
- 8.8 High severity
Spotted an error? Tell us.