A flaw was found in insights-client. (CVE-2026-71845)
A vulnerability in the insights-client component causes the CCX_TOKEN bearer credential to be logged in clear text in pod logs when glog verbosity is set to level 2 or higher. This token is used in disconnected cluster deployments to access the CCX API. An attacker with access to pod logs or centralized logging could obtain this credential and gain unauthorized access to the CCX API. The issue is rated as moderate severity with a CVSS score of 6.3.
AI Analysis
Technical Summary
CVE-2026-71845 is a moderate severity vulnerability in the insights-client component of Red Hat Advanced Cluster Management for Kubernetes. The setDefault() function logs every environment variable it processes, including the sensitive CCX_TOKEN bearer credential. When glog verbosity is configured at level 2 or higher, this token is written in clear text to pod logs on every startup. An attacker with access to these logs or centralized logging systems could extract the token and use it to access the CCX API without authorization. The vulnerability is classified under CWE-532 (Insertion of Sensitive Information into Log File).
Potential Impact
Exposure of the CCX_TOKEN bearer credential in pod logs can lead to unauthorized access to the CCX API for disconnected cluster deployments. This compromises confidentiality but does not affect integrity or availability. The vulnerability requires an attacker to have access to pod logs or centralized logging systems, and the attack complexity is high due to this prerequisite. The CVSS 3.1 base score is 6.3 (medium severity).
Mitigation Recommendations
Red Hat advises setting the glog verbosity level for the insights-client deployment below level 2 (e.g., -v=0 or -v=1) to prevent logging the CCX_TOKEN in clear text. If the CCX_TOKEN must be used in disconnected environments, access to pod logs in the open-cluster-management namespace and to centralized logging backends should be strictly restricted. No official patch or fix is currently available; patch status is not yet confirmed — check the vendor advisory for updates.
A flaw was found in insights-client. (CVE-2026-71845)
Description
A vulnerability in the insights-client component causes the CCX_TOKEN bearer credential to be logged in clear text in pod logs when glog verbosity is set to level 2 or higher. This token is used in disconnected cluster deployments to access the CCX API. An attacker with access to pod logs or centralized logging could obtain this credential and gain unauthorized access to the CCX API. The issue is rated as moderate severity with a CVSS score of 6.3.
CVSS v3.1
Score 6.3medium
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-71845 is a moderate severity vulnerability in the insights-client component of Red Hat Advanced Cluster Management for Kubernetes. The setDefault() function logs every environment variable it processes, including the sensitive CCX_TOKEN bearer credential. When glog verbosity is configured at level 2 or higher, this token is written in clear text to pod logs on every startup. An attacker with access to these logs or centralized logging systems could extract the token and use it to access the CCX API without authorization. The vulnerability is classified under CWE-532 (Insertion of Sensitive Information into Log File).
Potential Impact
Exposure of the CCX_TOKEN bearer credential in pod logs can lead to unauthorized access to the CCX API for disconnected cluster deployments. This compromises confidentiality but does not affect integrity or availability. The vulnerability requires an attacker to have access to pod logs or centralized logging systems, and the attack complexity is high due to this prerequisite. The CVSS 3.1 base score is 6.3 (medium severity).
Mitigation Recommendations
Red Hat advises setting the glog verbosity level for the insights-client deployment below level 2 (e.g., -v=0 or -v=1) to prevent logging the CCX_TOKEN in clear text. If the CCX_TOKEN must be used in disconnected environments, access to pod logs in the open-cluster-management namespace and to centralized logging backends should be strictly restricted. No official patch or fix is currently available; patch status is not yet confirmed — check the vendor advisory for updates.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-h2jx-ffv3-pwqm
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-71845"]
- Ecosystems
- []
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6a7c9b6fbf8831d539ce00f3
Added to database: 08/12/2026, 16:12:31 UTC
Last enriched: 08/12/2026, 17:24:09 UTC
Last updated: 08/13/2026, 02:41:00 UTC
Views: 2
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.