dbcve.org
Windows 11 24h2Operating system · Microsoft

CVE-2025-50169

HIGH · 7.5 CVSS v3.1 Published 2025-08-12
Fix available
A fix is available. Upgrade to 10.0.26100.4851 or later.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges

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
Concurrent execution using shared resource with improper synchronization ('race condition') in Windows SMB allows an unauthorized attacker to execute code over a network.

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 race condition vulnerability exists in Windows SMB (Server Message Block) that allows an unauthenticated remote attacker to execute arbitrary code by exploiting improper synchronization in concurrent SMB operations. The vulnerability stems from the way Windows handles shared resources during simultaneous SMB connections, enabling an attacker to win the race condition and achieve code execution.

MitigationApply the latest Microsoft Windows security updates addressing CVE-2025-50169 to all affected Windows systems. Additionally, restrict SMB access to trusted networks using firewalls, disable SMBv1, and enforce network-level authentication (SMB signing) to reduce the attack surface while patching.

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.4851
Windows Server 2025Operating system
Affected:< 10.0.26100.4851

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
Network
Complexity
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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. Identify the Windows version and build number
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to get the exact Windows version and build. Alternatively, run 'ver' at command prompt.
    Affected if The system is Windows 11 24h2 or Windows Server 2025 with a build number lower than 10.0.26100.4851
  2. Verify SMB service status
    Run 'Get-Service -Name SmbServer' in PowerShell or check Services.msc for the 'Server' (SMB) service to see if it is running.
    Affected if SMB service is running and exposed to the network
  3. Check SMB protocol versions enabled
    Run 'Get-WindowsOptionalFeature -Online -FeatureName SMB1Protocol' in PowerShell to check if SMBv1 is installed/enabled. Also run 'Get-SmbServerConfiguration' to view SMB server settings.
    Affected if SMBv1 is enabled or SMB is generally accessible without additional hardening
  4. Verify SMB network listening status
    Run 'Get-NetTCPConnection -State Listen | Where-Object {$_.LocalPort -eq 445}' to confirm SMB is listening on port 445, or use 'netstat -an | findstr :445'.
    Affected if Port 445 is open and listening on external or untrusted network interfaces
  5. Check firewall and network exposure of SMB
    Run 'Get-NetFirewallRule -DisplayName "File and Printer Sharing (SMB-In)"' in PowerShell to see if SMB firewall rules allow incoming connections from untrusted networks.
    Affected if SMB firewall rules permit connections from untrusted or external networks

The system is vulnerable if it runs Windows 11 24h2 or Windows Server 2025 with build below 10.0.26100.4851 AND has SMB exposed to untrusted networks.

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.26100.4851 or later
Fixed in 10.0.26100.4851
Interim mitigation

Apply the latest Microsoft Windows security updates addressing CVE-2025-50169 to all affected Windows systems. Additionally, restrict SMB access to trusted networks using firewalls, disable SMBv1, and enforce network-level authentication (SMB signing) to reduce the attack surface while patching.

Recommended fix High confidence

Windows 11 24h2 build 10.0.26100.4851 (KB5055527) or later | Windows Server 2025 build 10.0.26100.4851 (KB5055527) or later

  1. Check current Windows build version by running 'winver' or 'systeminfo' in Command Prompt
  2. Back up critical data and files before initiating the update
  3. Ensure the system is connected to a stable power source to prevent interruption during installation
  4. Open Settings > Windows Update and select 'Check for updates', or visit Microsoft Update Catalog (catalog.update.microsoft.com) to manually download KB5055527 for Windows 11 24h2 / Windows Server 2025
  5. Install the cumulative update and restart the system when prompted
  6. After reboot, verify the installed version is 10.0.26100.4851 or later using 'winver' command
Caveat Standard Windows cumulative update - minimal risk; verify critical applications are compatible 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
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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