Credential disclosure via non-200 request-header logging
Published Aug 11, 2026 · Updated Aug 11, 2026
Information disclosure in Red Hat Advanced Cluster Management for Kubernetes allows local users to read a pull-secret token from hub pod logs. When insights-client receives a non-200 response at verbosity level 3 or higher, it writes request headers containing the cloud.openshift.com token to stderr and pod logs. Access requires existing pods/log permission on the hub, and the exposed long-lived credential grants unauthorized access to Red Hat cloud services.
Summary
What happened
Information disclosure in Red Hat Advanced Cluster Management for Kubernetes allows local users to read a pull-secret token from hub pod logs. When insights-client receives a non-200 response at verbosity level 3 or higher, it writes request headers containing the cloud.openshift.com token to stderr and pod logs. Access requires existing pods/log permission on the hub, and the exposed long-lived credential grants unauthorized access to Red Hat cloud services.
The record
- CVE
- CVE-2026-71474
- Published
- Aug 11, 2026
- Updated
- Aug 11, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat Advanced Cluster Management for Kubernetes
- Classifications
- CWE-532, T1552.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 11, 2026CVE publishedPublication date reported by the CVE source.
- Aug 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo