CVE-2026-75888: Openshift/console: openshift/console: authenticated ssrf via helm chart url fetch
A flaw was found in the OpenShift console. An authenticated console user can exploit a Server-Side Request Forgery (SSRF) vulnerability by providing a specially crafted Helm chart URL without proper validation. This allows the user to make the console pod fetch arbitrary URLs, potentially leading to the disclosure of sensitive information through error messages or enabling blind port scanning within the cluster.
Other sources
The Helm chart endpoints in the OpenShift console accept a user-supplied chartUrl (query parameter or JSON field) and pass it to LocateChart without validation (pkg/helm/handlers/handlers.go:236-258, pkg/helm/actions/getchart.go:22-27).
LocateChart downloads http://, https://, or oci:// URLs. The same pattern recurs in InstallChart, InstallChartAsync, UpgradeRelease, and RenderManifests via the req.ChartUrl field. When the repositoryNamespace=="" short-circuit path is taken, no repository index validation occurs.
An authenticated console user can make the console pod fetch arbitrary URLs. The gzip/tar parse error reflected to the user contains response-body excerpts, enabling partial-read SSRF. Also usable for blind in-cluster port-scanning via timing.
Tested and reproduced on OCP 5.0 nightly cluster.
Upstream: https://github.com/openshift/console File: pkg/helm/handlers/handlers.go:236-258, pkg/helm/actions/getchart.go:22-27, pkg/helm/actions/installchart.go:71-77
— Red Hat
Affected Software
Event History
Frequently Asked Questions
Who can exploit this issue?
An authenticated OpenShift console user can exploit it. No user interaction is required beyond the attacker supplying a crafted Helm chart URL to a vulnerable console endpoint.
What network access does exploitation provide?
The console pod can be induced to fetch arbitrary http://, https://, or oci:// URLs. This can be used for blind port scanning of in-cluster services based on request timing.
Can an attacker obtain response data, or is this only a blind SSRF?
It can disclose partial response data. Gzip or tar parsing errors returned to the user may contain excerpts of the fetched response body.
Which operations handle the attacker-controlled chart URL?
The affected pattern is present in chart retrieval and in InstallChart, InstallChartAsync, UpgradeRelease, and RenderManifests through the chartUrl value. The repositoryNamespace=="" path bypasses repository index validation.