# CVE-2025-5417: Rhdh: red hat developer hub user permissions

> Standard cluster users can modify the Red Hat Developer Hub container image content, compromising data integrity and confidentiality until pod restart.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Aug 2025
- **Updated:** 19 Dec 2025
- **Also known as:** GHSA-qxg3-p56f-vx54

## What is CVE-2025-5417?

CVE-2025-5417 is a medium-severity missing authorization vulnerability in Red Hat Developer Hub, published on 19 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-266 (Incorrect Privilege Assignment)

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


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

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

## Is CVE-2025-5417 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-5417 is a medium-severity missing authorization vulnerability in Red Hat Developer Hub, published on 19 Aug 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-5417 in the wild and no public exploit code.

Affected product: Red Hat Developer Hub. 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-5417/ (Markdown: https://insights.sbomify.com/CVE-2025-5417/index.md)
```

## Sources

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

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