GPU VulnDB

Database/Container, Kubernetes & orchestration

Argo CD Image Updater: ImageUpdater resource crosses namespaces to update other tenants' apps

CVSS 9.1CVE-2026-6388Container, Kubernetes & orchestrationcurated

Impact

Insufficient validation of ImageUpdater resources lets a tenant who can create or edit one in their own namespace trigger image updates on Applications owned by other tenants. In a shared GPU cluster that means changing which container image another team's training or inference workload runs - the attacker chooses the image, the platform deploys it on their behalf onto nodes they were never granted. The practical effect is integrity loss across the namespace boundary GitOps multi-tenancy depends on, and an unexpected rollout on nodes the victim team cannot easily drain. Red Hat scores it with low confidentiality and availability impact and high integrity impact; the record describes unauthorized updates, not a direct container escape.

Who can reach it

An authenticated cluster user with RBAC to create or modify an ImageUpdater resource in any namespace of a multi-tenant cluster running Argo CD Image Updater. No cluster-admin needed.

What to do

Apply the Red Hat OpenShift GitOps update for CVE-2026-6388 (see the Red Hat CVE page and the CSAF VEX for the fixed component versions in your channel) and restart the Image Updater controller - a control-plane deployment restart, no node maintenance. Until it is available, restrict who may create ImageUpdater resources and audit recent image changes on Applications for updates nobody on the owning team requested.

References

Related entries

All Container, Kubernetes & orchestration entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.