dbcve.org
Windows 10 21h2Operating system · Microsoft

CVE-2025-29841

HIGH · 7.0 CVSS v3.1 Published 2025-05-13
Fix available
A fix is available. Upgrade to 10.0.19044.5854 / 10.0.19045.5854 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 Universal Print Management Service 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 · moderate confidence

This is a race condition vulnerability in the Universal Print Management Service where improper synchronization of shared resources allows an authorized attacker to manipulate timing to elevate privileges locally from their existing authorized access level to higher system privileges.

MitigationApply the relevant Windows security updates for Universal Print Management Service once released, or disable Universal Print if not required in the environment.

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 21h2Operating system
Affected:< 10.0.19044.5854
Windows 10 22h2Operating system
Affected:< 10.0.19045.5854
Windows 11 22h2Operating system
Affected:< 10.0.22621.5335
Windows 11 23h2Operating system
Affected:< 10.0.22631.5335
Windows 11 24h2Operating system
Affected:< 10.0.26100.4061
Windows Server 2022Operating system
Affected:< 10.0.20348.3692
Windows Server 2022 23h2Operating system
Affected:< 10.0.25398.1611
Windows Server 2025Operating system
Affected:< 10.0.26100.4061

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. Verify Universal Print Management Service is present
    Open Services.msc and look for 'Universal Print Management Service' or run: Get-Service -Name 'UniversalPrint*' in PowerShell
    Affected if The service exists and is installed on the system
  2. Confirm Windows version is within affected build range
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' and compare the build number against the listed thresholds (19044, 19045, 22621, 22631, 26100, 20348, 25398)
    Affected if The installed build number is lower than the fixed versions for your Windows release (21h2, 22h2, 23h2, 24h2, Server 2022, Server 2022 23h2, or Server 2025)
  3. Check if Universal Print is enabled in Windows Settings
    Navigate to Settings > Bluetooth & devices > Printers & scanners > Universal Print, or run: Get-PrintService -ErrorAction SilentlyContinue to check print service status
    Affected if Universal Print client or connector is registered and enabled on the endpoint
  4. Verify user has authorized print access
    Review which users have print permissions via 'Get-Printer | Format-List' or check Print Management console for assigned print roles
    Affected if Any non-admin user account with print queue management or printer installation rights is present on the system

The system is affected if Universal Print Management Service is installed, the Windows build falls below the fixed versions listed, and the environment has users with print-related permissions that could be exploited through the race condition.

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.19044.5854 / 10.0.19045.5854 / 10.0.20348.3692 or later
Fixed in 10.0.19044.585410.0.19045.585410.0.20348.3692
Interim mitigation

Apply the relevant Windows security updates for Universal Print Management Service once released, or disable Universal Print if not required in the environment.

Recommended fix High confidence

Microsoft Security Update (CVE-2025-29841) - Specific build numbers: Windows 10 21h2: 10.0.19044.5854 | Windows 10 22h2: 10.0.19045.5854 | Windows 11 22h2: 10.0.22621.5335 | Windows 11 23h2: 10.0.22631.5335 | Windows 11 24h2: 10.0.26100.4061 | Windows Server 2022: 10.0.20348.3692 | Windows Server 20

  1. Identify the affected Windows version and build number by running 'winver' or 'systeminfo'
  2. Open Windows Settings > Update & Security > Windows Update
  3. Click 'Check for updates' and install all available security updates
  4. Alternatively, for enterprise environments, use Windows Server Update Services (WSUS) or Microsoft Endpoint Configuration Manager to deploy the security update
  5. Verify the installation completed successfully by checking the installed updates or re-running 'winver' to confirm the build number matches or exceeds the fixed version for your product
  6. Restart the system if prompted to complete the installation
Caveat Standard Windows security update - no breaking changes expected for this privilege escalation patch

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

Fix this in Windows 10 21h2 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,950
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-29841 — 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-2025-29841 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