Skip to main content
Mallory
MediumVulnerability

CVE-2026-97015: Windows BitLocker Heap Buffer Overflow Secure Boot Bypass

Published Nov 10, 2026 · Updated 5 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days5 mentions · peak 3 in a dayToday
CVSS6.8Medium · v3.1
EPSS0.39%34th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Microsoft Corporation
IdentifiersCVE-2026-97015CWE-122 · Heap-based Buffer Overflow

CVE-2026-97015 is a heap-based buffer overflow in Windows BitLocker that allows an unauthenticated attacker with physical access to bypass Secure Boot. Exploitation requires no existing privileges or user interaction and has low attack complexity. Microsoft rates the vulnerability Important, with a CVSS v3.1 base score of 6.8. The specific vulnerable function and triggering input are not identified.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can bypass Secure Boot, undermining enforcement of boot-time security protections. The CVSS assessment assigns high potential impacts to confidentiality, integrity, and availability. Specific mechanisms for subsequent compromise are not identified.

Mitigation

If you can’t patch tonight, do this now.

Restrict unauthorized physical access to affected devices as an interim precaution. No vendor-provided workaround is identified.

Remediation

Patch, then assume compromise.

Apply the applicable Microsoft security update for CVE-2026-97015 from the November 10, 2026 release. An official fix is available; consult Microsoft's per-CVE guidance to identify the correct update for the installed Windows release and architecture. Specific update identifiers and fixed builds are not available here.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationWindows 10 1607operating_system
Microsoft CorporationWindows 10 1809operating_system
Microsoft CorporationWindows 10 21h2operating_system
Microsoft CorporationWindows 10 22h2operating_system
Microsoft CorporationWindows 11 23h2operating_system
Microsoft CorporationWindows 11 24h2operating_system
Microsoft CorporationWindows 11 25h2operating_system
Microsoft CorporationWindows 11 26h1operating_system
Microsoft CorporationWindows 11 Version 26H2 For Arm64-Based Systemsapplication
Microsoft CorporationWindows Server 2012operating_system
Microsoft CorporationWindows Server 2012 R2operating_system
Microsoft CorporationWindows Server 2016operating_system
Microsoft CorporationWindows Server 2019operating_system
Microsoft CorporationWindows Server 2022operating_system
Microsoft CorporationWindows Server 2025operating_system
FAQ

Frequently asked questions

Is CVE-2026-97015 exploited in the wild?
As of Nov 12, 2026, Mallory has no reports of CVE-2026-97015 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-97015?
As of Nov 12, 2026, Mallory has found no public exploit for CVE-2026-97015.
Is there a patch for CVE-2026-97015?
Apply the applicable Microsoft security update for CVE-2026-97015 from the November 10, 2026 release. An official fix is available; consult Microsoft's per-CVE guidance to identify the correct update for the installed Windows release and architecture.
What products are affected by CVE-2026-97015?
Microsoft Corporation Windows 10 1607, Microsoft Corporation Windows 10 1809, Microsoft Corporation Windows 10 21h2, Microsoft Corporation Windows 10 22h2, Microsoft Corporation Windows 11 23h2, and 10 more.
How severe is CVE-2026-97015?
CVE-2026-97015 has a CVSS v3.1 score of 6.8 (Medium) and an EPSS score of 0.39% (34th percentile) as of Nov 12, 2026.
Activity feed

Recent activity

5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
cryptika blogNews · Nov 11, 2026Windows BitLocker Vulnerabilities Allow Attackers to Bypass Security Feature | Cryptika CybersecurityA heap-based buffer overflow in Windows BitLocker that permits a security feature bypass by an attacker with physical access. No existing privileges or user interaction are required, and attack complexity is low. Microsoft rates it Important with a CVSS base score of 6.8. Its affected product list includes older Windows Server branches and is broader than that of CVE-2026-119832.Read more ↗cyber security newsNews · Nov 11, 2026Windows BitLocker Vulnerabilities Allow Attacker to Bypass Security FeatureAn Important-rated Windows BitLocker security feature bypass vulnerability caused by a heap-based buffer overflow, with a CVSS base score of 6.8. Exploitation requires physical access but no existing privileges or user interaction; attack complexity is low.Read more ↗ghsa syntheticNews · Nov 10, 2026GHSA-w67q-gpvv-jr3mA heap-based buffer overflow in Windows BitLocker permits an unauthorized attacker to bypass a security feature through a physical attack. The advisory does not specify the security feature bypassed or provide exploitation or remediation details.Read more ↗msrc microsoftNews · Nov 10, 2026CVE-2026-97015 - Security Update Guide - Microsoft - Windows BitLocker Security Feature Bypass VulnerabilityA heap-based buffer overflow in Windows BitLocker allows an attacker with physical access to bypass Secure Boot without prior privileges or user interaction. Microsoft rates the vulnerability Important, with a CVSS 3.1 base score of 6.8 and high confidentiality, integrity, and availability impacts. At original publication, Microsoft reported no exploitation, assessed exploitation as less likely, and indicated that an official fix was available.Read more ↗
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.