CVE Tools
Track your stack

CVE-2025-59200

Data Sharing Service Spoofing Vulnerability

No known exploitation. EPSS puts it in the 56th percentile. Fixed versions are out.

CVSS 3.17.7HighEPSS percentile56th0.8% chance in 30 daysCISA KEVNot listedNo confirmed exploitation
No public exploit knownFix5 products10 fixed builds listed below

Published Updated Sources: CVE.org, NVD, BDU

NVD CVE.org

What to do

Find your product and version, then upgrade to the build on the right.

  • Microsoft Windows Server 2016Affected: ≥ 10.0.14393.0, < 10.0.14393.8519Upgrade to: 10.0.14393.8519Stated by: CVE record
  • Microsoft Windows 10 Version 1507Affected: ≥ 10.0.10240.0, < 10.0.10240.21161Upgrade to: 10.0.10240.21161Affected: ≥ 10.0.14393.0, < 10.0.14393.8519Upgrade to: 10.0.14393.8519Affected: ≥ 10.0.17763.0, < 10.0.17763.7919Upgrade to: 10.0.17763.7919Affected: ≥ 10.0.19044.0, < 10.0.19044.6456Upgrade to: 10.0.19044.6456 + 1 more branchStated by: CVE record
  • Microsoft Windows Server 2025Affected: ≥ 10.0.26100.0, < 10.0.26100.6899Upgrade to: 10.0.26100.6899Stated by: CVE record
  • Microsoft Windows 11 version 22H2Affected: ≥ 10.0.22621.0, < 10.0.22621.6060Upgrade to: 10.0.22621.6060Affected: ≥ 10.0.22631.0, < 10.0.22631.6060Upgrade to: 10.0.22631.6060Affected: ≥ 10.0.26100.0, < 10.0.26100.6899Upgrade to: 10.0.26100.6899Affected: ≥ 10.0.26200.0, < 10.0.26200.6899Upgrade to: 10.0.26200.6899Stated by: CVE record
  • Microsoft Windows Server 2022Affected: ≥ 10.0.20348.0, < 10.0.20348.4294Upgrade to: 10.0.20348.4294Affected: ≥ 10.0.25398.0, < 10.0.25398.1913Upgrade to: 10.0.25398.1913Stated by: CVE record

Versions as the sources state them. 1 more product has version data. Full version matrix after sign-in

Check it yourselfA free OpenVAS check exists for this CVE. Run it against your hosts.Is your organisation exposed?Request an assessment to establish which checks fit your systems.

What it is

From the CVE record

Concurrent execution using shared resource with improper synchronization ('race condition') in Data Sharing Service Client allows an unauthorized attacker to perform spoofing locally.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS56th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.8% chance of exploitation activity in the next 30 days, which ranks it in the 56th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

6 events over 254 days, from the signal feeds we watch.

  1. OpenVAS check added
  2. Patch availablerecord updated
  3. Publishedweakness classified, att&ck mapped

Affected products

And 44 more affected products. See all after sign-in

Technical detail

CVSS 3.1 vector

Open in the CVSS calculator

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

Scored 7.7 by NVD.

How it is reached

  • Attack Vector LocalRequires local access to the vulnerable system (e.g. local login, malicious file)
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction RequiredA user must click a link, open a file, or perform some action

Scope

  • Scope ChangedThe exploit can affect other components (e.g. sandbox escape, host compromise from VM)

Impact if exploited

  • Confidentiality LowSome restricted information is disclosed, but limited in scope
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability LowReduced performance or intermittent disruption of service

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

References in the record

In the news

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Microsoft Corp, not every advisory.