Skip to main content
VulnerabilityPublished Updated

CVE-2026-71474: Red Hat Advanced Cluster Management for Kubernetes 2.11 · Sensitive Data in Logs

Affects Red Hat Advanced Cluster Management for Kubernetes 2.11Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.1 High.

Data as of 8 Nov 2026, 23:24 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Red HatRed Hat Advanced Cluster Management for Kubernetes 2.11Affected–Fixed in–
Red HatRed Hat Advanced Cluster Management for Kubernetes 2.13Affected–Fixed in–
Red HatRed Hat Advanced Cluster Management for Kubernetes 2.14Affected–Fixed in–
Red HatRed Hat Advanced Cluster Management for Kubernetes 2.15Affected–Fixed in–
Red HatRed Hat Advanced Cluster Management for Kubernetes 2.16Affected–Fixed in–
Red HatRed Hat Advanced Cluster Management for Kubernetes 2.17Affected–Fixed in–

AI-suggested

Red Hat currently states that no mitigation is available or that existing options do not meet their criteria for ease of use, applicability, or stability. Users should monitor Red Hat's advisory for updates. Since the vulnerability requires specific logging verbosity and pod log access, limiting access to pod logs and controlling logging verbosity may reduce exposure.

Description

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.

References

Community reviews

Loading reviews…