dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-34342

HIGH · 7.0 CVSS v3.1 Published 2026-05-12
Fix available
A fix is available. Upgrade to 10.0.14393.9140 / 10.0.17763.8755 or later.
See remediation →
72/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Print Spooler Components allows an authorized attacker to elevate privileges locally.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a race condition (TOCTOU - Time of Check to Time of Use) vulnerability in Windows Print Spooler Components. An authorized local attacker can exploit improper synchronization when accessing shared resources to elevate their privileges from a standard user to higher system privileges.

MitigationApply the Microsoft security update for this CVE. If Print Spooler is not required in the environment, consider disabling the service as a defense-in-depth measure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Windows 10 1607Operating system
Affected:< 10.0.14393.9140
Windows 10 1809Operating system
Affected:< 10.0.17763.8755
Windows 10 21h2Operating system
Affected:< 10.0.19044.7291
Windows 10 22h2Operating system
Affected:< 10.0.19045.7291
Windows 11 23h2Operating system
Affected:< 10.0.22631.7079
Windows 11 24h2Operating system
Affected:< 10.0.26100.8390
Windows 11 25h2Operating system
Affected:< 10.0.26200.8390
Windows 11 26h1Operating system
Affected:< 10.0.28000.2113

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Windows version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to identify your Windows build number
    Affected if The installed build number falls below the first fixed version listed for your Windows release (e.g., 14393.9140 for 1607, 17763.8755 for 1809, etc.)
  2. Verify Print Spooler service status
    Run 'Get-Service -Name Spooler' in PowerShell or check Services.msc for the Print Spooler service
    Affected if The service is running or set to start automatically (even if currently stopped, the vulnerability applies if the service is enabled)
  3. Check Print Spooler DLL version
    Locate spoolsv.exe (typically in C:\Windows\System32\) and check its file version properties, or run 'wmic product where "name like 'Print Spooler'" get version'
    Affected if The DLL version cannot be directly correlated to the CVE fixed versions; rely on OS build number check instead

Your system is affected if it runs a Windows version below the fixed build number AND has the Print Spooler service enabled, regardless of its current running state.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.0.14393.9140 / 10.0.17763.8755 / 10.0.19044.7291 or later
Fixed in 10.0.14393.914010.0.17763.875510.0.19044.7291
Interim mitigation

Apply the Microsoft security update for this CVE. If Print Spooler is not required in the environment, consider disabling the service as a defense-in-depth measure.

Recommended fix High confidence

Windows 10 1607: build 10.0.14393.9140 | Windows 10 1809: build 10.0.17763.8755 | Windows 10 21h2: build 10.0.19044.7291 | Windows 10 22h2: build 10.0.19045.7291 | Windows 11 23h2: build 10.0.22631.7079 | Windows 11 24h2: build 10.0.26100.8390 | Windows 11 25h2: build 10.0.26200.8390 | Windows 11 26

  1. Identify the current Windows build version by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine which Windows version and build is installed (e.g., Windows 10 22h2, Windows 11 23h2, etc.)
  3. Open Settings > Windows Update and check for updates
  4. Alternatively, manually download and install the appropriate Windows security update from Microsoft Update Catalog matching the fixed build version for your Windows edition
  5. For enterprise environments, use Windows Server Update Services (WSUS) or Group Policy to deploy the applicable security update
  6. After installation, verify the build number matches or exceeds the fixed version: Windows 10 1607 should be 10.0.14393.9140 or later; Windows 10 1809 should be 10.0.17763.8755 or later; Windows 10 21h2 should be 10.0.19044.7291 or later; Windows 10 22h2 should be 10.0.19045.7291 or later; Windows 11 23h2 should be 10.0.22631.7079 or later; Windows 11 24h2 should be 10.0.26100.8390 or later; Window
  7. Restart the system after applying the update
Caveat Standard Windows cumulative update; no expected breaking changes for this privilege escalation patch

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,480
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,568.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34342 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-34342 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data