CVE-2026-112981 · Infrastructure
NO FIX YET
A heap-based buffer overflow in the Windows Print Spooler components lets an authorized user raise their privileges on the same machine. The attacker needs a local account first and cannot use this flaw from the network alone.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Any Windows machine with the Print Spooler components present is in scope, and the flaw only matters where people with ordinary local accounts share the machine. The sources do not state which Windows builds are vulnerable or which configurations change exposure, so the team should check the vendor advisory before deciding how urgent it is.
Not affected if print-spooler-disabled, single-user-machines
Who cares multi-user-hosts, print-spooler, windows
winver and compare it against the Microsoft security update for CVE-2026-112981 (unknown which build is fixed; the sources do not say)Get-Service Spooler in PowerShell (unknown whether this affects exposure; the sources do not say)No fix yet, per the sources.
Heap-based buffer overflow in Windows Print Spooler Components allows an authorized attacker to elevate privileges locally.
This page as .md · .json · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.