Secure Boot disablement via unchecked return value
Published Jan 14, 2026 · Updated Jan 14, 2026
Secure Boot state handling in affected Lenovo ThinkPad BIOS allows local users with privileged BIOS access to disable boot verification. Lenovo identifies an unchecked return value but has not published the affected routine or the operation whose result is ignored. The flaw is reachable only in User Mode when BIOS and operating-system status disagree, so the system can start code that Secure Boot would reject.
Summary
What happened
Secure Boot state handling in affected Lenovo ThinkPad BIOS allows local users with privileged BIOS access to disable boot verification. Lenovo identifies an unchecked return value but has not published the affected routine or the operation whose result is ignored. The flaw is reachable only in User Mode when BIOS and operating-system status disagree, so the system can start code that Secure Boot would reject.
The record
- CVE
- CVE-2026-0421
- Published
- Jan 14, 2026
- Updated
- Jan 14, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-252, T1562
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jan 14, 2026CVE publishedPublication date reported by the CVE source.
- Jan 14, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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