Microsoft has published CVE-2026-121680, a spoofing vulnerability in Windows NTLM. Microsoft rates it Important, with a CVSS 3.1 base score of 7.5 (High). The flaw can disclose a user's NTLMv2 hash to an attacker. The fix is in the November 2026 security updates for supported Windows client and server versions. Microsoft Office for Android is also affected.
Advisory details
| CVE | CVE-2026-121680 |
|---|---|
| Title | Windows NTLM Spoofing Vulnerability |
| Assigning CNA | Microsoft |
| Release | 2026-Nov, released 2026-11-10 |
| Latest revision | 1.1, 2026-11-13: Microsoft Office software added to the Security Updates table |
| Severity (Microsoft) | Important |
| Impact | Spoofing |
| CVSS 3.1 base score | 7.5 (High) |
| CVSS 3.1 temporal score | 6.5 |
| Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N/E:U/RL:O/RC:C |
| Weakness | CWE-522: Insufficiently Protected Credentials |
| Publicly disclosed | No |
| Exploitability assessment | Less Likely (latest software release) |
| Customer action required | Yes |
Microsoft's description: "Exposure of sensitive information to an unauthorized actor in Windows NTLM allows an unauthorized attacker to perform spoofing over a network."
How an attack works, according to Microsoft
Microsoft says the flaw discloses a user's NTLMv2 hash to the attacker. The attacker could use this hash to authenticate as the user.
Microsoft's FAQ describes the method. An external attacker sends specially crafted emails. These cause a connection from the victim to a location the attacker controls. That connection leaks the victim's Net-NTLMv2 hash. The attacker can then relay the hash to another service and authenticate as the victim.
Affected products and security updates
The tables below reproduce every row of Microsoft's Security Updates table (29 rows), split by product group. Where Microsoft lists two updates for one product, both are shown with their own fixed build and restart requirement.
Windows 11
| Product | Security update | Fixed build | Restart required |
|---|---|---|---|
| Windows 11 version 26H1 for x64-based Systems | KB5132059 | 10.0.28000.3501 | Yes |
| Windows 11 Version 26H1 for ARM64-based Systems | KB5132059 | 10.0.28000.3501 | Yes |
| Windows 11 Version 26H2 for x64-based Systems | KB5132061 KB5132043 | 10.0.26300.9974 10.0.26300.9911 | Yes No |
| Windows 11 Version 26H2 for ARM64-based Systems | KB5132061 KB5132043 | 10.0.26300.9974 10.0.26300.9911 | Yes No |
| Windows 11 Version 25H2 for x64-based Systems | KB5132061 KB5132043 | 10.0.26200.9974 10.0.26200.9911 | Yes No |
| Windows 11 Version 24H2 for x64-based Systems | KB5132061 KB5132043 | 10.0.26100.9974 10.0.26100.9911 | Yes No |
| Windows 11 Version 25H2 for ARM64-based Systems | KB5132061 KB5132043 | 10.0.26200.9974 10.0.26200.9911 | Yes No |
| Windows 11 Version 24H2 for ARM64-based Systems | KB5132061 KB5132043 | 10.0.26100.9974 10.0.26100.9911 | Yes No |
| Windows 11 Version 23H2 for x64-based Systems | KB5131087 | 10.0.22631.7711 | Yes |
| Windows 11 Version 23H2 for ARM64-based Systems | KB5131087 | 10.0.22631.7711 | Yes |
Windows 10
| Product | Security update | Fixed build | Restart required |
|---|---|---|---|
| Windows 10 Version 22H2 for x64-based Systems | KB5131096 | 10.0.19045.7846 | Yes |
| Windows 10 Version 22H2 for ARM64-based Systems | KB5131096 | 10.0.19045.7846 | Yes |
| Windows 10 Version 22H2 for 32-bit Systems | KB5131096 | 10.0.19045.7846 | Yes |
| Windows 10 Version 21H2 for x64-based Systems | KB5131096 | 10.0.19044.7846 | Yes |
| Windows 10 Version 21H2 for ARM64-based Systems | KB5131096 | 10.0.19044.7846 | Yes |
| Windows 10 Version 21H2 for 32-bit Systems | KB5131096 | 10.0.19044.7846 | Yes |
| Windows 10 Version 1809 for x64-based Systems | KB5131085 | 10.0.17763.9487 | Yes |
| Windows 10 Version 1809 for 32-bit Systems | KB5131085 | 10.0.17763.9487 | Yes |
| Windows 10 Version 1607 for x64-based Systems | KB5131291 | 10.0.14393.9688 | Yes |
| Windows 10 Version 1607 for 32-bit Systems | KB5131291 | 10.0.14393.9688 | Yes |
Windows Server
| Product | Security update | Fixed build | Restart required |
|---|---|---|---|
| Windows Server 2025 | KB5131080 KB5131077 | 10.0.26100.33822 10.0.26100.33730 | Yes No |
| Windows Server 2025 (Server Core installation) | KB5131080 KB5131077 | 10.0.26100.33822 10.0.26100.33730 | Yes No |
| Windows Server 2022 | KB5131090 | 10.0.20348.5870 | Yes |
| Windows Server 2022 (Server Core installation) | KB5131090 | 10.0.20348.5870 | Yes |
| Windows Server 2019 | KB5131085 | 10.0.17763.9487 | Yes |
| Windows Server 2019 (Server Core installation) | KB5131085 | 10.0.17763.9487 | Yes |
| Windows Server 2016 (Server Core installation) | KB5131291 | 10.0.14393.9688 | Yes |
| Windows Server 2016 | KB5131291 | 10.0.14393.9688 | Yes |
Microsoft Office for Android
| Product | Security update | Fixed build | Restart required |
|---|---|---|---|
| Microsoft Office for Android | Release Notes | 16.0.20625.20014 | Not stated |
For Office for Android, Microsoft links its Microsoft 365 release notes instead of a KB article and does not state a restart requirement.
Known attacks
Microsoft lists CVE-2026-121680 as not publicly disclosed and not known to be exploited. The CVE is not in the CISA Known Exploited Vulnerabilities (KEV) catalog, version 2026.11.13. Absence from KEV does not prove that no attacks have happened. CISA's SSVC assessment in the NVD record, dated 2026-11-11, lists "automatable: yes" and "technical impact: partial".
Terms explained
- NTLM: a Microsoft challenge-response authentication protocol used by Windows, often as a fallback when Kerberos is not available.
- NTLMv2 hash (Net-NTLMv2): the value a Windows client sends to prove a user's identity during NTLM authentication. It is derived from the user's password.
- Relay: forwarding captured authentication data to another service, so the attacker is accepted there as the victim.
- Spoofing: Microsoft's impact category for an attacker pretending to be another user or system.
- CWE-522, Insufficiently Protected Credentials: the product sends or stores credentials in a way that lets others intercept or retrieve them.
- CVSS 3.1 vector:
- AV:N (Attack Vector: Network): the attack works over a network.
- AC:L (Attack Complexity: Low): no special conditions are needed.
- PR:N (Privileges Required: None): the attacker needs no account.
- UI:N (User Interaction: None): the score assumes no user action is needed.
- S:U (Scope: Unchanged): the impact stays within the affected component.
- C:H (Confidentiality: High): sensitive data, here the NTLMv2 hash, is disclosed.
- I:N and A:N (Integrity and Availability: None): no direct effect on data integrity or system availability.
- E:U (Exploit Code Maturity: Unproven): no known working attack code.
- RL:O (Remediation Level: Official Fix): the vendor has released a fix.
- RC:C (Report Confidence: Confirmed): the vendor has confirmed the vulnerability.
- SSVC: Stakeholder-Specific Vulnerability Categorization, a decision model CISA uses alongside CVSS.
What This Means for IT Teams
Every Windows version in Microsoft's table is affected, from Windows 10 Version 1607 and Windows Server 2016 to Windows 11 Version 26H2 and Windows Server 2025. Server Core installations are included. Office for Android is affected below build 16.0.20625.20014.
To check exposure, compare each device's Windows build number with the fixed build in the tables. Install the listed November 2026 update. Most of the listed updates require a restart. Microsoft lists no workaround or mitigation in the advisory.
The score assumes network access with no privileges and no user interaction. Microsoft does not know of any attacks, and the CVE is not in the KEV catalog. Confirming build levels across all workstations and servers is a routine patch management task.
NVD cross-check
The NVD record (status: Awaiting Analysis) was published on 2026-11-10 and last modified on 2026-11-13. NVD shows the same description and the same CVSS 3.1 base vector and score, 7.5 HIGH, supplied by Microsoft as a secondary source. NVD has not published its own score. NVD lists CWE-522, as Microsoft does.
NVD's affected-version ranges match the first fixed build Microsoft lists for each product, including Office for Android below 16.0.20625.20014. NVD does not repeat the second update and fixed build that Microsoft lists for some products. NVD lists Windows Server 2022 for x64-based systems only, without naming its Server Core installation separately.
Related coverage
Networking Pulse also covered another Windows flaw from the same release: Windows Remote Access API privilege flaw CVE-2026-119853.


