Skip to main content

WibuKey EUVDEUVD-2026-66985

| CVE-2026-81581 HIGH
Buffer Overflow (CWE-119)
2026-08-27 wibu GHSA-m4jv-48jv-489g
8.8
CVSS 3.1 · Vendor: wibu
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain low-privilege local Windows account
  2. Delivery
    Open IOCTL handle to WibuKey64.sys
  3. Exploit
    Submit crafted request with out-of-bounds pointer
  4. Execution
    Trigger CWE-119 memory boundary violation in SYSTEM context
  5. Persist
    Corrupt kernel data structure
  6. Impact
    Escalate to SYSTEM privileges

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, buffer size validation
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires a local Windows user-level account (low privilege - standard domain or local user) on a machine where WibuKey version 6.70 or earlier is installed and the WibuKey64.sys driver is loaded and running. The attacker must be able to open a file handle to the driver device and submit IOCTL requests - a capability typically available to all local users without administrator rights, which is what drives the PR:L and AV:L CVSS metrics. No special WibuKey configuration, no active dongle connection, and no user interaction from another account are required. Exploitation is bounded by three concrete limiting factors: (1) the attacker must have an interactive or network logon session on the target host - pure remote unauthenticated attack is not possible; (2) WibuKey software must be installed and its driver loaded, meaning hosts without the product are entirely unaffected; (3) only Windows is affected - the 64-bit driver is Windows-specific.

Impact

The vendor-reported CVSS 8.8 vector (AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H) is well-calibrated for this vulnerability class. The low attack complexity and low privileges required mean that any standard domain or local user account on an affected system is sufficient to trigger exploitation - no administrator access, no special configuration, and no user interaction are needed. The Scope:Changed metric is the key risk amplifier: the attacker's low-privilege process context crosses into SYSTEM-privileged kernel space through the driver, yielding C:H/I:H/A:H impact across the entire operating system. The description hedges between DoS and full RCE/PE, which is common for kernel memory corruption bugs before PoC development; historical precedent for this class (CWE-119 in Windows kernel drivers) shows reliable privilege escalation is typically achievable with research effort. No EPSS score or KEV listing was provided, meaning exploitation probability from external data cannot be quantified and no confirmed in-the-wild exploitation is known. The local attack vector (AV:L) prevents direct remote exploitation, meaningfully limiting opportunistic attack surface compared to a network-vector flaw - but this is a textbook local privilege escalation step in a post-compromise chain or insider threat scenario.

Exploit ScenarioDerived

A local attacker holding a standard Windows user account on a system with WibuKey ≤6.70 installed opens a handle to WibuKey64.sys and issues crafted IOCTL requests containing pointer values that fall outside the driver's valid memory scope. The driver dereferences these out-of-bounds pointers without validation in SYSTEM-privileged kernel context, corrupting kernel memory; with sufficient effort this can be converted from a reliable BSOD (DoS) into a controlled write primitive that overwrites a kernel function pointer or security token, granting the attacker SYSTEM-level process privileges. No public proof-of-concept has been identified at time of analysis, but the attack complexity is rated Low.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 27, 2026

WibuKey64.sys kernel-mode driver in Wibu-Systems WibuKey up to version 6.70 for Windows allows a local, low-privileged attacker to trigger memory boundary violations by supplying out-of-scope pointer values, with outcomes ranging from denial of service (BSOD) to full SYSTEM-level privilege escalation via kernel code execution. The CVSS Scope:Changed metric reflects the critical boundary crossing from user-space into the driver's SYSTEM-privileged kernel context, meaning successful exploitation yields complete machine control from an unprivileged account. No public exploit has been identified at time of analysis and WibuKey has not been listed in the CISA KEV catalog, but the low attack complexity makes this a high-value local privilege escalation primitive for post-compromise chains.

RemediationAI

Consult the Wibu-Systems AG security advisory at https://cdn.wibu.com/fileadmin/wibu_downloads/security_advisories/AdvisoryWIBU-100057.pdf for the official patched release; the exact fixed version number is not independently confirmed in the available data and should be taken directly from that document. As a compensating control pending patch deployment, restrict interactive and remote login access to systems running WibuKey to trusted users only, since exploitation requires a local low-privileged session - this does not eliminate the risk from insiders or compromised accounts but raises the barrier. On systems where WibuKey-protected software is not actively in use, consider unloading or disabling the WibuKey64.sys driver via Device Manager or sc.exe, accepting the trade-off that WibuKey-licensed applications will cease to function until the driver is re-enabled. Deploying Windows Defender Application Control (WDAC) or similar kernel driver allowlist policies can restrict which processes are permitted to open IOCTL channels to the driver, reducing the pool of potential exploiters without fully disabling the driver.

Affected VersionsENISA

wibukey 0 <6.71

Affected Packages

euvd wibukey fix: 6.71

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

WibuKey is a hardware dongle-based software licensing and protection system by Wibu-Systems AG, deployed primarily in industrial automation, embedded systems, and specialized enterprise software. WibuKey64.sys is the 64-bit Windows kernel-mode driver responsible for communicating with WibuKey hardware tokens. Operating at ring 0, the driver runs with full SYSTEM privileges. The flaw is classified as CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer): the driver fails to validate that attacker-controlled pointer values fall within the intended memory scope before dereferencing them. This class of kernel driver bug - often reachable via IOCTL interfaces accessible to low-privileged users - enables corruption of kernel data structures. Because the Windows kernel driver model grants SYSTEM-level trust to all loaded drivers, memory corruption in WibuKey64.sys directly threatens OS integrity. The CPE string cpe:2.3:a:wibu-systems-ag:wibukey:*:*:*:*:*:*:*:* confirms a broad version range is affected up to 6.70.

Know when Wibukey gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (wibu) PRIMARY 8.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
vuln.today AI 8.8 HIGH

Low-privilege local access reaches SYSTEM-privileged kernel driver; scope changes to OS kernel justifying S:C with full C/I/A impact.

3.1 AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Primary rating from Vendor (wibu).

CVSS VectorVendor: wibu

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
Patch available
Aug 27, 2026 - 11:16 EUVD
CVE Published
Aug 27, 2026 - 07:46 cve.org
HIGH 8.8

DescriptionCVE.org

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).

Executive ViewAI

Why It Matters

Wibu-Systems WibuKey driver on Windows (versions 6.70 and earlier) allows any standard user account to escalate to complete SYSTEM-level control, transforming routine local access into full administrative compromise. Organizations running vulnerable versions face risk that compromised user credentials or lateral movement become pathways to undetected system takeover.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: disable WibuKey64.sys driver if not operationally essential; restrict local system access via strong account controls and multi-factor authentication; enforce Windows kernel Driver Signature Enforcement and Code Integrity policies; monitor Windows Event Viewer for driver-related events and privilege escalation; implement application control policies to prevent post-exploitation tool execution.

Threat Intelligence Overview

EPSS Score
0.2%
Top 90% exploitable
Prevalence
Low
niche hardware dongle licensing system, industrial and specialized software deployments only
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy