CVE-2026-62284: OSAC operator: Kubeconfig credential-plugin execution and SSRF in console proxy
The console-proxy’s RemoteConfigResolver parses kubeconfig data from Kubernetes Secrets using clientcmd.RESTConfigFromKubeConfig without sanitizing the resulting rest.Config. A kubeconfig containing an exec plugin stanza (under users[].user.exec) is faithfully preserved. When rest.TransportFor later builds the HTTP transport for the upstream WebSocket connection, client-go invokes the exec plugin — spawning an arbitrary process as the osac-console-proxy service account.
This allows remote code execution inside the console-proxy pod for any principal that can create or modify a Secret with the label osac.openshift.io/remote-cluster-kubeconfig: “true” in a namespace where the console-proxy has Secret read access (governed by its RoleBinding). A secondary vector exists via attacker-controlled clusters[].server, enabling server-side request forgery (SSRF) from within the proxy pod.
Affected configurations: any deployment using remote or auto VM cluster mode (the default). Deployments using local mode exclusively are not affected, as they do not read kubeconfig Secrets.
References
- github.com/advisories/GHSA-5w5g-j6hw-6p8f
- github.com/osac-project/osac-operator/commit/7e4222b6ab465fc00606c8cfed980b226820cb1b
- github.com/osac-project/osac-operator/commit/86466378aa3603253dca7fa2f59a2733af0dc092
- github.com/osac-project/osac-operator/pull/321
- github.com/osac-project/osac-operator/security/advisories/GHSA-5w5g-j6hw-6p8f
- nvd.nist.gov/vuln/detail/CVE-2026-62284
Code Behaviors & Features
Detect and mitigate CVE-2026-62284 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →