Skip to content
VulniPulse
Sign in
Advisory severityMedium6.3Red Hat Linux

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.11, Red Hat Advanced Cluster Management for Kubernetes 2.13, Red Hat Advanced Cluster Management for Kubernetes 2.14.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-71845 Source published Source updated

VulniPulse record published Record updated

CVE-2026-71845
Affected products & platforms
Red Hat LinuxUnclassified
Open source 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 34 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery
Get CVE alertsSee app features

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 fixing advisory: RHSA-2026:60387, RHSA-2026:60390, RHSA-2026:60388, RHSA-2026:60389, RHSA-2026:60391, RHSA-2026:60386.

Affected products named by the advisory: Red Hat Advanced Cluster Management for Kubernetes 2.11; Red Hat Advanced Cluster Management for Kubernetes 2.13; Red Hat Advanced Cluster Management for Kubernetes 2.14; Red Hat Advanced Cluster Management for Kubernetes 2.15; and 2 more.

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 day ago·verify at source

Fixed versions
  • rhacm2/insights-client-rhel9:1787688993
  • rhacm2/insights-client-rhel9:1787259125
  • rhacm2/insights-client-rhel9:1786882244
  • rhacm2/insights-client-rhel9:1787238585
  • rhacm2/insights-client-rhel9:1787184541
  • rhacm2/insights-client-rhel9:1787227689
  • RHSA-2026:60387
  • RHSA-2026:60390
  • RHSA-2026:60388
  • RHSA-2026:60389
  • RHSA-2026:60391
  • RHSA-2026:60386

Official advisory · high-confidence parse· fetched 1 day 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 day 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.