# CVE-2026-71845: Insights-client: insights-client: ccx_token bearer credential logged in clear text at startup via setdefault()

> Attackers with log access can steal bearer tokens logged in clear text, enabling unauthorized access to the CCX API.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Aug 2026
- **Updated:** 5 Sep 2026
- **Also known as:** GHSA-h2jx-ffv3-pwqm

## What is CVE-2026-71845?

CVE-2026-71845 is a medium-severity vulnerability in Red Hat Advanced Cluster Management for Kubernetes 2.11, published on 11 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw was found in insights-client. The setDefault() function logs the value of every environment variable it processes, including CCX_TOKEN, a bearer credential used in disconnected cluster deployments. When glog verbosity is set to level 2 or higher, the token is written in clear text to the pod log on every startup. An attacker with access to pod logs or centralized logging could obtain the credential, leading to unauthorized access to the CCX API.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

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

It affects 2 products.


Products: Redhat Advanced Cluster Management for Kubernetes, Redhat Insights-Client.

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

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

## Is CVE-2026-71845 being exploited?

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

## Other vulnerabilities in Red Hat Advanced Cluster Management for Kubernetes 2.11

- [CVE-2026-4740](https://insights.sbomify.com/CVE-2026-4740/): Open Cluster Management (OCM): Cross-cluster privilege escalation via improper Kubernetes client certificate renewal validation (high 8.2)
- [CVE-2023-3027](https://insights.sbomify.com/CVE-2023-3027/): Privilege escalation in RHACM (high 7.8)
- [CVE-2022-3841](https://insights.sbomify.com/CVE-2022-3841/): Server-side request forgery in RHACM (high 7.8)
- [CVE-2026-71474](https://insights.sbomify.com/CVE-2026-71474/): Insights-client-rhel9: insights-client: pull-secret bearer token written to logs on non-200 ccx response (high 7.1)
- [CVE-2026-71475](https://insights.sbomify.com/CVE-2026-71475/): Insights-client-rhel9: insights-client: spoke-controlled clusterid injected unencoded into insights api url path (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-71845 is a medium-severity vulnerability in Red Hat Advanced Cluster Management for Kubernetes 2.11, published on 11 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-71845 in the wild and no public exploit code.

Affected product: Red Hat Advanced Cluster Management for Kubernetes 2.11. 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-71845/ (Markdown: https://insights.sbomify.com/CVE-2026-71845/index.md)
```

## Sources

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

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