dbcve.org
Advanced Cluster Management For KubernetesApplication · Redhat

CVE-2025-6017

MEDIUM · 5.5 CVSS v3.1 Published 2025-07-02
Fix available
A fix is available. Upgrade to 2.10.7 / 2.11.4 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Red Hat Advanced Cluster Management contains an improper access control vulnerability where unprivileged users can view confidential managed cluster credentials through the web UI. The UI fails to properly enforce authorization checks, exposing sensitive administrative credentials that should be restricted to authorized administrators only.

MitigationUpgrade RHACM to version 2.10.7, 2.11.4, 2.12.4 or later to remediate this vulnerability. Verify that unauthorized users can no longer access managed cluster credentials through the UI.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Advanced Cluster Management For KubernetesApplication
Affected:>= 2.10, < 2.10.7>= 2.11, < 2.11.4>= 2.12, < 2.12.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check the installed RHACM version
    Run 'oc get csv -n open-cluster-management' or check the RHACM operator version in the Operator Hub. Compare the version number to the affected ranges: 2.10.x before 2.10.7, 2.11.x before 2.11.4, or 2.12.x before 2.12.4.
    Affected if The installed version falls within any of the affected version ranges listed.
  2. Identify user roles with access to the RHACM web console
    Run 'oc get users' and 'oc get clusterrolebindings' to enumerate users and their assigned roles. Identify accounts that do not have administrator-level privileges.
    Affected if There are non-administrative users configured who can access the RHACM web console.
  3. Test if unprivileged users can view managed cluster credentials
    Log in to the RHACM web console as a non-admin user, navigate to the Clusters section, select a managed cluster, and check if the 'Credentials' tab or any credential information is visible and accessible without admin rights.
    Affected if Non-admin users can view managed cluster credentials (kubeconfig, SSH keys, pull secrets) through the web UI.
  4. Verify API authorization on credential endpoints
    As a non-admin user, attempt to query the RHACM API endpoint for cluster credentials (e.g., via 'oc get managedcluster <cluster-name> -o json' and check for exposed secret references) to confirm if authorization is bypassed.
    Affected if API responses include credential or secret data accessible to non-admin users.

You are affected if your RHACM version is 2.10.x < 2.10.7, 2.11.x < 2.11.4, or 2.12.x < 2.12.4 AND unprivileged users can view managed cluster credentials through the UI or API.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.10.7 / 2.11.4 / 2.12.4 or later
Fixed in 2.10.72.11.42.12.4
Interim mitigation

Upgrade RHACM to version 2.10.7, 2.11.4, 2.12.4 or later to remediate this vulnerability. Verify that unauthorized users can no longer access managed cluster credentials through the UI.

Recommended fix Moderate confidence

Upgrade to ACM 2.10.7, 2.11.4, or 2.12.4 (whichever corresponds to your current release line; 2.12.4 is the latest stable release)

  1. Identify the currently installed version of Advanced Cluster Management for Kubernetes
  2. Determine the appropriate upgrade path based on your current version (2.10.x -> 2.10.7, 2.11.x -> 2.11.4, or 2.12.x -> 2.12.4)
  3. Review the Red Hat Advanced Cluster Management upgrade documentation for your version
  4. Create a backup of your current ACM configuration and data
  5. Plan maintenance window as upgrade will require cluster downtime
  6. Execute the upgrade using the RHACM operator or OpenShift Container Platform operator lifecycle manager
  7. Verify the upgrade completed successfully by checking the ACM operator version
  8. Confirm the vulnerability is resolved by verifying unprivileged users can no longer access managed cluster credentials through the UI
Caveat Review upgrade prerequisites and known issues in the RHACM release notes before upgrading; ensure compatibility with your underlying OpenShift Container Platform version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Advanced Cluster Management For Kubernetes Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-6017 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-6017 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data