Local boot-trust bypass via vulnerable dependency
Published Sep 8, 2026 · Updated Sep 9, 2026
Security feature bypass in Microsoft Windows Secure Boot allows local users to undermine boot-code trust through a vulnerable dependency. Microsoft identifies the locus only as a vulnerable third-party component and has not disclosed the component, affected operation, or triggering input. Exploitation requires local high privileges and changes integrity of the Secure Boot trust decision, with no reported confidentiality loss or service interruption.
Summary
What happened
Security feature bypass in Microsoft Windows Secure Boot allows local users to undermine boot-code trust through a vulnerable dependency. Microsoft identifies the locus only as a vulnerable third-party component and has not disclosed the component, affected operation, or triggering input. Exploitation requires local high privileges and changes integrity of the Secure Boot trust decision, with no reported confidentiality loss or service interruption.
The record
- CVE
- CVE-2026-69713
- Published
- Sep 8, 2026
- Updated
- Sep 9, 2026
- Vendor
- Microsoft
- Product
- Windows Server 2019
- Classifications
- CWE-1395, T1542.003
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Sep 8, 2026CVE publishedPublication date reported by the CVE source.
- Sep 9, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=10.0.17763.0 <10.0.17763.9245
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo