Security readout for executives and security teams
Plain-English summary
This is a critical Microsoft Windows NTLMv1 privilege-escalation vulnerability. The provided sources identify affected Windows 11 24H2 and Windows Server 2022/2025 builds. Microsoft published an advisory with a patch reference. No provided source says it is being actively exploited.
Executive priority
Treat as urgent patching for affected Windows estates because the score is critical and the attack vector is network-based with no user interaction required.
Technical view
CVE-2025-21311 is a CWE-303 issue in Windows NTLMv1 with CVSS 3.1 score 9.8. The vector is network-accessible, low complexity, requires no privileges or user interaction, and rates confidentiality, integrity, and availability impact as high. The bundle does not describe exploit mechanics.
Likely exposure
Exposure is limited by the bundle to listed Microsoft Windows 11 Version 24H2, Windows Server 2022 23H2 Server Core, Windows Server 2025, and Windows Server 2025 Server Core builds.
Exploitation context
The bundle marks CISA KEV status as false and CVSS exploit maturity as unproven. Treat active exploitation as unconfirmed from these sources, not absent in the wild.
Researcher notes
Evidence is sparse. The public bundle provides severity, affected products, CWE-303, CVSS vector, KEV false, and MSRC patch reference, but not root-cause detail or exploitation procedure.
Mitigation direction
Apply the Microsoft update referenced by the MSRC advisory.
Prioritize internet-facing, authentication, and server workloads running listed affected builds.
Check MSRC guidance before changing NTLMv1 configuration or applying compensating controls.
Track vendor advisory updates for revised affected versions or operational mitigations.
Validation and detection
Inventory Windows assets for the exact affected products and builds listed.
Confirm the applicable Microsoft security update is installed on affected systems.
Review authentication logs for unusual NTLMv1-related activity without assuming exploitation.
Document exceptions and revisit them when Microsoft updates the advisory.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-303: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-303 · source CWE mapping
Incorrect Implementation of Authentication Algorithm
Incorrect Implementation of Authentication Algorithm represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.