dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-59200

HIGH · 7.7 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 10.0.10240.21161 / 10.0.14393.8519 or later.
See remediation →
80/100
Remediation priority · High
No privileges

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 Data Sharing Service Client allows an unauthorized attacker to perform spoofing 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 vulnerability exists in the Data Sharing Service Client where concurrent execution of shared resources lacks proper synchronization. An unauthenticated local attacker can exploit this to perform spoofing attacks by manipulating the timing of operations to gain unauthorized access or impersonate other entities in the data sharing context.

MitigationImplement proper locking mechanisms (mutexes, semaphores, or atomic operations) around shared resources in the Data Sharing Service Client to ensure thread-safe operations and prevent race conditions.

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.21161
Windows 10 1607Operating system
Affected:< 10.0.14393.8519
Windows 10 1809Operating system
Affected:< 10.0.17763.7919
Windows 10 21h2Operating system
Affected:< 10.0.19044.6456
Windows 10 22h2Operating system
Affected:< 10.0.19045.6456
Windows 11 22h2Operating system
Affected:< 10.0.22621.6060
Windows 11 23h2Operating system
Affected:<= 10.0.22631.6060
Windows 11 24h2Operating system
Affected:< 10.0.26100.6899

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

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

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. Identify Windows build version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to obtain the full build number (e.g., 10.0.19045.6456)
    Affected if The build number falls below any of these thresholds: 10240.21161, 14393.8519, 17763.7919, 19044.6456, 19045.6456, 22621.6060, 22631.6060, or 26100.6899 depending on your Windows release
  2. Confirm Data Sharing Service is present
    Run 'sc query dssvc' or 'Get-Service -Name dssvc' to query the Data Sharing Service status
    Affected if The service exists and returns a state (running, stopped, or paused)
  3. Verify service executable version
    Locate the Data Sharing Service Client binary (typically in C:\Windows\System32\dssvc.exe) and right-click to view Properties > Details for the File Version
    Affected if The file version is lower than the corresponding Windows build patch level for your release

You are affected if your Windows build version is lower than the thresholds listed for your specific release and the Data Sharing Service Client binary is present on the 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.21161 / 10.0.14393.8519 / 10.0.17763.7919 or later
Fixed in 10.0.10240.2116110.0.14393.851910.0.17763.7919
Interim mitigation

Implement proper locking mechanisms (mutexes, semaphores, or atomic operations) around shared resources in the Data Sharing Service Client to ensure thread-safe operations and prevent race conditions.

Recommended fix High confidence

Windows 10 1507: Build 10.0.10240.21161 or later | Windows 10 1607: Build 10.0.14393.8519 or later | Windows 10 1809: Build 10.0.17763.7919 or later | Windows 10 21h2: Build 10.0.19044.6456 or later | Windows 10 22h2: Build 10.0.19045.6456 or later | Windows 11 22h2: Build 10.0.22621.6060 or later |

  1. 1. Identify the current Windows version and build number by running 'winver' or 'systeminfo' in Command Prompt
  2. 2. Determine which Windows 10 or 11 version and build is installed (1507, 1607, 1809, 21h2, 22h2, 23h2, or 24h2)
  3. 3. Open Windows Update by navigating to Settings > Update & Security > Windows Update
  4. 4. Click 'Check for updates' to download and install the latest security updates
  5. 5. For enterprise or managed systems, deploy the applicable monthly security update from the Microsoft Update Catalog matching your Windows version (e.g., KB5055523 for January 2025 or later)
  6. 6. Restart the system when prompted to complete the installation
  7. 7. Verify the update was applied by checking the build number matches or exceeds the fixed version for your Windows release
Caveat Standard Windows update with no expected breaking changes; as a local privilege spoofing fix, apply per normal patching cadence

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 / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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