CVE-2025-1118 | Grub2: commands/dump: the dump command is not in lockdown when secure boot is enabled

A flaw was found in grub2. Grub's dump command is not blocked when grub is in lockdown mode, which allows the user to read any memory information, and an attacker may leverage this in order to extract signatures, salts, and other sensitive information from the memory.

Published: 2025-02-19 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-1118 is rated Low Risk (24.9/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.29%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-1118

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.02% 0.29% +0.27%
2 2026-03-30 0.06% 0.02% -0.04%
3 2026-03-25 — 0.06% —

Full EPSS history (6 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-1118

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.4 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 0.8 3.6 [email protected]

Weakness enumeration for CVE-2025-1118

OS Trackers for CVE-2025-1118

vendor priority summary link
debian not yet assigned CVE-2025-1118 not yet assigned priority: Debian including 1 source packages (grub2), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 4, open 1. https://security-tracker.debian.org/tracker/CVE-2025-1118
redhat medium — https://access.redhat.com/security/cve/CVE-2025-1118
suse medium CVE-2025-1118 severity moderate: SUSE including 376 source package names (2.0.4-5.8.146:grub2-2.06-150500.29.43.2, 2.0.4-5.8.146:grub2-i386-pc-2.06-150500.29.43.2, …), 1407 product×package rows across 291 product lines (Container suse/manager/5.0/x86_64/server, Container suse/sl-micro/6.0/base-os-container, … (291 product lines)): Fixed 1186, Known Affected 221. https://www.suse.com/security/cve/CVE-2025-1118/
ubuntu medium CVE-2025-1118 medium priority: Ubuntu including 3 source packages (grub2, grub2-signed, grub2-unsigned), 29 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): needs-triage 15, not-affected 8, ignored 6. https://ubuntu.com/security/CVE-2025-1118

Affected software / configurations for CVE-2025-1118

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-1118

cvelogic Threat Intelligence