Skip to main content
VulnerabilityPublished Updated

CVE-2026-71845: Red Hat Advanced Cluster Management for Kubernetes 2.11 · Sensitive Data in Logs

Affects Red Hat Advanced Cluster Management for Kubernetes 2.11Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.3 Medium.

Data as of 8 Nov 2026, 23:24 UTC

CVSS 3.1 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Red HatRed Hat Advanced Cluster Management for Kubernetes 2.11Affected–Fixed in–
Red HatRed Hat Advanced Cluster Management for Kubernetes 2.13Affected–Fixed in–
Red HatRed Hat Advanced Cluster Management for Kubernetes 2.14Affected–Fixed in–
Red HatRed Hat Advanced Cluster Management for Kubernetes 2.15Affected–Fixed in–
Red HatRed Hat Advanced Cluster Management for Kubernetes 2.16Affected–Fixed in–
Red HatRed Hat Advanced Cluster Management for Kubernetes 2.17Affected–Fixed in–

AI-suggested

The vendor advisory recommends setting the glog verbosity level on the insights-client deployment below level 2 (e.g., -v=0 or -v=1) to prevent logging the token. Additionally, if CCX_TOKEN must be used in disconnected environments, access to pod logs in the open-cluster-management namespace and to centralized logging backends should be strictly restricted. Monitor the Red Hat advisory for updates on official fixes.

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.

References

Community reviews

Loading reviews…