dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2026-58628

HIGH · 7.8 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 10.0.17763.9020 / 10.0.19044.7548 or later.
See remediation →
80/100
Remediation priority · High
Zero-click 5 weeks old

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 Windows Wireless Networking allows an authorized attacker to elevate privileges locally.

In the news

Third-party coverage
Trending covered by 1 outlet this week · latest 1mo ago

Surfaced from public web coverage — external links open in a new tab.

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 Windows Wireless Networking where improper synchronization of shared resources allows an authorized local attacker to execute code with elevated privileges. The vulnerability stems from concurrent access to kernel-mode resources without proper locking mechanisms, enabling privilege escalation from a standard user to SYSTEM or administrator-level access.

MitigationApply the relevant Microsoft Windows security patch for this vulnerability when released. In the interim, limit local administrative access and monitor for suspicious processes interacting with wireless networking components.

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.9020
Windows 10 21h2Operating system
Affected:< 10.0.19044.7548
Windows 10 22h2Operating system
Affected:< 10.0.19045.7548
Windows 11 24h2Operating system
Affected:< 10.0.26100.8875
Windows 11 25h2Operating system
Affected:< 10.0.26200.8875
Windows 11 26h1Operating system
Affected:< 10.0.28000.2269
Windows Server 2019Operating system
Affected:< 10.0.17763.9020
Windows Server 2022Operating system
Affected:< 10.0.20348.5386

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

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/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 version
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to obtain the full version and build number
    Affected if The build number is lower than the fixed version for your Windows release (e.g., below 10.0.17763.9020 for Windows 10 1809/Server 2019, below 10.0.19044.7548 for Windows 10 21h2, below 10.0.19045.7548 for Windows 10 22h2, below 10.0.26100.8875 for Windows 11 24h2, below 10.0.26200.8875 for Windows 1
  2. Verify wireless networking component presence
    Open Device Manager, expand 'Network adapters' to confirm wireless adapters are present, or run 'netsh wlan show drivers' to check wireless driver status
    Affected if A wireless adapter is installed and the driver is loaded, making the wireless networking stack active on the system
  3. Confirm wireless service status
    Run 'Get-Service -Name WlanSvc' in PowerShell or check 'Windows Wireless LAN Service' in services.msc to see if the wireless service is running
    Affected if The wireless networking service (WlanSvc) is enabled and running, exposing the vulnerable code path

You are affected if your Windows build version is lower than the fixed build for your Windows release AND wireless networking hardware/feature is present and active 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.17763.9020 / 10.0.19044.7548 / 10.0.19045.7548 or later
Fixed in 10.0.17763.902010.0.19044.754810.0.19045.7548
Interim mitigation

Apply the relevant Microsoft Windows security patch for this vulnerability when released. In the interim, limit local administrative access and monitor for suspicious processes interacting with wireless networking components.

Recommended fix High confidence

Install the relevant Windows security update from Windows Update that patches to or beyond the listed build numbers for your Windows version

  1. Check current Windows version by running `winver` or `systeminfo | findstr /B /C:"OS Name" /C:"OS Version"`
  2. Open Settings > Update & Security > Windows Update
  3. Click 'Check for updates' to download and install available security updates
  4. Restart the computer when prompted to complete the installation
  5. Verify the update was installed by checking the Windows version matches or exceeds: Windows 10 1809: 10.0.17763.9020, Windows 10 21h2: 10.0.19044.7548, Windows 10 22h2: 10.0.19045.7548, Windows 11 24h2: 10.0.26100.8875, Windows 11 25h2: 10.0.26200.8875, Windows 11 26h1: 10.0.28000.2269, Windows Server 2019: 10.0.17763.9020, Windows Server 2022: 10.0.20348.5386
Caveat Standard Windows update; ensure backups of critical data exist before any system update as a precautionary measure

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

Fix this in Windows 10 1809 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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