CVSS 3.1
6.6 mediumCVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:NCVE-2026-125672
Medium (6.6) in red hat.
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.
Severity
- CWE
- CWE-88 Improper Neutralization of Argument Delimiters in a Command (Argument Injection)
- OWASP Top 10
- A05:2025 Injection
- Published
- Modified
- Assigned by
- redhat (CNA)
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-125672 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-125672?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-125672?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-125672 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
- red hat:red hat enterprise linux 10
- red hat:red hat enterprise linux 6
- red hat:red hat enterprise linux 7
- red hat:red hat enterprise linux 8
- red hat:red hat enterprise linux 9
Attack patterns (CAPEC)
- CAPEC-41 Using Meta-characters in E-mail Headers to Inject Malicious Payloads Likelihood: High · Severity: High
- CAPEC-88 OS Command Injection Likelihood: High · Severity: High
- CAPEC-137 Parameter Injection Likelihood: Medium · Severity: Medium
- CAPEC-174 Flash Parameter Injection Likelihood: High · Severity: Medium
- CAPEC-460 HTTP Parameter Pollution (HPP) Severity: Medium
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.