dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2025-5417

MEDIUM · 6.1 CVSS v3.1 Published 2025-08-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
63/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
An insufficient access control vulnerability was found in the Red Hat Developer Hub rhdh/rhdh-hub-rhel9 container image. The Red Hat Developer Hub cluster admin/user, who has standard user access to the cluster, and the Red Hat Developer Hub namespace, can access the rhdh/rhdh-hub-rhel9 container image and modify the image's content. This issue affects the confidentiality and integrity of the data, and any changes made are not permanent, as they reset after the pod restarts.

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 · moderate confidence

A role-based access control (RBAC) misconfiguration in Red Hat Developer Hub allows standard cluster users with namespace access to read and modify container image content, impacting confidentiality and integrity. While modifications are ephemeral (reset on pod restart), unauthorized image access and tampering remains possible.

MitigationImplement proper RBAC policies to restrict access to the rhdh namespace and container images, ensuring only authorized service accounts can pull or modify images. Consider using Kubernetes NetworkPolicies and ImagePullSecrets to further isolate image access.

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

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
Adjacent
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:H/I:H/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. Identify Red Hat Developer Hub installation and version
    Run 'helm list -A' or 'oc get pods -A | grep -i rhdh' to find RHDH deployment, then check the version from the operator or pod labels using 'oc get deployment -n <rhdh-namespace> -o yaml' or 'helm list -n <rhdh-namespace>'
    Affected if RHDH is installed and version falls within the affected range (compare to vendor advisory)
  2. Locate the rhdh namespace
    Run 'kubectl get namespaces' or 'oc get namespaces' to identify namespaces containing 'rhdh' or 'developer-hub'
    Affected if The rhdh namespace exists and standard cluster users have access to it
  3. Review RoleBindings in the rhdh namespace
    Run 'kubectl get rolebindings -n <rhdh-namespace> -o yaml' or 'oc get rolebindings -n rhdh -o wide' to list all role bindings and their subjects
    Affected if Standard cluster users (non-admin) are listed as subjects in RoleBindings within rhdh namespace
  4. Examine ClusterRoleBindings affecting image access
    Run 'kubectl get clusterrolebindings -o yaml | grep -i image' or 'oc get clusterrolebindings | grep -E "image|pull|push"' to identify cluster-wide bindings related to container images
    Affected if ClusterRoleBindings grant image read/write permissions to standard users or groups
  5. Check for overly permissive default service account bindings
    Run 'kubectl get serviceaccount default -n <rhdh-namespace> -o yaml' and review 'kubectl auth can-i --list --as=system:serviceaccount:<rhdh-namespace>:default' to determine what the default SA can do
    Affected if The default service account in rhdh namespace has elevated permissions to pull, push, or modify images

A user is affected if RHDH is installed with the vulnerable configuration and standard cluster users have been granted access to the rhdh namespace or have image pull/push permissions through RBAC bindings.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper RBAC policies to restrict access to the rhdh namespace and container images, ensuring only authorized service accounts can pull or modify images. Consider using Kubernetes NetworkPolicies and ImagePullSecrets to further isolate image access.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-5417 — 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-5417 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