dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-24294

HIGH · 7.8 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 10.0.14393.8957 / 10.0.17763.8511 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
Improper authentication in Windows SMB Server 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

Improper authentication in Windows SMB Server enables a locally authorized attacker to bypass normal authentication checks and elevate their privileges to a higher level on the affected system.

MitigationApply Microsoft security patches for this vulnerability and ensure SMB server configurations follow least-privilege principles.

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.8957
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

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. Confirm SMB Server is enabled
    Run 'Get-Service -Name SMBserver' in PowerShell or check Services.msc for 'SMB 1.0 CIFS Server' and 'SMB 2.0 and 3.0 file sharing support' features under Windows Features. Also verify via 'Get-WindowsOptionalFeature -Online -FeatureName SMB1Protocol' and 'SMB2Protocol'
    Affected if SMB Server is installed and enabled - the vulnerability exists in the SMB Server component, so it only applies when SMB is present on the system
  2. Check Windows build version
    Run 'winver' or execute 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' in Command Prompt, or use 'Get-ComputerInfo | Select-Object WindowsVersion, OsBuildNumber' in PowerShell
    Affected if The installed build number falls within any of these vulnerable ranges: Windows 10 1607 < 10.0.14393.8957, Windows 10 1809 < 10.0.17763.8511, Windows 10 21h2 < 10.0.19044.7058, Windows 10 22h2 < 10.0.19045.7058, Windows 11 23h2 < 10.0.22631.6783, Windows 11 24h2 < 10.0.26100.7979, Windows 11 25h2 <
  3. Verify SMB configuration settings
    Run 'Get-SmbServerConfiguration | Select-Object RequireSecuritySignature, EnableSecuritySignature, AuthenUserMaxPasswordAge' in PowerShell to review SMB signing and authentication settings
    Affected if SMB signing is not enforced (RequireSecuritySignature is False) - this relates to the authentication bypass aspect of the flaw

The system is affected if SMB Server is enabled AND the Windows build version is lower than the fixed build for your specific Windows version.

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.8957 / 10.0.17763.8511 / 10.0.19044.7058 or later
Fixed in 10.0.14393.895710.0.17763.851110.0.19044.7058
Interim mitigation

Apply Microsoft security patches for this vulnerability and ensure SMB server configurations follow least-privilege principles.

Recommended fix High confidence

Apply the corresponding Windows security update (KB) that addresses CVE-2026-24294 - the minimum fixed build numbers are: Windows 10 1607 (10.0.14393.8957), Windows 10 1809 (10.0.17763.8511), Windows 10 21h2 (10.0.19044.7058), Windows 10 22h2 (10.0.19045.7058), Windows 11 23h2 (10.0.22631.6783), Win

  1. 1. Ensure Windows Update is enabled and configured to automatically receive security updates
  2. 2. Run Windows Update: Open Settings > Update & Security > Windows Update and click 'Check for updates'
  3. 3. Install all available security updates, particularly those marked as cumulative updates for Windows
  4. 4. After updates are installed, restart the affected system to complete the patching process
  5. 5. Verify the SMB Server version has been updated by running 'winver' to confirm the build number matches or exceeds the fixed version for your Windows edition
Caveat Standard Windows update risks apply - ensure backups and system restore points exist before applying updates in production environments

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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