# CVE-2026-92747: Cockpit-machines: cockpit-machines: sensitive data exposure of guest credentials via json argument in process list

> Local attackers can expose sensitive VM credentials by inspecting process lists during installation, requiring a patch to Cockpit-machines.

- **Severity:** Medium 5.0 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 18 Sep 2026
- **Updated:** 21 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-92747, GHSA-8p9r-6652-9xc4, UBUNTU-CVE-2026-92747

## What is CVE-2026-92747?

CVE-2026-92747 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 18 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A flaw was found in `cockpit-machines`. This vulnerability allows a local attacker with the ability to inspect running processes to expose sensitive guest virtual machine (VM) credentials, such as `rootPassword` and `userPassword`. This occurs when the `install_machine.py` script passes these credentials as a JSON command-line argument during VM creation or installation. The exposure is limited to the period when the installation workflow is active and depends on host process-visibility policies.

Weakness: CWE-214 (Invocation of Process Using Visible Sensitive Information)

## Which versions are affected by CVE-2026-92747?


## How do I fix CVE-2026-92747?

Apply the vendor's patch.

## Is CVE-2026-92747 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92747 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-92747 and fix it if it is affected.

What it is: CVE-2026-92747 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 18 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92747 exists.

Affected product: Red Hat Enterprise Linux 10. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-92747/ (Markdown: https://insights.sbomify.com/CVE-2026-92747/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-92747
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-92747
- OSV: https://osv.dev/vulnerability/CVE-2026-92747

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-92747/
Summaries are generated and may contain mistakes; the official description above is the record.