COCKPIT-STORAGED · CVE-2026-125672 · Other
NO FIX YET
Cockpit's storage module passes a Tang keyserver address from a LUKS/clevis header to curl without a separator, so an address starting with a dash is read as a curl option. An attacker who can attach a crafted encrypted device can get an admin user to trigger arbitrary file read or write as that Cockpit session user.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Systems running Cockpit with the storage module (cockpit-storaged) that manage LUKS devices with Tang/clevis bindings. The exposure needs a crafted device to be attached and an administrator to edit its Tang settings in the Cockpit UI. Hosts without cockpit-storaged or without clevis-bound LUKS devices can skip it.
Not affected if no-clevis-luks, no-cockpit-storaged
Who cares clevis, cockpit, cockpit-storaged, linux, luks, tang
Unknown from the sources.
No fix yet, per the sources.
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.
This page as .md · .json · CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.