VulnerabilityPublished 2 Jul 2025Updated 20 Nov 2025

CVE-2025-6017: Red Hat Advanced Cluster Management for Kubernetes 2 · Exposure of Private Personal Information to an Unauthorized Actor

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

Not known to be exploited · CVSS 5.5 Medium · fixed in Red Hat package updates : update the Red Hat redhat/advanced-cluster-management package when convenient.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

5.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2.12.4, 2.11.4, 2.10.7

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 2 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade the Red Hat redhat/advanced-cluster-management package to 2.12.4, 2.11.4 or 2.10.7.

Affected software

Product	Affected	Fixed in
Red Hatredhat/advanced-cluster-management`pkg:rpm/redhat/advanced-cluster-management`Other threats	Affected <2.10.7 <2.11.4 <2.12.4	Fixed in 2.10.7 2.11.4 2.12.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2025-6017, organizations should promptly upgrade Red Hat Advanced Cluster Management for Kubernetes 2 to versions 2.10.7, 2.11.4, 2.12.4, or later, where the vulnerability is patched. Until patching is complete, restrict UI access to trusted and fully authorized personnel only, employing network segmentation and strict access control policies. Implement role-based access control (RBAC) to ensure users have the minimum necessary privileges, and regularly audit user permissions to detect and revoke unnecessary access. Monitor UI access logs for unusual or unauthorized attempts to view cluster credentials. Employ multi-factor authentication (MFA) for UI access to reduce the risk of compromised accounts being exploited. Additionally, consider using secrets management solutions that provide additional layers of encryption and access control for cluster credentials. Conduct security awareness training for administrators and users to recognize and report suspicious activities. Finally, maintain an incident response plan to quickly address any suspected credential exposure or misuse.

Description

A flaw was found in Red Hat Advanced Cluster Management through versions 2.10, before 2.10.7, 2.11, before 2.11.4, and 2.12, before 2.12.4. This vulnerability allows an unprivileged user to view confidential managed cluster credentials through the UI. This information should only be accessible to authorized users and may result in the loss of confidentiality of administrative information, which could be leaked to unauthorized actors.

Impact

The primary impact of CVE-2025-6017 is the loss of confidentiality of sensitive managed cluster credentials. Unauthorized access to these credentials can enable attackers or malicious insiders to gain unauthorized control over Kubernetes clusters, potentially leading to data exposure, unauthorized deployment or modification of workloads, and lateral movement within the infrastructure. Although the vulnerability does not directly affect integrity or availability, the compromise of credentials can be a stepping stone to more severe attacks, including privilege escalation and persistent access. Organizations using affected versions of Red Hat Advanced Cluster Management are at risk of credential leakage if unprivileged users can access the UI. This risk is heightened in environments with multiple users or where access controls are not tightly enforced. The absence of known exploits in the wild reduces immediate risk but does not eliminate the threat, especially as attackers may develop exploits following public disclosure. The impact is significant for enterprises relying on Kubernetes for critical workloads, including cloud service providers, financial institutions, government agencies, and large enterprises with complex container orchestration environments.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Feb 2026, 15:54 UTC

Technical details

References

Community reviews

Related threats