User input in WibuKey is used (without proper sanitization) to compute the address of a pointer, which can be exploited to let the user point to any storage, to which Windows responds with a denial of service. (CVE-2026-81581) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-81581

User input in WibuKey is used (without proper sanitization) to compute the address of a pointer, which can be exploited to let the user point to any storage, to which Windows responds with a denial of service.

Answer in brief

CVE-2026-81581 records a Unknown severity vulnerability in User input in WibuKey is used (without proper sanitization) to compute the address of a pointer, which can be exploited to let the user point to any storage, to which Windows responds with a denial of service.. The current sources do not mark it as known exploited. The current feed maps wibu-systems-ag/wibukey (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 27, 2026Updated Aug 27, 2026Source checked Aug 27, 2026First seen by HOL Aug 27, 2026Material review Aug 27, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps wibu-systems-ag/wibukey (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
wibu-systems-ag/wibukeygeneric	>=0 <6.71	6.71

Recommended response

Check inventory. Check lockfiles and deployed manifests for wibu-systems-ag/wibukey.
Review the reported fix. Update wibu-systems-ag/wibukey to 6.71 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 27, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 27, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 27, 2026

Sources and claim methodology

Source referencecdn.wibu.com

Upstream source description

Improper validation of memory boundaries in WibuKey64.sys of WibuKey up to 6.70 for Windows can be exploited by an attacker by setting the pointers outside the scope of the program. This usually results in a denial of service, yet we cannot rule out the possibility of exploits that can cause Remote Code Execution and Privilege Escalation (since the driver runs with system privileges).

Quoted source text, attributed separately from HOL analysis.