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

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

Which versions of Windows LSASS are affected by CVE-2026-40378?

CVE-2026-40378 enables unauthenticated remote attackers to disrupt authentication services across your Windows infrastructure, blocking user logon and domain operations.. A patch is available.

How to fix or mitigate CVE-2026-40378?

Immediately inventory all Windows 10, Windows 11, and Windows Server (2012-2025) systems in your environment. Within 24 hours, establish a prioritized patching plan with domain controllers and critical production servers marked for urgent deployment. Within 7 days, apply the Microsoft security patch for CVE-2026-40378 to all domain controllers and high-priority infrastructure. Within 30 days, complete deployment across all remaining Windows systems to achieve organization-wide remediation.

Windows LSASS CVE-2026-40378

EUVD-2026-43790 HIGH

Memory Allocation with Excessive Size Value (CWE-789)

2026-07-14 microsoft

GHSA-2jv5-2qvr-82qr

Authentication Bypass Microsoft Windows Server 2012 Windows Server 2016 Windows Server 2019 Windows Server 2022 Windows Server 2025 Windows 10 Version 1607 Windows 10 Version 1809 Windows 10 Version 21H2 Windows 10 Version 22H2 Windows Server 2016 Server Core Installation Windows Server 2019 Server Core Installation Windows 11 Version 23H2 Windows 11 Version 24H2 Windows 11 Version 25H2 Windows 11 Version 26H1 Windows Server 2025 Server Core Installation Windows Server 2012 Server Core Installation Windows Server 2012 R2 Windows Server 2012 R2 Server Core Installation

7.5

CVSS 3.1 · Vendor: microsoft

Temporal: 6.5

Severity by source

Vendor (microsoft) PRIMARY

7.5 HIGH

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

CIRCL (temporal)

6.5 MEDIUM

cvss

vuln.today AI

7.5 HIGH

Network-reachable LSASS with no auth or interaction and low complexity (AV:N/AC:L/PR:N/UI:N); impact is availability-only service crash, so C:N/I:N/A:H, scope unchanged.

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

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

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Lifecycle Timeline

Analysis Generated

Jul 14, 2026 - 18:40 vuln.today

CVE Published

Jul 14, 2026 - 17:05 cve.org

HIGH 7.5

DescriptionCVE.org

Memory allocation with excessive size value in Windows Local Security Authority Subsystem Service (LSASS) allows an unauthorized attacker to deny service over a network.

AnalysisAI

Denial of service in the Windows Local Security Authority Subsystem Service (LSASS) allows a remote, unauthenticated attacker to crash the service and disrupt authentication across all supported Windows client and server releases from Windows 10 1607 through Windows 11 26H1 and Windows Server 2012 through Server 2025. The flaw stems from an excessive-size memory allocation (CWE-789) triggerable over the network with no privileges or user interaction, and while a vendor patch is available, there is no public exploit identified at time of analysis and it is not listed in CISA KEV. Impact is limited to availability (A:H) with no confidentiality or integrity loss, but LSASS failure can force system instability or reboots, affecting domain authentication and logon.

Technical ContextAI

LSASS is the core Windows process responsible for enforcing security policy, validating logons, handling password changes, and issuing access tokens - its availability is essential for authentication and Active Directory operations. The root cause is CWE-789 (Memory Allocation with Excessive Size Value): an attacker-controlled length or count field in a network-reachable request is used to size a memory allocation without adequate bounds checking, leading to an oversized or failed allocation that crashes or hangs the process. Per the CPE data, the affected component ships across the full Windows family: Windows 10 (1607, 1809, 21H2, 22H2), Windows 11 (23H2, 24H2, 25H2, 26H1), and Windows Server 2012, 2012 R2, 2016, 2019, 2022, and 2025, including Server Core installations. Because LSASS is exposed to authentication-related network protocols, a single malformed request can exhaust or corrupt allocation state and terminate the service.

RemediationAI

Apply the Microsoft security update for CVE-2026-40378 as the primary fix - Patch available per vendor advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-40378; consult the MSRC update guide for the exact fixed build number matching each affected SKU, as specific patched version numbers were not provided in this data set and should not be invented. Prioritize internet-facing and domain controller / authentication-critical hosts. Where immediate patching is not possible, reduce network exposure of LSASS-related authentication services: restrict inbound access to affected hosts using host and perimeter firewalls so only trusted management and domain networks can reach authentication ports (trade-off: may break legitimate remote authentication or cross-segment logons if over-restricted), and place domain controllers and servers behind segmentation that blocks untrusted network reachability. Because the impact is a service crash rather than code execution, monitoring LSASS process health and configuring automatic recovery/alerting can shorten outages while patches are staged. Avoid third-party 'fixes'; use the official Microsoft update only.