CVE-2026-113752 · Infrastructure
NO FIX YET
A use-after-free bug in the Windows Print Spooler components lets an unauthorized attacker run code on an affected Windows machine. The attack works over an adjacent network, so the attacker must be on the same local network segment.
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.
Windows systems with the Print Spooler service exposed to an adjacent network are the relevant targets. The sources do not state which Windows builds are affected or whether the service must be enabled by default. Systems without the Print Spooler service running, or isolated from the adjacent network, are less exposed.
Not affected if no-adjacent-network-access, spooler-disabled
Who cares print-spooler, self-hosted, windows
Get-Service Spooler in PowerShell.No fix yet, per the sources.
Use after free in Windows Print Spooler Components allows an unauthorized attacker to execute code over an adjacent network.
This page as .md · .json · CVSS:3.1/AV:A/AC:H/PR:N/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.