dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-58629

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 DirectX 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 in Windows DirectX allows a locally authenticated attacker to elevate privileges to higher integrity levels. The vulnerability stems from improper memory management in DirectX components, where memory is accessed after being freed, potentially leading to arbitrary code execution with elevated privileges.

MitigationApply Microsoft security updates for Windows when available. Until a patch is released, limit local administrative access and monitor for suspicious processes interacting with DirectX 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 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 23h2Operating system
Affected:< 10.0.22631.7376
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

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 and build number
    Open Command Prompt and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to retrieve the exact Windows build
    Affected if The build number is lower than any of these thresholds: 14393.9339 (1607), 17763.9020 (1809), 19044.7548 (21h2), 19045.7548 (22h2), 22631.7376 (23h2), 26100.8875 (24h2), 26200.8875 (25h2), or 28000.2269 (26h1)
  2. Confirm DirectX is installed
    Run 'dxdiag' from the Run dialog or command line. Accept the prompt to view the DirectX Diagnostic Tool
    Affected if DirectX is present on the system (the vulnerability requires DirectX components to be available)
  3. Identify processes using DirectX components
    Use Task Manager or run 'tasklist /FI "IMAGENAME eq *"' combined with monitoring tools to list running processes. DirectX-based applications typically use d3d9.dll, d3d11.dll, or dxgi.dll
    Affected if Any untrusted or suspicious third-party applications using DirectX libraries are running on an affected Windows version

You are affected if your Windows build number falls below the thresholds listed for your Windows version AND DirectX is installed 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.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 Microsoft security updates for Windows when available. Until a patch is released, limit local administrative access and monitor for suspicious processes interacting with DirectX components.

Recommended fix High confidence

Windows 10 1607: 10.0.14393.9339 or later | Windows 10 1809: 10.0.17763.9020 or later | Windows 10 21h2: 10.0.19044.7548 or later | Windows 10 22h2: 10.0.19045.7548 or later | Windows 11 23h2: 10.0.22631.7376 or later | Windows 11 24h2: 10.0.26100.8875 or later | Windows 11 25h2: 10.0.26200.8875 or

  1. Open Windows Settings and navigate to Update & Security > Windows Update
  2. Click 'Check for updates' to download and install the latest security updates for your Windows version
  3. Alternatively, manually install the applicable cumulative security update from Microsoft Update Catalog for your specific Windows version (KB reference from MSRC)
  4. After updates are installed, restart your computer to complete the remediation
  5. Verify the update was applied by checking Windows Update history for recent security updates
Caveat Standard Windows update - minimal risk; ensure backups of critical data before any system update

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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