Windows Print Spooler CVE-2026-83733

Exploitation requires local access to the affected Windows system with valid low-privilege credentials (CVSS PR:L) - an 'authorized attacker' per the description - and the ability to reach Print Spooler component code paths, which run by default on Windows client and server editions. No user interaction is required (UI:N). Limiting factors: the attacker must already possess a foothold and authentication on the host (no remote or unauthenticated vector), impact is confined to information disclosure (C:H, I:N, A:N) with no privilege gain or code execution, and only builds below the patched versions listed in the EUVD data (e.g., Windows 11 24H2 before 10.0.26100.9711, Server 2025 before 10.0.26100.33650) are affected.

This is a moderate-severity, low-priority issue under real-world scrutiny. The CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, base 5.5) describes a local, low-complexity attack requiring existing low-level privileges that yields high confidentiality impact but no integrity or availability impact - i.e., a memory-disclosure primitive, not a code-execution or privilege-escalation flaw. All corroborating signals align toward low urgency: CISA's SSVC framework rates Exploitation as 'none', Automatable as 'no', and Technical Impact as only 'partial', and the issue is not on CISA KEV. No EPSS score was provided in the input (missing data - EPSS cannot be factored in), and no public proof-of-concept is referenced. There are no conflicting signals here: the local attack vector, authenticated prerequisite, information-disclosure-only impact, and 'none' exploitation status are mutually consistent. The practical risk is bounded - an attacker must already have a foothold with valid credentials on the host to leak spooler memory - so this ranks below remotely exploitable or wormable Print Spooler bugs and should be patched on a normal cycle rather than emergency.

An attacker who already has low-privileged authenticated access to a Windows host (for example a standard domain user on a shared print server) invokes an affected Print Spooler code path to trigger an out-of-bounds read, leaking adjacent process memory that may contain sensitive data such as credentials, handles, or address information useful for a follow-on exploit. Exploitation is local and requires no user interaction, but no public exploit code is referenced in the available data.