Security readout for executives and security teams
Plain-English summary
This is a high-severity Windows Hyper-V vulnerability. Microsoft describes it as improper input validation that could let an authorized local attacker run code. The impact is serious because successful exploitation could affect confidentiality, integrity, and availability. The provided sources do not show active exploitation or CISA KEV listing.
Executive priority
Treat this as a priority patching item for Hyper-V-capable Windows systems, especially virtualization hosts. It is not shown as actively exploited in the provided evidence, but successful exploitation could have full confidentiality, integrity, and availability impact.
Technical view
CVE-2026-21247 affects multiple Windows client and server releases with Hyper-V. The CVSS 3.1 score is 7.3 with local attack vector, low complexity, low privileges, and required user interaction. Microsoft associates it with CWE-20, CWE-122, and CWE-125, indicating input validation and memory-safety concerns.
Likely exposure
Exposure is likely on affected Windows 10, Windows 11, and Windows Server systems where Hyper-V is present or relevant. The source bundle lists many supported client and server versions, including Server Core installations. Confirm exposure by matching OS versions and Microsoft update applicability.
Exploitation context
The source bundle says exploitation requires an authorized local attacker and user interaction. Exploit maturity is listed as unproven, and KEV is false. There is no source evidence here of active exploitation, public weaponization, or remote unauthenticated attack.
Researcher notes
The advisory data is internally important but limited. The title says remote code execution, while the CVSS vector and description indicate local attack conditions. Avoid classifying this as unauthenticated remote exploitation unless Microsoft or another cited source later supports that.
Mitigation direction
- Apply Microsoft’s update for CVE-2026-21247 on affected Windows releases.
- Prioritize Hyper-V hosts, virtualization infrastructure, and developer workstations using Hyper-V.
- Check MSRC guidance for release-specific update packages and prerequisites.
- Restrict unnecessary local access to systems where Hyper-V is installed or enabled.
- Track vendor updates for any revised affected-product or mitigation guidance.
Validation and detection
- Inventory Windows client and server versions against the affected list.
- Identify systems with Hyper-V installed, enabled, or operationally required.
- Verify the Microsoft update for CVE-2026-21247 is installed.
- Run authenticated vulnerability scans that check Microsoft patch state.
- Confirm no unsupported assumptions about active exploitation are used in risk reporting.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-122: 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.
Open ATT&CK lookupCWE-125: 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.
Open ATT&CK lookupCWE-20: 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.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-21247 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C1.35.9microsoftVulnerability scoring details
Base CVSS 3.1 score
7.3HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- Windows Hyper-V Remote Code Execution VulnerabilityCVE reference, microsoft · vendor-advisory, patch
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.