CVE-2026-71845: insights-client · Sensitive Data in Logs
Source GCVE Database
Not known to be exploited · CVSS 6.3 Medium · fixed in Red Hat Advanced Cluster Management for Kubernetes 2.11 package updates : update Red Hat Advanced Cluster Management for Kubernetes 2.11 when convenient.
Data as of 11 Nov 2026, 23:24 UTC
- 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.
- Patch
- Available – fixed in 2.17.1
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 11 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 11 Nov 2026.
What to do
Patches and advisories
- access.redhat.com/errata/RHSA-2026:60386 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:60387 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:60388 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:60389 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:60390 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:60391 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Red HatRed Hat Advanced Cluster Management for Kubernetes 2.11 | Affected– | Fixed in– |
| Red HatRed Hat Advanced Cluster Management for Kubernetes 2.13 | Affected– | Fixed in– |
| Red HatRed Hat Advanced Cluster Management for Kubernetes 2.14 | Affected– | Fixed in– |
| Red HatRed Hat Advanced Cluster Management for Kubernetes 2.15 | Affected– | Fixed in– |
| Red HatRed Hat Advanced Cluster Management for Kubernetes 2.16 | Affected– | Fixed in– |
| Red HatRed Hat Advanced Cluster Management for Kubernetes 2.17 | Affected– | Fixed in– |
AI-suggested
Red Hat has released a security update for Red Hat Advanced Cluster Management for Kubernetes version 2.17.1 that addresses this issue. Users should apply this update to prevent token leakage via logs. If you cannot patch yet, avoid setting glog verbosity to level 2 or higher in production environments where sensitive tokens are used. Review and restrict access to pod logs and centralized logging systems to minimize exposure.
Description
A vulnerability in insights-client's setDefault() function causes sensitive environment variables, including the CCX_TOKEN bearer token, to be logged in clear text when glog verbosity is set to level 2 or higher. This token exposure in pod logs can allow attackers with access to logs to obtain credentials and gain unauthorized access to the CCX API.
References
- nvd.nist.gov/vuln/detail/CVE-2026-71845 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:60386 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:60387 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:60388 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:60389 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:60390 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:60391 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-71845 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2512568 (opens in a new tab)