Skip to main content
CVE-2025-2296VulnerabilityPublished

CVE-2025-2296: TianoCore EDK2 · Improper Input Validation

Affects TianoCore EDK2Source CVE Database V5

0

Not known to be exploited · CVSS 8.4 High.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 4.0 base score
8.4High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 55% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:H/VA:L/SC:L/SI:H/SA:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubtianocore/edk2pkg:github/tianocore/edk2Other threatsAffected
  • =0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Restrict physical and local access to systems running EDK2 firmware to trusted personnel only, employing strong access controls and monitoring. 2. Enforce strict privilege management policies to minimize the number of users with high-level local privileges capable of exploiting this vulnerability. 3. Implement firmware integrity monitoring solutions that can detect unauthorized changes or anomalies in BIOS behavior. 4. Prepare for rapid deployment of official patches or firmware updates from TianoCore or hardware vendors once released; establish a firmware update testing and rollout process. 5. Use hardware-based security features such as TPM and Secure Boot to limit unauthorized firmware modifications and detect tampering. 6. Conduct regular audits and penetration testing focusing on firmware and local privilege escalation vectors. 7. Educate IT staff and security teams about the risks of firmware vulnerabilities and the importance of layered security controls. 8. Maintain up-to-date asset inventories to identify all systems running EDK2 firmware to prioritize mitigation efforts. 9. Consider network segmentation to isolate critical systems and reduce the risk of lateral movement by attackers with local access. 10. Collaborate with hardware vendors and security communities to share intelligence and best practices related to firmware security.

Description

EDK2 contains a vulnerability in BIOS where an attacker may cause “ Improper Input Validation” by local access. Successful exploitation of this vulnerability could alter control flow in unexpected ways, potentially allowing arbitrary command execution and impacting Confidentiality, Integrity, and Availability.

References

Community reviews

Loading reviews…