# CVE-2026-25828: Command injection in n/a

> An attacker can execute arbitrary commands via unsanitized input in grub-btrfs, potentially compromising the system during initramfs execution.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Feb 2026
- **Updated:** 4 Mar 2026
- **Also known as:** GHSA-2fcc-cgw7-6rrw

## What is CVE-2026-25828?

CVE-2026-25828 is a medium-severity command injection vulnerability in n/a, published on 12 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

grub-btrfs through 2026-01-31 (on Arch Linux and derivative distributions) allows initramfs OS command injection because it does not sanitize the $root parameter to resolve_device(). NOTE: a third party reports "exploitation may not be feasible under normal conditions and may depend on specific implementation details within resolve_device."

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-25828?


## How do I fix CVE-2026-25828?

No fix has been published for CVE-2026-25828 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-25828 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-25828 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-25828 and fix it if it is affected.

What it is: CVE-2026-25828 is a medium-severity command injection vulnerability in n/a, published on 12 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-25828 exists.

Affected product: n/a. 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-2026-25828/ (Markdown: https://insights.sbomify.com/CVE-2026-25828/index.md)
```

## Sources

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

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