# CVE-2025-6017: Rhacm: users with clusterreader role can see credentials from managed-clusters

> Unprivileged users with clusterreader role can view confidential managed cluster credentials via the UI, exposing administrative information.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jul 2025
- **Updated:** 20 Nov 2025
- **Also known as:** GHSA-g8pw-ch7g-q2vc

## What is CVE-2025-6017?

CVE-2025-6017 is a medium-severity vulnerability in Red Hat Advanced Cluster Management for Kubernetes 2, published on 2 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-359 (Exposure of Private Personal Information to an Unauthorized Actor)

## Which versions are affected by CVE-2025-6017?

It affects 1 product.


Products: Redhat Advanced Cluster Management for Kubernetes.

## How do I fix CVE-2025-6017?

No fix has been published for CVE-2025-6017 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-6017 being exploited?

There is no known exploitation of CVE-2025-6017 in the wild and no public exploit code.

## Other vulnerabilities in Red Hat Advanced Cluster Management for Kubernetes 2

- [CVE-2026-4740](https://insights.sbomify.com/CVE-2026-4740/): Open Cluster Management (OCM): Cross-cluster privilege escalation via improper Kubernetes client certificate renewal validation (high 8.2)
- [CVE-2023-3027](https://insights.sbomify.com/CVE-2023-3027/): Privilege escalation in RHACM (high 7.8)
- [CVE-2022-3841](https://insights.sbomify.com/CVE-2022-3841/): Server-side request forgery in RHACM (high 7.8)
- [CVE-2026-71474](https://insights.sbomify.com/CVE-2026-71474/): Insights-client-rhel9: insights-client: pull-secret bearer token written to logs on non-200 ccx response (high 7.1)
- [CVE-2026-71475](https://insights.sbomify.com/CVE-2026-71475/): Insights-client-rhel9: insights-client: spoke-controlled clusterid injected unencoded into insights api url path (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-6017 and fix it if it is affected.

What it is: CVE-2025-6017 is a medium-severity vulnerability in Red Hat Advanced Cluster Management for Kubernetes 2, published on 2 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-6017 in the wild and no public exploit code.

Affected product: Red Hat Advanced Cluster Management for Kubernetes 2. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-6017/ (Markdown: https://insights.sbomify.com/CVE-2025-6017/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-6017
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-6017
- OSV: https://osv.dev/vulnerability/CVE-2025-6017

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-6017/
Summaries are generated and may contain mistakes; the official description above is the record.