LiveActive security incident?Get immediate response
CVE Record

CVE-2026-21255: Windows Hyper-V Security Feature Bypass Vulnerability

Improper access control in Windows Hyper-V allows an authorized attacker to bypass a security feature locally.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A user who already has authorized local access to an affected Windows system may bypass a Hyper-V security boundary. Successful exploitation could compromise confidentiality, integrity, and availability beyond the attacker’s original security scope. This is serious, but it is not described as remotely exploitable or requiring no prior access.

Executive priority

Treat as a high-priority patching and access-control issue, especially on Hyper-V systems with multiple local users. It does not justify emergency remote-exploitation assumptions, but its potential cross-boundary impact and high confidentiality, integrity, and availability consequences warrant prompt remediation and documented verification.

Technical view

CVE-2026-21255 is a CWE-284 improper-access-control flaw in Windows Hyper-V. Its CVSS 3.1 score is 8.8: local access, low complexity, low privileges, no user interaction, changed scope, and high confidentiality, integrity, and availability impacts. The supplied evidence does not identify the bypassed feature or affected component internals.

Likely exposure

Potential exposure spans the listed Windows 10, Windows 11, and Windows Server builds from 2016 through 2025 and specified later releases. Risk is most relevant where Hyper-V is enabled and authorized local access is available. The bundle does not establish exact configuration prerequisites, so asset matching should be confirmed against Microsoft’s advisory.

Exploitation context

The attacker must already be authorized locally and hold low privileges; no user interaction is required. The CVSS exploit-maturity value is unproven, and the CVE is not listed as KEV in the supplied bundle. Therefore, active exploitation is not supported by the available evidence.

Researcher notes

The supplied record provides no technical component, bypass mechanism, public proof of concept, attack observations, workaround, or specific update identifier. The affected list also contains duplicated Windows 11 26H1 entries and an unusual 22H3 label. Confirm product naming, applicability, and remediation directly in Microsoft’s current advisory.

Mitigation direction

  • Review Microsoft’s CVE advisory and apply its associated security updates promptly.
  • Prioritize affected systems using Hyper-V or permitting broadly assigned local access.
  • Restrict local accounts and administrative access to necessary, trusted users.
  • If updates cannot be applied, check Microsoft guidance for supported mitigations or workarounds.

Validation and detection

  • Inventory listed Windows editions and compare their builds with Microsoft’s affected-product table.
  • Identify systems where Hyper-V is installed or enabled.
  • Verify the Microsoft security update associated with CVE-2026-21255 is installed.
  • Review local account assignments and recent unauthorized access indicators.
  • Recheck Microsoft’s advisory for revisions, prerequisites, and superseding updates.
Prepared
Confidence
medium
Sources
3

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 · medium confidence lookup

CWE-284: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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 lookup
cve · low confidence lookup

CVE-2026-21255 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H/E:U/RL:O/RC:C

Official CVE source material

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.

1CVSS vectors
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical 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.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H/E:U/RL:O/RC:C26microsoft

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2026-21255Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H/E:U/RL:O/RC:C

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MicrosoftWindows 10 Version 160710.0.14393.0Listed
MicrosoftWindows 10 Version 180910.0.17763.0Listed
MicrosoftWindows 10 Version 21H210.0.19044.0Listed
MicrosoftWindows 10 Version 22H210.0.19045.0Listed
MicrosoftWindows 11 version 22H310.0.22631.0Listed
MicrosoftWindows 11 Version 23H210.0.22631.0Listed
MicrosoftWindows 11 Version 24H210.0.26100.0Listed
MicrosoftWindows 11 Version 25H210.0.26200.0Listed
MicrosoftWindows 11 version 26H110.0.28000.0Listed
MicrosoftWindows 11 Version 26H110.0.28000.0Listed
MicrosoftWindows Server 201610.0.14393.0Listed
MicrosoftWindows Server 2016 (Server Core installation)10.0.14393.0Listed
MicrosoftWindows Server 201910.0.17763.0Listed
MicrosoftWindows Server 2019 (Server Core installation)10.0.17763.0Listed
MicrosoftWindows Server 202210.0.20348.0Listed
MicrosoftWindows Server 2022, 23H2 Edition (Server Core installation)10.0.25398.0Listed
MicrosoftWindows Server 202510.0.26100.0Listed
MicrosoftWindows Server 2025 (Server Core installation)10.0.26100.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-284 · source CWE mapping

Improper Access Control

Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.