GPU VulnDB

Database/Container, Kubernetes & orchestration

Argo CD repo-server: shell metacharacters in a repository proxy URL run commands and leak Git/Helm/OCI credentials

CVSS 8.8CVE-2026-55797Container, Kubernetes & orchestrationcurated

Impact

The repo-server builds an SSH ProxyCommand from a repository's configured proxy host and port and runs it through a shell without neutralizing metacharacters, so a crafted proxy host executes arbitrary commands inside the repo-server. The repo-server holds the credentials for every Git, Helm and OCI source the cluster deploys from, so this converts the ability to add or edit one repository into read access to the deployment credentials for all of them. On a GPU fleet that is the component that renders the manifests for the GPU Operator, device plugin, scheduler and tenant workloads, so credential theft or manifest tampering here reaches every node without touching a node directly. Affects 2.11.0 up to the fixed releases.

Who can reach it

Any authenticated Argo CD user (or service account) with permission to create or update a repository or a repository credential template - over the network, no cluster access required.

What to do

Upgrade Argo CD to 3.3.15, 3.4.10, 3.5.4 or 3.6.0-rc2 and restart the repo-server deployment; this is a control-plane rollout, not a node operation, so no GPU node drain is needed. Until then, restrict who holds repository create/update RBAC and audit existing repository configurations for proxy URLs containing shell metacharacters.

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.