VulnerabilityPublished 12 Nov 2026Updated 13 Nov 2026

CVE-2026-125672: cockpit-storaged

Affects cockpitSource GCVE Database

Compare

Authoritative record:CVE-2026-125672· Medium 6.6

Not known to be exploited · CVSS 6.6 Medium.

Data as of 13 Nov 2026, 22:33 UTC

CVSS 3.1 base score

6.6Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (redhat)	CVSS 3.1	6.6

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Ubuntu 26.10cockpit`pkg:deb/ubuntu/cockpit?arch=source&distro=stonking`Other threats	Affected 360-1 – 367-1 4 affected builds	Fixed in–
Ubuntu 26.04 LTScockpit`pkg:deb/ubuntu/cockpit?arch=source&distro=resolute`Other threats	Affected 346-1 – 360-1 9 affected builds	Fixed in–
Ubuntu 24.04 LTScockpit`pkg:deb/ubuntu/cockpit?arch=source&distro=noble`Other threats	Affected 300.1-1 – 314-1 12 affected builds	Fixed in–
Ubuntu 22.04 LTScockpit`pkg:deb/ubuntu/cockpit?arch=source&distro=jammy`Other threats	Affected 252-1 – 264-1ubuntu0.22.04.1 11 affected builds	Fixed in–
Ubuntu 20.04 LTScockpit`pkg:deb/ubuntu/cockpit?arch=source&distro=focal`Other threats	Affected 202.1-1 – 215-1 11 affected builds	Fixed in–
Ubuntu 18.04 LTScockpit`pkg:deb/ubuntu/cockpit?arch=source&distro=bionic`Other threats	Affected 151-1 – 164-1 9 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

There is no complete mitigation without a code fix. Administrators should restrict local interactive console or desktop login access on hosts running Cockpit's Storage module to trusted users only. Additionally, they should carefully verify the Tang keyserver address in the "Edit Tang keyserver" dialog before saving; any value that does not resemble a well-formed hostname, especially those starting with a hyphen, should be rejected. Monitor Red Hat advisories for an official patch.

Description

A vulnerability in cockpit-storaged allows a local unprivileged user with console or desktop access to craft a malicious LUKS/clevis block device that triggers curl option injection when an administratively-privileged Cockpit user edits Tang keyserver settings. This can lead to arbitrary file read or write as the Cockpit session user. Exploitation requires both local device attachment and privileged Cockpit interaction. No non-default configuration is needed. There is no complete mitigation without a code fix; partial mitigation involves restricting local interactive access and careful validation of Tang keyserver addresses.

Impact

The vulnerability allows local unprivileged users with console or desktop login access to cause an administratively-privileged Cockpit user to execute curl with injected options, leading to arbitrary file read or write as the Cockpit session user. This compromises confidentiality and integrity of data accessible to the Cockpit user. The attack requires local device attachment and privileged user interaction, limiting remote exploitation. Availability is not impacted.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 13 Nov 2026, 22:33 UTC

Technical details

References

Community reviews

Related threats