Security readout for executives and security teams
Plain-English summary
This vulnerability can let an already highly privileged local attacker bypass Windows Secure Boot protections. A successful bypass could undermine trust in the startup process and expose sensitive systems to confidentiality, integrity, and availability impacts. It is important, but the required authorized local access reduces immediate risk compared with remotely exploitable flaws.
Executive priority
Schedule prompt remediation through the normal security-update process, accelerating high-value systems and devices with broadly assigned local administrators. This is not an emergency remote compromise scenario based on supplied evidence, but a Secure Boot bypass could materially weaken platform trust after privileged access is obtained.
Technical view
Windows Secure Boot relies on a component that cannot be updated, creating a security-feature bypass classified as CWE-1329. CVSS 3.1 rates it 6.7: local access, low complexity, high privileges, no user interaction, unchanged scope, and potentially high confidentiality, integrity, and availability impact.
Likely exposure
Exposure includes the listed Windows 10, Windows 11, Windows Server 2019, 2022, 2025, and specified Server Core releases. Actual exposure depends on affected build presence and Microsoft update applicability. The supplied sources do not establish whether Secure Boot configuration changes exploitability.
Exploitation context
The attacker must already be authorized locally with high privileges. No user interaction is required, and attack complexity is rated low. The source bundle marks this CVE as absent from KEV and provides no other evidence of active exploitation or public exploit availability.
Researcher notes
The key weakness is reliance on a non-updateable Secure Boot component. The source bundle does not describe the component, bypass mechanism, affected firmware conditions, indicators, or update prerequisites. Researchers should use Microsoft's advisory for authoritative applicability and remediation details and should not infer active exploitation from the CVSS environmental metrics.
Mitigation direction
- Review Microsoft's CVE advisory for applicable security updates and deployment requirements.
- Prioritize affected privileged workstations, administrative endpoints, servers, and other high-value systems.
- Deploy the vendor-provided update through established change and recovery procedures.
- Restrict local administrative access while remediation is pending.
- Monitor Microsoft guidance for prerequisite, firmware, or Secure Boot servicing instructions.
Validation and detection
- Inventory listed Windows editions and compare operating-system builds with Microsoft's applicability guidance.
- Confirm the applicable Microsoft security update is installed successfully on affected systems.
- Verify update compliance centrally and investigate failed, deferred, or excluded devices.
- Retest Secure Boot health after updating without attempting bypass techniques.
- Confirm privileged access is limited and monitored on systems awaiting remediation.
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-1329: 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 lookupCVE-2026-41097 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
- Medium
- CVSS
- 6.7 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/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:H/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C0.85.9microsoftVulnerability scoring details
Base CVSS 3.1 score
6.7MediumVector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/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
- Secure Boot Security Feature Bypass 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.
Reliance on Component That is Not Updateable
Reliance on Component That is Not Updateable represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.