dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-58619

HIGH · 7.0 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 10.0.14393.9339 / 10.0.17763.9020 or later.
See remediation →
72/100
Remediation priority · Elevated
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
Use after free in Windows Sensor Data Service 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 use-after-free vulnerability exists in the Windows Sensor Data Service where memory is accessed after being freed, allowing a locally authorized attacker to elevate privileges to higher permission levels.

MitigationApply the relevant Microsoft security patch for Windows Sensor Data Service through Windows Update or enterprise patch management to remediate the memory corruption.

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 1607Operating system
Affected:< 10.0.14393.9339
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 2016Operating system
Affected:< 10.0.14393.9339

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/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 version against affected ranges
    Run 'winver' or 'systeminfo' from command prompt and note the Windows build number shown (e.g., 10.0.14393.x for Windows 10 1607/Server 2016, 10.0.17763.x for Windows 10 1809, etc.). Compare your build number to the minimum fixed versions: 14393.9339, 17763.9020, 19044.7548, 19045.7548, 26100.8875, 26200.8875, 28000.2269.
    Affected if Your Windows build number is LOWER than the corresponding threshold for your Windows version (10 1607/Server 2016 < 14393.9339, 10 1809 < 17763.9020, 10 21h2 < 19044.7548, 10 22h2 < 19045.7548, 11 24h2 < 26100.8875, 11 25h2 < 26200.8875, 11 26h1 < 28000.2269)
  2. Verify Windows Sensor Data Service presence
    Open Services console (services.msc) or run 'sc query SensorService' from an elevated command prompt to check if the Windows Sensor Data Service exists on the system.
    Affected if The Windows Sensor Data Service (SensorService) is installed and present on the system
  3. Confirm Sensor Data Service status
    Run 'sc query SensorService' or check the service status in services.msc to determine if the service is currently running.
    Affected if The Windows Sensor Data Service is currently running (even if not actively used by the user, the vulnerable code path exists when the service is active)

You are affected if your Windows version/build falls within any of the affected ranges listed AND the Windows Sensor Data Service is present on your system, since the use-after-free vulnerability exists in that specific service component.

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.14393.9339 / 10.0.17763.9020 / 10.0.19044.7548 or later
Fixed in 10.0.14393.933910.0.17763.902010.0.19044.7548
Interim mitigation

Apply the relevant Microsoft security patch for Windows Sensor Data Service through Windows Update or enterprise patch management to remediate the memory corruption.

Recommended fix High confidence

Upgrade to Windows 10 1607 build 10.0.14393.9339 or later; Windows 10 1809 build 10.0.17763.9020 or later; Windows 10 21h2 build 10.0.19044.7548 or later; Windows 10 22h2 build 10.0.19045.7548 or later; Windows 11 24h2 build 10.0.26100.8875 or later; Windows 11 25h2 build 10.0.26200.8875 or later; W

  1. Open Settings > Update & Security > Windows Update, or run 'ms-settings:windowsupdate'
  2. Click 'Check for updates' to download and install the latest cumulative update
  3. Ensure the update includes the security fix for CVE-2026-58619
  4. After installation, restart the system to apply the changes
  5. Verify the installed version matches or exceeds: 10.0.14393.9339 (Win 10 1607/Server 2016), 10.0.17763.9020 (Win 10 1809), 10.0.19044.7548 (Win 10 21h2), 10.0.19045.7548 (Win 10 22h2), 10.0.26100.8875 (Win 11 24h2), 10.0.26200.8875 (Win 11 25h2), or 10.0.28000.2269 (Win 11 26h1)
Caveat Standard Windows update - no expected breaking changes; as a local privilege escalation fix, apply at earliest convenience

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

Fix this in Windows 10 1607 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-2026-58619 — 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-58619 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