Skip to content

← Actionable
High, CVSS 8.6amended

OSAC operator: Kubeconfig credential-plugin execution and SSRF in console proxy

CVE-2026-62284GHSA-5w5g-j6hw-6p8f

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/osac-project/osac-operator 0.0.4), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
8.6 · CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-62284: 0.51% estimated exploitation activity in the next 30 days; percentile 43.50 (FIRST EPSS, 2026-11-10). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Impact 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).…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from osv record GHSA-5w5g-j6hw-6p8f

  2. Revision 1 · created ·

    Published from ghsa record GHSA-5w5g-j6hw-6p8f

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-62284

Advisory: OSAC operator: Kubeconfig credential-plugin execution and SSRF in console proxy
IDs: CVE-2026-62284, GHSA-5w5g-j6hw-6p8f
Record: https://patchnext.com/advisories/cve-2026-62284 (revision 2, source checked 7 Nov 2026, 06:05 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/osac-project/osac-operator 0.0.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/osac-project/osac-operator: affected < 0.0.4; fixed in 0.0.4

## Suggested inspection (read-only)
- Go github.com/osac-project/osac-operator: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/osac-project/osac-operator.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-5w5g-j6hw-6p8f (GitHub-reviewed advisory GHSA-5w5g-j6hw-6p8f lists affected ranges: Go github.com/osac-project/osac-operator >=0 <0.0.4)
- Verified: https://osv.dev/vulnerability/GHSA-5w5g-j6hw-6p8f (OSV record GHSA-5w5g-j6hw-6p8f lists affected ranges: Go github.com/osac-project/osac-operator >=0 <0.0.4 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…