CVE-2026-71474
HighCVSS 7.1Exploitation Probability (EPSS)
Low risk1th percentile - higher than 1% of all known CVEs
Summary
In insights-client, when a non-200 response is received, request headers are logged, which may include the cloud.openshift.com pull-secret token. A local user with access to pod logs on the hub could read this long-lived credential. This information disclosure could grant unauthorized access to Red Hat cloud services.
Risk Assessment
Disclosure of a long-lived token could lead to unauthorized access to Red Hat cloud services, potentially compromising data confidentiality and system integrity.
Recommendation
It is recommended to immediately update insights-client to a version that does not log request headers, and to rotate pull-secret tokens. Also, restrict access to pod logs to trusted users only.
Other vulnerabilities in insights-client
See all- CVE-2026-71846Medium
A flaw was found in insights-client. The component's ServiceAccount is bound to a ClusterRole granting cluster-wide secrets get, list, and watch permissions, while the code only requires access to a single specific Secret. This excessive privilege means that a compromise of the insights-client pod or ServiceAccount token would grant an attacker read access to all Secrets across the hub cluster, including managed-cluster kubeconfigs and other sensitive credentials.
- CVE-2026-71845Medium
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.
- CVE-2026-71475Medium
A flaw was found in insights-client: a compromised managed cluster (spoke) can inject unencoded data into the Insights API URL path. This occurs because the ClusterID, which is controlled by the spoke, is used directly in the request path without proper validation or URL encoding. This vulnerability allows a malicious spoke to redirect authenticated requests to unintended API endpoints, potentially leading to information disclosure or unauthorized access.
Original NVD description (English source)
A flaw was found in insights-client. When the application receives a non-200 response, it logs the request headers, which can include the cloud.openshift.com pull-secret token. A local user with access to pod logs on the hub could read this long-lived credential. This information disclosure could grant unauthorized access to Red Hat cloud services.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS