LiveActive security incident?Get immediate response
CVE Record

CVE-2025-21213: Secure Boot Security Feature Bypass Vulnerability

Secure Boot Security Feature Bypass Vulnerability

MediumCVSS 4.6Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2025-21213 is a Microsoft Secure Boot security feature bypass. An attacker with physical access could bypass a boot-time protection and gain access to confidential data. Microsoft rates it medium severity and lists official remediation as available. There is no provided evidence of active exploitation.

Executive priority

Schedule remediation through standard Windows patching, with faster handling for devices at higher physical-access risk. This is not a top emergency based on available evidence, but it weakens a foundational boot security control and should not be deferred indefinitely.

Technical view

The CVSS 3.1 vector is 4.6: AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. The issue is mapped to CWE-284 and affects multiple supported Windows client and server versions. The impact is confidentiality only, with no integrity or availability impact stated in the provided data.

Likely exposure

Exposure is mainly Windows endpoints and servers in the listed affected versions where Secure Boot protections matter and updates have not been applied. The physical-access requirement lowers broad remote risk but raises concern for laptops, kiosks, labs, branch offices, and less-controlled server rooms.

Exploitation context

The source data indicates physical access is required, with low attack complexity, no privileges, and no user interaction. CISA KEV status is false in the bundle, and no cited source claims active exploitation. Treat this as a local physical-access risk, not an internet-exposed remote vulnerability.

Researcher notes

Evidence is limited to the CVE record, CVE List data, and Microsoft advisory metadata. The bundle does not include technical root cause details, proof-of-concept status, or specific KB numbers. Avoid assuming exploitability beyond the CVSS physical-access model and Microsoft’s security feature bypass classification.

Mitigation direction

  • Apply Microsoft updates for CVE-2025-21213 from the MSRC guidance.
  • Prioritize mobile, shared, kiosk, and physically accessible systems.
  • Confirm affected Windows versions are covered by normal patch management.
  • Review Microsoft’s advisory for any product-specific update details.

Validation and detection

  • Inventory Windows versions listed in the advisory.
  • Check patch compliance against Microsoft guidance for CVE-2025-21213.
  • Verify Secure Boot is enabled where required by policy.
  • Confirm no high-risk devices remain unpatched after deployment.
Prepared
Confidence
high
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-2025-21213 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
Medium
CVSS
4.6 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N/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: partial

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
4.6CVSS 3.1MediumCVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N/E:U/RL:O/RC:C0.93.6microsoft

Vulnerability scoring details

Base CVSS 3.1 score

4.6Medium
CVSS 3.1 vector shape for CVE-2025-21213Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N/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 150710.0.10240.0Listed
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 22H210.0.22621.0Listed
MicrosoftWindows 11 version 22H310.0.22631.0Listed
MicrosoftWindows 11 Version 23H210.0.22631.0Listed
MicrosoftWindows 11 Version 24H210.0.26100.0Listed
MicrosoftWindows Server 20126.2.9200.0Listed
MicrosoftWindows Server 2012 (Server Core installation)6.2.9200.0Listed
MicrosoftWindows Server 2012 R26.3.9600.0Listed
MicrosoftWindows Server 2012 R2 (Server Core installation)6.3.9600.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.