Home › Intelligence › Brief
VULNERABILITY BRIEF 🟠 High Vulnerability

Improper Locking in win32kfull Leads to Local Privilege Escalation (CVE-2026-33104) in Microsoft Windows

A critical local privilege escalation vulnerability (CVE‑2026‑33104) has been disclosed in the Windows win32kfull driver. The flaw allows low‑privileged code to gain SYSTEM rights, posing a high‑impact risk for any organization that runs Microsoft Windows. Prompt patching and strict privilege controls are essential for third‑party risk mitigation.

Verisq™ Intelligence · 📅 April 16, 2026 · 📰 zerodayinitiative.com
🟠
Severity
High
VU
Type
Vulnerability
🎯
Confidence
High
🏢
Affected
4 sector(s)
✅
Actions
5 recommended
📰
Source
zerodayinitiative.com

Improper Locking in win32kfull Leads to Local Privilege Escalation (CVE‑2026‑33104) in Microsoft Windows

What It Is – A newly disclosed vulnerability (CVE‑2026‑33104) in the Windows win32kfull.sys driver allows a local attacker to bypass proper locking mechanisms, enabling escalation from a low‑privileged account to SYSTEM.

Exploitability – The flaw is locally exploitable; an attacker must already have code execution at a low privilege level. No public exploit code has been released, but the CVSS 7.8 rating (AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H) reflects a high impact if leveraged.

Affected Products – Microsoft Windows (all supported versions that include the win32kfull driver).

TPRM Impact – Organizations that rely on Windows‑based workstations, servers, or virtual desktop infrastructure inherit a supply‑chain risk: a compromised endpoint can be used to pivot, exfiltrate data, or disrupt services across the enterprise.

Recommended Actions –

  1. Deploy Microsoft’s security update for CVE‑2026‑33104 immediately (see Microsoft Update Guide).
  2. Verify patch deployment via endpoint management tools and maintain an up‑to‑date inventory of Windows assets.
  3. Enforce least‑privilege policies; restrict local admin rights where possible.
  4. Monitor for anomalous process creation and privilege‑escalation events in Windows Event Logs (e.g., 4624, 4648).
  5. Review third‑party software that bundles its own win32kfull driver or modifies kernel components.

Source: Zero Day Initiative Advisory – ZDI‑26‑278

📰 Original Source
http://www.zerodayinitiative.com/advisories/ZDI-26-278/ ↗

This Verisq Intelligence Brief is an independent analysis. Read the original reporting at the link above.

Vulnerability exposure

Is this CVE in your supply chain?

Verisq matches published vulnerabilities against the software your vendors run, so you know which relationships this touches before the next review.

See vendor exposure →