CVE-2026-32223 json
Windows USB Printing Stack (usbprint.sys) Elevation of Privilege Vulnerability
published 2026-04-14 6 mo ago modified 2026-10-15 24 d ago also EUVD-2026-22611
- cvss
- 6.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 44%
- public exploits
- 0
- none known
Summary
Heap-based buffer overflow in Windows USB Print Driver allows an unauthorized attacker to elevate privileges with a physical attack.
Patch / fix
- Microsoft Windows 11 Version 24H2 10.0.26100.8246
- Microsoft Windows 11 Version 25H2 10.0.26200.8246
- Microsoft Windows 11 version 26H1 10.0.28000.1836
- Microsoft Windows Server 2025 10.0.26100.32690
- Microsoft Windows Server 2025 (Server Core installation) 10.0.26100.32690
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 6 mo ago
Exploit prediction
0.52% chance of exploitation in the next 30 days, higher than 44% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.8 | CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C |
| CNA | 3.1 | 6.8 | CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Microsoft Windows 11 Version 24H2
- Microsoft Windows 11 Version 25H2
- Microsoft Windows 11 version 26H1
- Microsoft Windows Server 2025
- Microsoft Windows Server 2025 (Server Core installation)
Classification
- Weakness
-
- CWE-122 Heap-based Buffer Overflow
References
-
msrc.microsoft.com
/update-guide/vulnerability/CVE-2026-32223
vendor-advisory, patch
- vicarius.io /vsociety/posts/cve-2026-32223-detection-script-heap-based-buffer-overflow-in-windows-usb-print-driver
- vicarius.io /vsociety/posts/cve-2026-32223-mitigation-script-heap-based-buffer-overflow-in-windows-usb-print-driver
Sources
- CVE List CVE-2026-32223
- NVD CVE-2026-32223
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.