Windows Print Spooler CVE-2026-69569

Attacker must hold at least low-level credentials on the target Windows system or domain (PR:L). Some form of user interaction is required (UI:R), likely a user initiating a print job or connecting a print client that triggers the vulnerable code path. The Windows Print Spooler service must be running and accessible over the network, which is the default configuration on Windows Server and desktop editions. Exploitation is limited to a denial-of-service outcome (A:H only) - there is no path to code execution, privilege escalation, or data exfiltration based on the CVSS vector (C:N/I:N). Non-credentialed (unauthenticated) remote attackers cannot exploit this vulnerability.

With a CVSS base score of 5.7 and a vector of AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:H, real-world risk is moderate and bounded by two key mitigating factors: the attacker must already hold at least low-level credentials (PR:L), and some form of user interaction is required (UI:R), likely involving a user initiating or interacting with a print operation. The impact is limited entirely to availability - a Print Spooler crash that could disrupt printing operations but has no confidentiality or integrity consequence. EPSS data is not provided; no KEV listing and no POC code are confirmed. Given the scope (no privilege escalation, no data leakage), this is a functional disruption rather than a strategic compromise risk. Organizations relying heavily on Windows print infrastructure (e.g., enterprise printing in healthcare or manufacturing) face higher operational impact. The 'Information Disclosure' tag attached in the source metadata is incorrect and conflicts with the CVSS C:N metric - this should be flagged for correction.

An authenticated network user sends a malformed print request to a target Windows server with Print Spooler running, crafting the request to supply an untrusted pointer value. The spooler dereferences the invalid pointer, triggers an access violation, and the spooler process crashes, denying print service to all users on that system. No public exploit code exists at time of analysis, but the low attack complexity and broad Windows deployment surface make this feasible for any credentialed attacker.