dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2025-59511

HIGH · 7.8 CVSS v3.1 Published 2025-11-11
Fix available
A fix is available. Upgrade to 10.0.17763.8027 / 10.0.19044.6575 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
External control of file name or path in Windows WLAN 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

A local privilege escalation vulnerability exists in the Windows WLAN Service due to external control of file name or path, allowing an authorized local attacker to manipulate file locations and gain elevated system privileges.

MitigationApply the Microsoft security patch for CVE-2025-59511 when released and verify WLAN service functionality remains normal after deployment.

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 1809Operating system
Affected:< 10.0.17763.8027
Windows 10 21h2Operating system
Affected:< 10.0.19044.6575
Windows 10 22h2Operating system
Affected:< 10.0.19045.6575
Windows 11 23h2Operating system
Affected:< 10.0.22631.6199
Windows 11 24h2Operating system
Affected:< 10.0.26100.7092
Windows 11 25h2Operating system
Affected:< 10.0.26200.7092
Windows Server 2019Operating system
Affected:< 10.0.17763.8027
Windows Server 2022Operating system
Affected:< 10.0.20348.4346

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 build number
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to obtain the exact build number
    Affected if The build number falls below any of these thresholds: 17763.8027 (Windows 10 1809/Server 2019), 19044.6575 (Windows 10 21h2), 19045.6575 (Windows 10 22h2), 22631.6199 (Windows 11 23h2), 26100.7092 (Windows 11 24h2), 26200.7092 (Windows 11 25h2), or 20348.4346 (Windows Server 2022)
  2. Verify WLAN Service presence
    Open Services console (services.msc) or run 'Get-Service -Name WlanSvc' in PowerShell to confirm the WLAN Service is installed
    Affected if The WLAN Service (WlanSvc) is present on the system, indicating the vulnerable component exists
  3. Confirm WLAN Service status
    Run 'Get-Service -Name WlanSvc' in PowerShell or check via Services console to see if the service is running or set to start
    Affected if The WLAN Service is installed and either running or set to automatic/manual start, making it a potential attack vector for local privilege escalation

The system is likely affected if it runs any Windows version with a build number lower than the patched versions listed AND has the WLAN Service present and enabled.

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.17763.8027 / 10.0.19044.6575 / 10.0.19045.6575 or later
Fixed in 10.0.17763.802710.0.19044.657510.0.19045.6575
Interim mitigation

Apply the Microsoft security patch for CVE-2025-59511 when released and verify WLAN service functionality remains normal after deployment.

Recommended fix High confidence

Windows 10 1809: 10.0.17763.8027 | Windows 10 21h2: 10.0.19044.6575 | Windows 10 22h2: 10.0.19045.6575 | Windows 11 23h2: 10.0.22631.6199 | Windows 11 24h2: 10.0.26100.7092 | Windows 11 25h2: 10.0.26200.7092 | Windows Server 2019: 10.0.17763.8027 | Windows Server 2022: 10.0.20348.4346

  1. Open Windows Settings and navigate to Update & Security > Windows Update
  2. Click 'Check for updates' to download and install the latest security updates
  3. Alternatively, manually download and install the specific KB patch for this CVE from the Microsoft Update Catalog (search by CVE number)
  4. Restart the system after applying the update
  5. Verify the update was installed successfully by checking Windows Update history
Caveat Standard Windows security update with no expected breaking changes; as with any system update, test in non-production environment first if possible

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

Fix this in Windows 10 1809 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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