Key points
- CVE-2026-113708 is rated Critical with a CVSS score of 9.9.
- Affected versions include 2.7.0 through 3.3.14 and specific 3.4, 3.5, and 3.6 releases.
- Patches are available in versions 3.3.15, 3.4.10, 3.5.4, and 3.6.0-rc2.
Argo CD versions from 2.7.0 up to 3.3.15, 3.4.10, 3.5.4, and 3.6.0-rc2 contain a critical remote code execution flaw. The vulnerability exists in how the tool handles Kustomize configurations. Attackers can execute commands inside the argocd-repo-server container by supplying malicious URL parameters. This issue has been assigned CVE-2026-113708 and carries a CVSS score of 9.9.
In plain English
The bug occurs because Kustomize passes query values from remote resource URLs directly to the git fetch command. It fails to include an end-of-options separator. If an attacker provides a value starting with a hyphen, git interprets it as a command-line flag. This allows the injection of the --upload-pack option, which triggers command execution within the repo-server process.
The background
This execution happens when the remote resource uses a local transport like file://. Git does not execute commands for https:// remotes. The local transport stays within the pod, so blocking network egress does not stop the attack. The command runs with the permissions of the repo-server user. This allows access to repository credentials and other data accessible to that process.
What changes now
Attackers can exploit this by committing a malicious Kustomization to a Git repository that an Argo CD Application builds. They can also upload files via the POST /api/v1/applications/manifestsWithFiles endpoint. This upload path requires only Application get permission on an existing Application. It does not require Application update, sync permission, or repository write access.
Who needs to act first
Teams should prioritize updating systems that expose the manifest generation API to untrusted users or repositories. Check whether your Argo CD instance allows external contributions to Git repositories used for applications. Roll out the patch to environments with high-value credentials first. Test the update in a staging environment to ensure application stability. Back up current configurations before applying changes. If immediate patching is not possible, restrict access to the manifest generation endpoints.
What to do and how to stay safe: Argo CD
- Verify if your Argo CD version falls within the affected range listed in the advisory.
- Review Application permissions to ensure only trusted users have get access to sensitive apps.
- Monitor repo-server logs for unexpected command executions or manifest generation errors.
- Apply the vendor-provided update once you have validated it in a test environment.
Step-by-step guide: 7 Configuration Errors That Expose Systems to Zero-Day Exploits
General security guidance from the Vuln Post newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
Which Argo CD versions are vulnerable to CVE-2026-113708?
Versions from 2.7.0 until 3.3.15, 3.4.10, 3.5.4, and 3.6.0-rc2 are affected.
Is there a fix available for this vulnerability?
Yes, the issue is fixed in versions 3.3.15, 3.4.10, 3.5.4, and 3.6.0-rc2.
Can blocking network traffic prevent this attack?
No, the local transport does not leave the pod, so blocking egress does not prevent execution.
