Skip to content
VulniPulse
Medium6.3Red Hat Linux Updated

Medium [CVE-2026-71845] CCX_TOKEN bearer credential logged in clear text at startup via setDefault

This medium-severity Red Hat Linux advisory covers CVE-2026-71845 affecting Red Hat Advanced Cluster Management for Kubernetes 2.

CVE-2026-71845 Published Aug 11, 2026Updated by vendor Aug 11, 2026
Affected products & platforms
Red Hat LinuxUnclassified
Open vendor advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

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.

This is a Moderate flaw in Red Hat Advanced Cluster Management for Kubernetes. This credential is used by disconnected cluster deployments as an alternative to cloud.redhat.com.

Red Hat severity: Moderate — CVSS 6.3 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N). Weakness: CWE-532.

Red Hat does not currently list a fixing RHSA for this CVE.

Affected product named by the advisory: Red Hat Advanced Cluster Management for Kubernetes 2.

Affected versions

No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.

Official advisory · high-confidence parse· fetched 1 hour ago·verify at source

Fixed versions

No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.

Official advisory · high-confidence parse· fetched 1 hour ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Ensure glog verbosity on the insights-client Deployment is set below level 2 (-v=0 or -v=1). If CCX_TOKEN must be configured for disconnected environments, restrict access to pod logs in the open-cluster-management namespace and to centralized logging backends.

Official advisory · high-confidence parse· fetched 1 hour ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.