dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2025-2296

HIGH · 8.4 CVSS v4.0 Published 2025-12-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

EDK2 BIOS contains an improper input validation vulnerability that allows a local attacker to alter control flow in unexpected ways, potentially achieving arbitrary command execution with high privileges. This affects the foundational firmware layer of the system, impacting confidentiality, integrity, and availability.

MitigationApply vendor-supplied BIOS/firmware updates that address this vulnerability. Until patches are available, limit local physical access to affected systems and monitor for unauthorized firmware modifications.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if your system uses EDK2-based firmware
    Check your system information or BIOS setup to determine the firmware implementation. On Linux, run 'dmidecode -s bios-vendor' and 'dmidecode -s bios-version' to see the BIOS vendor and version. EDK2 is commonly used by Intel, AMD, and many OEM system manufacturers.
    Affected if The system uses an EDK2-based BIOS/UEFI implementation from an affected vendor without the security update applied.
  2. Determine the installed BIOS/UEFI version
    Run 'dmidecode -s bios-version' on Linux, 'wmic bios get smbiosbiosversion' on Windows, or access the BIOS setup screen during boot to view the current firmware version.
    Affected if Your installed version matches or precedes the unpatched version for your specific system model as defined by your hardware vendor's security advisory.
  3. Verify if local physical access is possible
    Assess whether unauthorized individuals can obtain physical access to the system, including console access, USB ports, or boot option manipulation capabilities.
    Affected if Physical or console access to the affected system is available to untrusted users, which is required to exploit this vulnerability.
  4. Check firmware integrity verification status
    Examine if your system has Secure Boot, measured boot, or firmware integrity verification enabled in the BIOS setup or via 'bootctl status' on Linux systems with systemd-boot.
    Affected if Firmware integrity verification mechanisms are disabled or not implemented, allowing potential firmware tampering.
  5. Review system event logs for firmware modifications
    Check BIOS event logs or UEFI event logs for any unexpected firmware modifications, failed integrity checks, or unusual boot events using 'journalctl -b' on Linux or Windows Event Viewer under System logs.
    Affected if Log entries indicate unauthorized firmware changes or integrity check failures that may suggest exploitation attempts.

Your system is affected if it runs an unpatched EDK2-based BIOS/UEFI firmware from a vendor that has not issued a security update for CVE-2025-2296, and an attacker can gain local physical access to the system.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied BIOS/firmware updates that address this vulnerability. Until patches are available, limit local physical access to affected systems and monitor for unauthorized firmware modifications.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-2296 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-2296 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data