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

> An attacker with physical access can read sensitive memory data via the GRUB2 dump command even when Secure Boot lockdown is enabled.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Feb 2025
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-56904, AZL-57025, BELL-CVE-2025-1118, DEBIAN-CVE-2025-1118, GHSA-5r25-p9f2-w2xv, UBUNTU-CVE-2025-1118

## What is CVE-2025-1118?

CVE-2025-1118 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 19 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-501 (Trust Boundary Violation)

## Which versions are affected by CVE-2025-1118?


## How do I fix CVE-2025-1118?

Apply the vendor's patch.

## Is CVE-2025-1118 being exploited?

There is no known exploitation of CVE-2025-1118 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-1118 and fix it if it is affected.

What it is: CVE-2025-1118 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 19 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-1118 in the wild and no public exploit code.

Affected product: Red Hat Enterprise Linux 10. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-1118/ (Markdown: https://insights.sbomify.com/CVE-2025-1118/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-1118
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-1118
- OSV: https://osv.dev/vulnerability/CVE-2025-1118

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-1118/
Summaries are generated and may contain mistakes; the official description above is the record.