# CVE-2026-125672: A flaw was found in cockpit-storaged.


- **Severity:** Medium 6.6 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 10 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-7vw6-56j5-6r97, UBUNTU-CVE-2026-125672

## What is CVE-2026-125672?

CVE-2026-125672 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 10 Nov 2026. 

### Official description

A flaw was found in cockpit-storaged. A Tang keyserver address read from a clevis token in a LUKS header is concatenated into curl's argument vector without a "--" separator. An address beginning with "-" is parsed by curl as an option instead of a hostname, allowing an attacker who can attach a crafted LUKS/clevis block device (for example, a local unprivileged user with an active console or desktop login session) to have an administratively-privileged Cockpit user unknowingly trigger curl option injection when editing the device's Tang keyserver settings. This can lead to arbitrary file read or write as the Cockpit session user.

Weakness: CWE-88 (Improper Neutralization of Argument Delimiters in a Command)

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


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

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

## Is CVE-2026-125672 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-125672 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 10 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-125672 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-2026-125672/ (Markdown: https://insights.sbomify.com/CVE-2026-125672/index.md)
```

## Sources

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

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