dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-59201

HIGH · 7.8 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
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
Improper access control in Network Connection Status Indicator (NCSI) 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 local privilege escalation vulnerability in Windows Network Connection Status Indicator (NCSI) stemming from improper access control. An authorized local attacker can exploit this vulnerability to elevate their privileges on the affected system.

MitigationApply the Microsoft security update addressing CVE-2025-59201 to patch the improper access control vulnerability in NCSI.

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
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. Identify Windows build number
    Open Command Prompt or PowerShell and run: `winver` or `systeminfo | findstr /B /C:"OS Name" /C:"OS Version"`
    Affected if The displayed build number falls below the affected threshold for your Windows release (see step 2)
  2. Determine Windows release version
    Run `winver` to identify if you are on Windows 10 1507, 1607, 1809, 21h2, 22h2, or Windows 11 22h2, 23h2, or 24h2
    Affected if Your Windows release matches one of the affected versions listed in the CVE
  3. Compare build against affected thresholds
    Run `ver` in Command Prompt or check the build number from winver. Compare against: 10240.21161 (Win10 1507), 14393.8519 (Win10 1607), 17763.7919 (Win10 1809), 19044.6456 (Win10 21h2), 19045.6456 (Win10 22h2), 22621.6060 (Win11 22h2), 22631.6060 (Win11 23h2), 26100.6899 (Win11 24h2)
    Affected if Your installed build number is lower than the corresponding threshold for your Windows release

You are affected if your Windows version and build number fall within any of the affected ranges listed in the CVE - the vulnerability exists in the NCSI component due to improper access control in the unpatched versions.

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

Apply the Microsoft security update addressing CVE-2025-59201 to patch the improper access control vulnerability in NCSI.

Recommended fix High confidence

Upgrade to the latest Windows cumulative update that includes the CVE-2025-59201 fix (minimum fixed build for your Windows version as listed in the Microsoft Security Response Center)

  1. Open Settings > Update & Security > Windows Update
  2. Click 'Check for updates' to download and install the latest cumulative update for your Windows version
  3. Verify the update installed successfully by checking Windows Update history
  4. Confirm the build number matches or exceeds the fixed version for your Windows release: Windows 10 1507 should be 10.0.10240.21161 or later, Windows 10 1607 should be 10.0.14393.8519 or later, Windows 10 1809 should be 10.0.17763.7919 or later, Windows 10 21h2 should be 10.0.19044.6456 or later, Windows 10 22h2 should be 10.0.19045.6456 or later, Windows 11 22h2 should be 10.0.22621.6060 or later,
  5. Restart the system if prompted to complete the installation
Caveat Standard Windows update risks - ensure backups of critical data before applying

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 / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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