CVE-2026-34342 is a local privilege escalation vulnerability in the Windows Print Spooler, specifically within the splwow64.exe process. The flaw is caused by improper synchronization during concurrent access to a shared resource, described as unsafe use of shared memory that creates a race condition. An attacker who can already execute low-privileged code locally can exploit the timing flaw to win the race and elevate privileges. Reported exploitation results in a transition from low integrity to medium integrity on affected Windows systems.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Windows Print Spooler elevation of privilege vulnerability caused by a race condition that allows an authorized local attacker with low privileges to elevate privileges locally.
A local privilege escalation vulnerability in the Windows Print Spooler splwow64.exe process caused by a race condition in shared memory handling, allowing an attacker with low-privileged code execution to escalate from low integrity to medium integrity.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.