dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2026-24287

HIGH · 7.8 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 10.0.17763.8511 / 10.0.19044.7058 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 Kernel 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 path traversal vulnerability exists in the Windows Kernel where user-controlled input is used to construct file paths without proper validation. An authorized local attacker can manipulate file paths to gain elevated privileges, likely by accessing protected system files or resources.

MitigationApply Microsoft security updates for Windows Kernel when available; restrict file system access permissions and monitor for anomalous kernel-level file operations.

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.8511
Windows 10 21h2Operating system
Affected:< 10.0.19044.7058
Windows 10 22h2Operating system
Affected:< 10.0.19045.7058
Windows 11 23h2Operating system
Affected:< 10.0.22631.6783
Windows 11 24h2Operating system
Affected:< 10.0.26100.7979
Windows 11 25h2Operating system
Affected:< 10.0.26200.7979
Windows 11 26h1Operating system
Affected:< 10.0.28000.1719
Windows Server 2019Operating system
Affected:< 10.0.17763.8511

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 and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to display the installed Windows version and build number
    Affected if The build number falls below any of these thresholds: 17763.8511, 19044.7058, 19045.7058, 22631.6783, 26100.7979, 26200.7979, or 28000.1719 depending on your Windows release
  2. Identify Windows release version
    Run 'winver' to see the specific Windows release (such as 1809, 21h2, 22h2, 23h2, 24h2, 25h2, 26h1) or check System Properties to determine which release you are running
    Affected if You are running an affected release (Windows 10 1809, 10 21h2, 10 22h2, 11 23h2, 11 24h2, 11 25h2, 11 26h1, or Server 2019) and the build number is below the corresponding threshold for that release
  3. Check for pending or missing security updates
    Open Settings > Windows Update > Update history, or run 'wmic qfe list' in Command Prompt to display installed hotfixes. Look for recent Windows Kernel or security updates
    Affected if No recent kernel or security updates are installed, or the system shows the affected build version without security patches applied
  4. Verify Windows Server version if applicable
    If the system is Windows Server, run 'systeminfo' or 'winver' to confirm the server version and build number
    Affected if Running Windows Server 2019 with build number below 10.0.17763.8511

You are affected if your Windows version matches one of the listed releases AND your installed build number is below the corresponding threshold for that release.

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.8511 / 10.0.19044.7058 / 10.0.19045.7058 or later
Fixed in 10.0.17763.851110.0.19044.705810.0.19045.7058
Interim mitigation

Apply Microsoft security updates for Windows Kernel when available; restrict file system access permissions and monitor for anomalous kernel-level file operations.

Recommended fix High confidence

Windows Cumulative Updates (KB referenced in MSRC for CVE-2026-24287)

  1. 1. Apply the appropriate Windows cumulative update for your specific Windows version from Microsoft Update Catalog or Windows Update
  2. 2. Verify the installed build number matches or exceeds the fixed version for your Windows edition (1809: 10.0.17763.8511, 21h2: 10.0.19044.7058, 22h2: 10.0.19045.7058, 23h2: 10.0.22631.6783, 24h2: 10.0.26100.7979, 25h2: 10.0.26200.7979, 26h1: 10.0.28000.1719, Server 2019: 10.0.17763.8511)
  3. 3. Restart the system as prompted to complete the patch installation
  4. 4. Confirm the vulnerability is remediated by checking that the KB corresponding to this CVE is installed
Caveat Standard Windows update risks - test in staging environment before production deployment

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
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
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,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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