dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-49665

HIGH · 7.8 CVSS v3.1 Published 2025-07-08
Fix available
A fix is available. Upgrade to 10.0.10240.21073 / 10.0.14393.8246 or later.
See remediation →
80/100
Remediation priority · High
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 Workspace Broker 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

A race condition in Workspace Broker's shared resource handling allows an authorized local attacker to exploit improper synchronization between concurrent operations, potentially elevating privileges by manipulating the timing of privilege checks and their enforcement.

MitigationApply vendor-provided patches for Workspace Broker. If no patch exists, conduct code review to identify and fix the improper synchronization around shared resource access, and implement proper locking mechanisms.

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 1507Operating system
Affected:< 10.0.10240.21073
Windows 10 1607Operating system
Affected:< 10.0.14393.8246
Windows 10 1809Operating system
Affected:< 10.0.17763.7558
Windows 10 21h2Operating system
Affected:< 10.0.19044.6093
Windows 10 22h2Operating system
Affected:< 10.0.19045.6093
Windows 11 22h2Operating system
Affected:< 10.0.22621.5624
Windows 11 23h2Operating system
Affected:< 10.0.22631.5624
Windows 11 24h2Operating system
Affected:< 10.0.26100.4652

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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/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 and build number
    Open Command Prompt and run: `winver` or `systeminfo | findstr /B /C:"OS Name" /C:"OS Version"`. Alternatively, run `ver` command or check Registry key: `HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion` for CurrentBuild and UBR values.
    Affected if The Windows build number is below the following thresholds depending on your version: Windows 10 1507 < 10240.21073, Windows 10 1607 < 14393.8246, Windows 10 1809 < 17763.7558, Windows 10 21h2 < 19044.6093, Windows 10 22h2 < 19045.6093, Windows 11 22h2 < 22621.5624, Windows 11 23h2 < 22631.5624, Win
  2. Identify if Workspace Broker component is present
    Check for the presence of Workspace Broker files or registry entries. Search for files named "WorkspaceBroker.exe" or related DLLs in typical installation paths such as `C:\Program Files\Microsoft\` or `C:\Program Files (x86)\`. Also check for the service in Services console (services.msc) looking for a service related to Workspace Broker.
    Affected if Workspace Broker software is installed on the system, regardless of whether it is currently running.
  3. Check if Workspace Broker service is running
    Open Task Manager or run `tasklist | findstr -i workspace` or `get-process | where-object {$_.name -like "*workspace*"}` in PowerShell to list running processes. Also check services via `sc queryex type= service state= all` looking for Workspace Broker entries.
    Affected if The Workspace Broker process or service is actively running on the system.

You are affected if your Windows build number falls below the threshold for your specific Windows version AND Workspace Broker is installed on your system.

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.10240.21073 / 10.0.14393.8246 / 10.0.17763.7558 or later
Fixed in 10.0.10240.2107310.0.14393.824610.0.17763.7558
Interim mitigation

Apply vendor-provided patches for Workspace Broker. If no patch exists, conduct code review to identify and fix the improper synchronization around shared resource access, and implement proper locking mechanisms.

Recommended fix High confidence

Apply the Windows security update containing the fix for CVE-2025-49665 (KB reference available at msrc.microsoft.com) - version requirements: Windows 10 1507: 10.0.10240.21073+ | Windows 10 1607: 10.0.14393.8246+ | Windows 10 1809: 10.0.17763.7558+ | Windows 10 21h2: 10.0.19044.6093+ | Windows 10 2

  1. Open Settings > Update & Security > Windows Update and check for available updates
  2. If updates are not automatically offered, visit the Microsoft Update Catalog (catalog.update.microsoft.com) and search for the relevant KB for this CVE (CVE-2025-49665)
  3. Download and install the appropriate security update for your Windows version and architecture
  4. Restart the system after the update is installed
  5. Verify the installed security update by running: winver or by checking the installed updates list in Control Panel > Programs and Features > View installed updates
Caveat Standard Windows security update with no expected breaking changes; as with any system update, test in a non-production environment first if possible

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
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,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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