CVE-2026-71474: Insertion of Sensitive Information into Log File in Red Hat Red Hat Advanced Cluster Management for Kubernetes 2.11
A vulnerability in Red Hat Advanced Cluster Management for Kubernetes 2.11's insights-client causes sensitive information, specifically the cloud.openshift.com pull-secret token, to be logged when a non-200 response is received. This token is written to pod logs at verbosity level 3 or higher, potentially exposing it to local users with access to these logs. Unauthorized access to Red Hat cloud services could result from this information disclosure. No official fix or mitigation meeting Red Hat's criteria is currently available.
AI Analysis
Technical Summary
CVE-2026-71474 is a vulnerability in the insights-client component of Red Hat Advanced Cluster Management for Kubernetes 2.11. When the client receives a non-200 HTTP response, it logs request headers that may include the cloud.openshift.com pull-secret token. This token is a long-lived credential that, if exposed in pod logs accessible to local users, could allow unauthorized access to Red Hat cloud services. The exposure requires specific logging conditions (verbosity level 3 or higher) and existing permissions to access pod logs. Red Hat has not provided an official patch or mitigation that meets their criteria for ease of use, applicability, and stability.
Potential Impact
The vulnerability allows local users with access to pod logs on the hub to read sensitive pull-secret tokens, which are long-lived credentials for Red Hat cloud services. This could lead to unauthorized access to these cloud services. The impact is confidentiality loss only; integrity and availability are not affected. Exploitation requires local access and specific logging configurations.
Mitigation Recommendations
Red Hat currently does not offer a mitigation or patch that meets their product security criteria for this issue. Users should be aware that the exposure depends on logging at verbosity level 3 or higher and existing pod log access permissions. Limiting log verbosity and restricting pod log access to trusted users may reduce exposure risk until an official fix is available. Monitor Red Hat's advisory for updates.
CVE-2026-71474: Insertion of Sensitive Information into Log File in Red Hat Red Hat Advanced Cluster Management for Kubernetes 2.11
Description
A vulnerability in Red Hat Advanced Cluster Management for Kubernetes 2.11's insights-client causes sensitive information, specifically the cloud.openshift.com pull-secret token, to be logged when a non-200 response is received. This token is written to pod logs at verbosity level 3 or higher, potentially exposing it to local users with access to these logs. Unauthorized access to Red Hat cloud services could result from this information disclosure. No official fix or mitigation meeting Red Hat's criteria is currently available.
CVSS v3.1
Score 7.1high
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-71474 is a vulnerability in the insights-client component of Red Hat Advanced Cluster Management for Kubernetes 2.11. When the client receives a non-200 HTTP response, it logs request headers that may include the cloud.openshift.com pull-secret token. This token is a long-lived credential that, if exposed in pod logs accessible to local users, could allow unauthorized access to Red Hat cloud services. The exposure requires specific logging conditions (verbosity level 3 or higher) and existing permissions to access pod logs. Red Hat has not provided an official patch or mitigation that meets their criteria for ease of use, applicability, and stability.
Potential Impact
The vulnerability allows local users with access to pod logs on the hub to read sensitive pull-secret tokens, which are long-lived credentials for Red Hat cloud services. This could lead to unauthorized access to these cloud services. The impact is confidentiality loss only; integrity and availability are not affected. Exploitation requires local access and specific logging configurations.
Mitigation Recommendations
Red Hat currently does not offer a mitigation or patch that meets their product security criteria for this issue. Users should be aware that the exposure depends on logging at verbosity level 3 or higher and existing pod log access permissions. Limiting log verbosity and restricting pod log access to trusted users may reduce exposure risk until an official fix is available. Monitor Red Hat's advisory for updates.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-6q5x-r3rm-rpv8
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-71474"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6a7c9b6fbf8831d539ce011f
Added to database: 08/12/2026, 16:12:31 UTC
Last enriched: 09/12/2026, 05:02:09 UTC
Last updated: 09/26/2026, 13:47:47 UTC
Views: 41
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.