GPU VulnDB

Database/Container, Kubernetes & orchestration

Argo CD: read-only users can extract plaintext Kubernetes Secret data via ServerSideDiff

CVSS 9.6CVE-2026-42880Container, Kubernetes & orchestrationcurated

Impact

Argo CD's ServerSideDiff endpoint misses an authorization check and a data-masking step, so a user with nothing but read access round-trips a Secret through the API server's server-side apply dry-run and reads the plaintext back. Read-only Argo access is the level handed out broadly - to developers, to platform teams, to anyone who wants to see sync status - while Argo itself usually holds cluster-wide privileges to sync manifests everywhere. On a GPU cluster that means registry pull secrets, object store and model registry credentials, cloud keys and scheduler tokens all become readable by an account that was never meant to see them. Scored 9.6 with a scope change.

Who can reach it

An authenticated Argo CD user with read-only permission on at least one application, with network reach to the Argo CD API or UI. No admin role and no direct Kubernetes API access needed.

What to do

Upgrade Argo CD to 3.2.11 or 3.3.9; on OpenShift GitOps take RHSA-2026:20943 / RHSA-2026:20947. That is a rolling restart of the argocd-server deployment - no node drain, no GPU workload impact. Then rotate the Secrets that read-only users could have pulled, since the endpoint leaves no distinguishing trace in normal Argo audit output.

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.