CVSS 3.1
6.4 mediumCVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:HMedium (6.4) in gnu grub2. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:HExplain CVE-2026-97876 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-97876?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-97876?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-97876 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| GNU grub2 | from 2.12 before 2.16 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 13 | grub2 | no fix listed | DEBIAN-CVE-2026-97876 |
| Debian | 14 | grub2 | 2.14-4 | DEBIAN-CVE-2026-97876 |
| Ubuntu | 16.04:LTS, 18.04:LTS, 20.04:LTS and 4 more | grub2-signed, grub2-unsigned | no fix listed | UBUNTU-CVE-2026-97876 |
| Ubuntu | Pro:14.04:LTS | grub2, grub2-signed | no fix listed | UBUNTU-CVE-2026-97876 |
| Alpaquita | 23 | grub | 2.12-r9 | BELL-CVE-2026-97876 |
| Alpaquita | 25 | grub | 2.12-r12 | BELL-CVE-2026-97876 |
| Alpaquita | stream | grub | 2.14-r2 | BELL-CVE-2026-97876 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpaquita.
Red Hat rates this Moderate.
There is no complete mitigation for this issue other than applying a fixed GRUB build; the underlying fix requires validating the UART/MMIO resource used by the serial command and making the module-verification path fail closed when the verifier list is empty under lockdown.
Until a fixed build is available, exposure can be reduced by:
- Restricting who can modify or supply GRUB boot configuration (grub.cfg) and disallowing untrusted or attacker-controlled removable boot media.
- Avoiding use of the serial console/terminal_input during boot on systems relying on Secure Boot lockdown, where serial input is not otherwise required.
- Treating administrator-level control over boot configuration as equivalent to the ability to bypass lockdown module verification on affected GRUB builds, and applying the same access controls accordingly.
These steps reduce the attack surface but do not close the underlying validation flaw; they do not help if the attacker already controls boot configuration or removable boot media.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | grub2 | Fix deferred | |
| Red Hat Enterprise Linux 7 | grub2 | Fix deferred | |
| Red Hat Enterprise Linux 8 | grub2 | Fix deferred | |
| Red Hat Enterprise Linux 9 | grub2 | Fix deferred | |
| Red Hat OpenShift Container Platform 4 | openshift/ose-rhel-coreos-8 | Fix deferred | |
| Red Hat OpenShift Container Platform 4 | openshift/ose-rhel-coreos-9 | Fix deferred | |
| Red Hat OpenShift Container Platform 5 | openshift/ose-rhel-coreos-9 | Fix deferred |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-97876.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.