What is the CVSS score of CVE-2026-50360?

CVE-2026-50360 has a CVSS 3.1 base score of 8.8 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.5%.

Which versions of Windows SMB Server are affected by CVE-2026-50360?

Microsoft Windows SMB Server (affecting Windows 10, 11, and Server 2022/2025) contains a privilege escalation vulnerability that could impact system integrity and confidentiality across enterprise…. A patch is available.

How to fix or mitigate CVE-2026-50360?

Within 24 hours: Inventory all Windows 10 (21H2/22H2), Windows 11 (24H2/25H2/26H1), Windows Server 2022, and Windows Server 2025 systems to determine patch scope and prioritization strategy. Within 7 days: Deploy the Microsoft vendor-released patch to all affected systems, prioritizing administrative workstations, domain controllers, and file servers. Within 30 days: Complete patch deployment across all identified systems and verify compliance through endpoint management tools or WSUS reporting.

Windows SMB Server CVE-2026-50360

EUVD-2026-43858 HIGH

Incorrect Implementation of Authentication Algorithm (CWE-303)

2026-07-14 microsoft

GHSA-rc38-f4j6-jq4f

Information Disclosure Microsoft Windows Server 2022 Windows Server 2025 Windows 10 Version 21H2 Windows 10 Version 22H2 Windows 11 Version 24H2 Windows 11 Version 25H2 Windows 11 Version 26H1 Windows Server 2025 Server Core Installation

8.8

CVSS 3.1 · Vendor: microsoft

Severity by source

Vendor (microsoft) PRIMARY

8.8 HIGH

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

vuln.today AI

8.8 HIGH

Network-reachable SMB (AV:N) with low complexity (AC:L) exploitable by an authenticated low-privileged user (PR:L) and no interaction, yielding full host compromise (C/I/A:H).

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Jul 14, 2026 - 21:27 vuln.today

CVE Published

Jul 14, 2026 - 17:06 nvd

HIGH 8.8

DescriptionCVE.org

Incorrect implementation of authentication algorithm in Windows SMB Server allows an authorized attacker to elevate privileges over a network.

AnalysisAI

Privilege escalation in Microsoft Windows SMB Server allows an already-authenticated network attacker to elevate to higher privileges by abusing a flawed authentication algorithm, yielding high confidentiality, integrity, and availability impact. The flaw affects Windows 10 (21H2/22H2), Windows 11 (24H2/25H2/26H1), and Windows Server 2022/2025 including Server Core. Reported by Microsoft with a patch available; no public exploit identified at time of analysis.

Technical ContextAI

The Server Message Block (SMB) service is Windows' core file-, printer-, and named-pipe-sharing protocol, reachable over the network on TCP 445 and enabled by default on virtually all Windows hosts. This issue is classified as CWE-303 (Incorrect Implementation of Authentication Algorithm), meaning the server's authentication logic is coded incorrectly rather than merely misconfigured - an authenticated party can subvert the intended access-control decision the algorithm was meant to enforce. Per the affected CPE set, the defect spans the SMB Server component shipped across current Windows 10, Windows 11, and Windows Server 2022/2025 (including Server Core) builds.

RemediationAI

Apply the Microsoft security update for CVE-2026-50360 as delivered through Windows Update / WSUS for each affected SKU; Patch available per vendor advisory (see https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-50360 for the exact patched build per product), as no single fix version string is provided in the input. Because exploitation requires authenticated network access to SMB, compensating controls until patching is complete include blocking inbound TCP 445 at the host and network firewall for hosts that do not need to serve SMB (side effect: breaks Windows file/printer sharing and domain functions like SYSVOL/GPO access if applied to servers that need it), restricting SMB access to trusted management subnets, enforcing SMB signing and, where feasible, disabling SMBv1, and tightening account privileges so a low-privileged foothold has fewer lateral targets. Prioritize domain controllers, file servers, and any internet- or broadly-network-exposed Windows hosts.