Red Hat Advanced Cluster Management for…: Insertion of Sensitive Information into Log File
CVE-2026-71845 is a high-severity insertion of sensitive information into log file vulnerability in Red Hat Advanced Cluster Management for Kubernetes 2.11 from Red Hat, with a CVSS 3.1 base score of 7.7 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. There is no confirmed exploitation so far. EPSS estimates a 0.5% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of Red Hat Advanced Cluster Management for Kubernetes 2.11 you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on access.redhat.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Red Hat | Red Hat Advanced Cluster Management for Kubernetes 2.11 | Not specified in the record | Not stated |
| Red Hat | Red Hat Advanced Cluster Management for Kubernetes 2.13 | Not specified in the record | Not stated |
| Red Hat | Red Hat Advanced Cluster Management for Kubernetes 2.14 | Not specified in the record | Not stated |
| Red Hat | Red Hat Advanced Cluster Management for Kubernetes 2.15 | Not specified in the record | Not stated |
| Red Hat | Red Hat Advanced Cluster Management for Kubernetes 2.16 | Not specified in the record | Not stated |
| Red Hat | Red Hat Advanced Cluster Management for Kubernetes 2.17 | Not specified in the record | Not stated |
| Red Hat | Advanced Cluster Management For Kubernetes | 2.0 | Not stated |
| Red Hat | Insights-client | Not specified in the record | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- NoneNothing can be modified.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 6.3 | Medium | CNA (redhat.com) |
| CVSS 3.1 | 7.7 | High | NVD |
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Insertion of Sensitive Information into Log File
The product writes sensitive information to a log file.
How developers prevent this class of flaw
- Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.
- Remove debug log files before deploying the application into production.
- Protect log files against unauthorized read/write.
More Insertion of Sensitive Information into Log File vulnerabilities (CWE-532)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other references
Other vulnerabilities in Red Hat Advanced Cluster Management for Kubernetes 2.11
- 7.7 High severity
- 9.9 Critical severity
- 8.0 High severity
- 9.9 Critical severity
- 9.1 Critical severity
- 8.8 High severity
Recent Insertion of Sensitive Information into Log File vulnerabilities
- 7.5 High severity
- 7.5 High severity
- 7.8 High severity
- 9.8 Critical severity
- 7.2 High severity
- 8.6 High severity
Spotted an error? Tell us.