# CVE-2026-81579: An untrusted Pointer Dereference can be exploited to escalate privileges by an unprivileged user on Windows

> An untrusted pointer dereference in the WibuKey Windows kernel driver allows local attackers to escalate privileges and execute arbitrary code.

- **Severity:** High 8.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** GHSA-gqq4-6ppr-52p5

## What is CVE-2026-81579?

CVE-2026-81579 is a high-severity vulnerability in wibu-systems-ag wibukey, published on 27 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

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

Weakness: CWE-123 (Write-what-where Condition)

## Which versions are affected by CVE-2026-81579?


## How do I fix CVE-2026-81579?

No fix has been published for CVE-2026-81579 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-81579 being exploited?

There is no known exploitation of CVE-2026-81579 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-81579 and fix it if it is affected.

What it is: CVE-2026-81579 is a high-severity vulnerability in wibu-systems-ag wibukey, published on 27 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-81579 in the wild and no public exploit code.

Affected product: wibu-systems-ag wibukey. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-81579/ (Markdown: https://insights.sbomify.com/CVE-2026-81579/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-81579
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-81579
- OSV: https://osv.dev/vulnerability/CVE-2026-81579

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-81579/
Summaries are generated and may contain mistakes; the official description above is the record.