# CVE-2026-113495: Cockpit-machines: rhsm access-token disclosure through image helper command-line arguments


- **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
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-113495, GHSA-rq8f-q9xv-wmhm, UBUNTU-CVE-2026-113495

## What is CVE-2026-113495?

CVE-2026-113495 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 20 Oct 2026. 

### Official description

A flaw was found in cockpit-machines. Red Hat Subscription Management (RHSM) authentication tokens are passed as command-line arguments to background helper processes during image retrieval operations. A local, unprivileged attacker on a system permitting cross-user process inspection can view these arguments while the process is active. This flaw can lead to information disclosure, potentially allowing unauthorized access to RHSM resources within the token's validity period.

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

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


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

No fix has been published for CVE-2026-113495 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-113495 being exploited?

There is no known exploitation of CVE-2026-113495 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-113495 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-113495 in the wild and no public exploit code.

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-113495/ (Markdown: https://insights.sbomify.com/CVE-2026-113495/index.md)
```

## Sources

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

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