High [CVE-2026-71474] Pull-secret bearer token written to logs on non-200 CCX response
This high-severity Red Hat Linux advisory covers CVE-2026-71474 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.
VulniPulse record published Record updated
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.
Summary
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.
This vulnerability is rated as Moderate rather than Important because credential leakage requires elevated debug logging enabled alongside an upstream service failure, and access is constrained to users with log-reading permissions on the hub cluster.
In standard Red Hat Advanced Cluster Management environments, default logging levels do not expose HTTP headers during regular operations.
If high verbosity is activated and server communication fails, an authenticated user capable of reading container output could retrieve the cloud authentication token, allowing unauthorized interaction with associated Red Hat hosted services. Red Hat severity: Moderate — CVSS 7.1 (CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N).
Weakness: CWE-532.
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 3 hours ago·verify at source
- 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 3 hours ago·verify at source
Mitigation checklist
- Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Official advisory · high-confidence parse· fetched 3 hours 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.