Argo CD Repo Server Command Execution Through Kustomize

You probably treat get on an Argo CD Application as read access. On an unpatched server, it is enough to run commands inside argocd-repo-server and read the repository credentials that process can reach. The Argo CD project published two Critical advisories for this on 2026-10-07, and the fixes are already out. If you run 2.7.0 or later, upgrade this week.
| Kustomize remote ref | Kustomize Helm config home | |
|---|---|---|
| Identifier | GHSA-9v9p-x54c-58gc | GHSA-fw5c-w8rc-j7fx |
| Affected | 2.7.0 up to the fixed versions, and 3.6.0-rc1 | 2.1.0 up to the fixed versions, and 3.6.0-rc1, only where --enable-helm is passed to kustomize build |
| Fixed in | 3.3.15, 3.4.10, 3.5.4, 3.6.0-rc2 | Same releases |
| Severity | Critical, CVSS 3.1 9.9, as published on the project's GitHub advisory | Same |
| Exploited as of 2026-10-08 | No public reports in the advisories | Same |
| Disclosed | Fixed releases 2026-10-06, advisory 2026-10-07 | Same |
Track these by GHSA id. The 9.9 is the advisory's own number, and I have no NVD score to quote. The advisories mention no public proof of concept, but they explain the mechanism well enough that I would not wait for one.
Two bugs, both inherited from Kustomize
In the first, Kustomize takes a remote resource, base or component URL and appends its ref or version query value to git fetch with no -- separator. A value starting with a hyphen, such as --upload-pack=<command>, is parsed by Git as an option. That option runs the command when the remote uses a local transport such as file://, and not for https://.
A file:// remote never leaves the pod, so blocking repo-server egress does not help, and Git returns the command's output in the manifest-generation error.
It became reachable when Argo CD's bundled Kustomize went from 4.5.7 to 5.0.1 in commit 25badeb7a1 on 2023-03-16, first released in 2.7.0. Kustomize 4.5.7 rejects file://, and 5.0.0 first accepts it. Upgrading Kustomize alone does not help, because current Kustomize still passes the ref without a separator. Argo CD's patch puts a Git wrapper ahead of the real git on the build's PATH, so the URL and ref cannot parse as options. Remote bases keep working.
The second bug needs --enable-helm in your build options. Kustomize copies helmGlobals.configHome into Helm's config and data directories. Helm then loads a downloader plugin from <configHome>/.data/plugins with no separate install step, and runs its program when a helmCharts repository URL uses that plugin's protocol. This arrived with the Kustomize 3.9.4 to 4.1.2 upgrade in commit b6d5c23bc on 2021-04-20, first released in 2.1.0. The patch points Helm at an empty config and data directory for every Kustomize build.
Both bugs share two delivery paths:
- A Kustomization committed to a Git repository that an Application builds.
- An upload to
POST /api/v1/applications/manifestsWithFiles, the path behindargocd app diff --local --server-side-generate.
The upload path needs only Application get on an existing Application, with no permission to update or sync it and no write access to its repository. Either way, the command runs as the repo-server user and can read repository credentials and anything else available to that process.
What to check and do now
Upgrade. Go to 3.3.15, 3.4.10, 3.5.4 or 3.6.0-rc2, matching your minor. Argo CD 2.x and 3.0 to 3.2 have no patch, so move those to a supported minor. If you install from the project's manifests, the 3.3.15 release notes give this, with manifests/ha/install.yaml for HA:
kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.3.15/manifests/install.yaml
Check for the breaking change first. Kustomize builds that render Helm charts no longer honor helmGlobals.configHome, so Helm plugins registered that way stop working.
If you cannot upgrade today, know what each stopgap buys:
| Stopgap | Covers | Cost or gap |
|---|---|---|
Remove --enable-helm from kustomize.buildOptions | Helm bug, completely | Apps rendering Helm through Kustomize break |
Register Kustomize 4.5.7 with kustomize.path.<version> in argocd-cm, and set spec.source.kustomize.version on every Application | Remote ref bug | Breaks apps needing Kustomize 5, and leaving 5.x as default or registered leaves it open |
Restrict Application get, or block the upload endpoint | Upload path only | A Kustomization committed to Git is still built on the next sync |
The project says the remote ref bug has no complete workaround besides upgrading. The 4.5.7 pin also postdates Kustomize 4.1.0, which first passes configHome to Helm, so do not count it against the Helm bug.
Look back. The advisories publish no indicators of compromise, so this is my reading of the mechanism, not project guidance. Search Kustomizations for remote ref or version values beginning with a hyphen, for file:// remotes, and for helmGlobals.configHome alongside a .data/plugins directory. Review manifestsWithFiles calls from identities with no reason to make them, and look for command output in manifest-generation errors. On a real hit, treat the repository credentials as exposed and rotate them.
The renderer is part of your control plane
A GitOps controller is trusted to turn what is in Git into what runs in a cluster, and to do that it runs third-party tools over files written by many people. Rendering is not a harmless step before the real work: it can mean running commands chosen by whoever wrote the repository.
The advisories stop at repository credentials and process access. My own read is that a token with write access to a repo Argo CD syncs is a short path to the cluster, so scope those tokens to read wherever you can. Stop handing out Application get as harmless, and treat write access to any repo an Application builds as a privileged grant, for the same reason your CI pipeline is production.
Both bugs came in through a bump of a bundled tool and sat there for roughly three and a half and five and a half years. An Argo CD version number does not tell you which Kustomize you run, so that belongs in your inventory too, because you cannot secure what you cannot list. Dwaar discovers what you ship from source control, registries and cloud accounts, scans it, and keeps the results in one findings list.
Today, write down one line for each Argo CD instance: its version, every registered Kustomize version, whether --enable-helm is set, and who holds Application get. Then find other pipelines running kustomize build on repositories you do not control, because Argo CD's Git wrapper does not protect them.
References
- A Kustomize remote ref can run commands in the repo-server, Argo CD project, 2026-10-07
- A Kustomize Helm config home can run commands in the repo-server, Argo CD project, 2026-10-07
- Argo CD v3.3.15 release, Argo CD project, 2026-10-06
- Argo CD v3.4.10 release, Argo CD project, 2026-10-06
- Argo CD v3.5.4 release, Argo CD project, 2026-10-06
- Argo CD v3.6.0-rc2 release, Argo CD project, 2026-10-06
