VulnerabilityPublished 18 Sep 2026Updated 17 Oct 2026

CVE-2026-92745: cockpit-machines

Affects cockpit-machinesSource GCVE Database

Compare

Authoritative record:CVE-2026-92745· Medium 5.0

Not known to be exploited · CVSS 5.0 Medium.

Data as of 6 Nov 2026, 23:24 UTC

CVSS 3.1 base score

5.0Medium

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

EPSS: 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: None
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: None: There is no loss of integrity within 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 18 Sep 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 7 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-machines`pkg:deb/ubuntu/cockpit-machines?arch=source&distro=stonking`Other threats	Affected 351-1 – 356-1 5 affected builds	Fixed in–
Ubuntu 26.04 LTScockpit-machines`pkg:deb/ubuntu/cockpit-machines?arch=source&distro=resolute`Other threats	Affected 339-1 – 351-1 8 affected builds	Fixed in–
Ubuntu 24.04 LTScockpit-machines`pkg:deb/ubuntu/cockpit-machines?arch=source&distro=noble`Other threats	Affected 299-1 – 310-1 10 affected builds	Fixed in–
Ubuntu 22.04 LTScockpit-machines`pkg:deb/ubuntu/cockpit-machines?arch=source&distro=jammy`Other threats	Affected 251-1 – 265-1 12 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

Until fixed packages are installed, avoid validating RHSM offline tokens through the Cockpit Machines 'Download an OS' or RHEL image download flow on multi-user hosts where untrusted local users can inspect process metadata. As a system-level mitigation, restrict /proc visibility by remounting /proc with the hidepid=2 mount option to prevent unprivileged users from reading other users' process command lines. Updating to the fixed cockpit-machines package once it is available resolves the issue.

Description

A local information disclosure vulnerability exists in cockpit-machines that allows a local attacker to disclose a sensitive Red Hat Subscription Management (RHSM) offline token. The token is exposed via process command-line arguments during token validation, potentially compromising confidentiality by enabling unauthorized access token requests. Exploitation requires local access and the ability to inspect process metadata on systems without restrictive /proc visibility settings. Mitigations include avoiding token validation on multi-user hosts with untrusted users and restricting /proc visibility. Fixed packages are being released to address this issue.

Impact

The vulnerability allows local attackers to disclose sensitive RHSM offline tokens by inspecting process metadata, leading to a confidentiality breach. The exposed token can be used to request access tokens, potentially granting unauthorized access to subscription management services. There is no impact on integrity or availability. Exploitation requires local access and low privileges but user interaction is required to trigger the validation flow.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Nov 2026, 09:58 UTC

Technical details

References

Community reviews

Related threats