Authenticated container tampering via writable backend filesystem
Published Aug 19, 2025 · Updated Dec 19, 2025
Incorrect privilege assignment in Red Hat Developer Hub before 1.7.0 allows remote authenticated users to alter its container filesystem. The backend container leaves readOnlyRootFilesystem disabled by default, permitting a cluster user with Developer Hub namespace access to write into the running rhdh/rhdh-hub-rhel9 container. The resulting confidentiality and integrity impact is limited to the running pod because modified contents reset when the pod restarts.
Summary
What happened
Incorrect privilege assignment in Red Hat Developer Hub before 1.7.0 allows remote authenticated users to alter its container filesystem. The backend container leaves readOnlyRootFilesystem disabled by default, permitting a cluster user with Developer Hub namespace access to write into the running rhdh/rhdh-hub-rhel9 container. The resulting confidentiality and integrity impact is limited to the running pod because modified contents reset when the pod restarts.
The record
- CVE
- CVE-2025-5417
- Published
- Aug 19, 2025
- Updated
- Dec 19, 2025
- Vendor
- 389 Directory Server
- Product
- Red Hat Developer Hub
- Classifications
- CWE-266, T1565.001
- Attack vector
- adjacent
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 19, 2025CVE publishedPublication date reported by the CVE source.
- Dec 19, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.7.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo