CVE-2026-0940: Lenovo ThinkPad T14 Gen 5 BIOS · Improper Initialization
Affects Lenovo ThinkPad T14 Gen 5 BIOSSource CVE Database V5
Not known to be exploited · CVSS 8.4 High.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 11 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LenovoThinkPad T14 Gen 5 BIOS | Affected
| Fixed in– |
| LenovoThinkPad P14s Gen 5 BIOS | Affected
| Fixed in– |
| LenovoThinkPad Z13 Gen 2 BIOS | Affected
| Fixed in– |
| LenovoThinkPad Z16 Gen 2 BIOS | Affected
| Fixed in– |
| LenovoThinkPad P16v Gen 1 BIOS | Affected
| Fixed in– |
| LenovoThinkPad P15v Gen 3 BIOS | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2026-0940, organizations should implement the following specific measures: 1) Monitor Lenovo security advisories closely and apply BIOS firmware updates immediately upon release to address the improper initialization flaw. 2) Restrict local privileged access strictly to trusted administrators and enforce the principle of least privilege to reduce the risk of exploitation by insiders or malware with elevated rights. 3) Employ endpoint detection and response (EDR) solutions capable of monitoring BIOS-level changes or suspicious firmware activity. 4) Use hardware-based security features such as Trusted Platform Module (TPM) and BIOS write protections to prevent unauthorized firmware modifications. 5) Conduct regular audits of BIOS configurations and integrity checks using vendor tools or third-party firmware validation utilities. 6) Educate users and administrators about the risks of local privilege escalation and enforce strong authentication and physical security controls to prevent unauthorized device access. These targeted actions go beyond generic patching advice and focus on minimizing the attack surface and detecting potential exploitation attempts at the firmware level.
Description
A potential improper initialization vulnerability was reported in the BIOS of some ThinkPads that could allow a local privileged user to modify data and execute arbitrary code.