dbcve.org
Windows 11 24h2Operating system · Microsoft

CVE-2026-24283

HIGH · 8.8 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 10.0.25398.2207 / 10.0.26100.7979 or later.
See remediation →
90/100
Remediation priority · Urgent
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
Heap-based buffer overflow in Windows File 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

Heap-based buffer overflow vulnerability in Windows File Server enabling a local authenticated attacker to elevate privileges to higher integrity levels. The flaw allows code execution with elevated permissions by exploiting memory corruption in the file server component.

MitigationApply Microsoft security updates for Windows File Server components immediately upon release; enforce least privilege access and limit local attacker surface.

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 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 2022 23h2Operating system
Affected:< 10.0.25398.2207
Windows Server 2025Operating system
Affected:< 10.0.26100.32463

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

CVSS:3.1/AV:L/AC:L/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 number
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to obtain the full build number (e.g., 10.0.26100.xxxx)
    Affected if The build number is lower than the threshold for your Windows version: 24h2 (<10.0.26100.7979), 25h2 (<10.0.26200.7979), 26h1 (<10.0.28000.1719), Server 2022 23h2 (<10.0.25398.2207), Server 2025 (<10.0.26100.32463)
  2. Verify File Server role is installed
    Run 'Get-WindowsOptionalFeature -Online -FeatureName *FileServer*' in PowerShell or check via Server Manager > Add Roles and Features > File Server role
    Affected if The File Server role or any File Server component (such as File Server Storage Services, SMB server) is enabled on the system
  3. Confirm SMB service is running
    Run 'Get-Service -Name *Server*' or 'sc query mup' to check if the Server service (which handles SMB file sharing) is active
    Affected if The Server service (srv2.sys or related SMB components) is running, as this is the file server component where the vulnerability exists

You are affected if your Windows build number falls below the threshold for your specific version AND the File Server/SMB server component is installed and running on your 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.25398.2207 / 10.0.26100.7979 / 10.0.26100.32463 or later
Fixed in 10.0.25398.220710.0.26100.797910.0.26100.32463
Interim mitigation

Apply Microsoft security updates for Windows File Server components immediately upon release; enforce least privilege access and limit local attacker surface.

Recommended fix High confidence

Apply Microsoft security updates to reach the fixed build versions: 10.0.26100.7979 (Win11 24h2), 10.0.26200.7979 (Win11 25h2), 10.0.28000.1719 (Win11 26h1), 10.0.25398.2207 (Server 2022 23h2), or 10.0.26100.32463 (Server 2025)

  1. Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. For Windows 11 24h2: Upgrade to build 10.0.26100.7979 or later
  3. For Windows 11 25h2: Upgrade to build 10.0.26200.7979 or later
  4. For Windows 11 26h1: Upgrade to build 10.0.28000.1719 or later
  5. For Windows Server 2022 23h2: Upgrade to build 10.0.25398.2207 or later
  6. For Windows Server 2025: Upgrade to build 10.0.26100.32463 or later
  7. Apply the corresponding Microsoft security update via Windows Update or WSUS
  8. Restart the system as required after applying the update
Caveat Standard Windows security update risks apply - ensure backups and test in staging before production deployment

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

Fix this in Windows 11 24h2 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
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,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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