Is CVE-2026-113708 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-113708 being exploited in the wild.

How severe is CVE-2026-113708?

Critical severity, with a CVSS score of 9.9, published 20 October 2026.

Which products and versions are affected?

Argoproj Argo CD 2.7.0 through 3.3.14, 3.4.0 through 3.4.9, 3.5.0 through 3.5.3, 3.6.0-rc1 and earlier.

Is there a fix for CVE-2026-113708?

Yes: fixed in Argo CD 3.3.15, 3.4.10, 3.5.4, 3.6.0-rc2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-113708 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2026-113708?

Check whether you run Argoproj Argo CD at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-113708: Argo CD command injection in Kustomize via file:// transport

CVE-2026-113708 · Severity: critical · CVSS 9.9 · Published 2026-10-20

Argo CD is a GitOps continuous delivery tool that automates application deployment to Kubernetes clusters. Attackers can execute arbitrary commands on the repo-server pod by committing a malicious Kustomization file or uploading files through the manifest API, potentially compromising repository credentials and sensitive data. The vulnerability affects versions 2.7.0 through 3.5.x and requires only minimal permissions to exploit.

Quick answers

Is CVE-2026-113708 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-113708 being exploited in the wild.
How severe is CVE-2026-113708?: Critical severity, with a CVSS score of 9.9, published 20 October 2026.
Which products and versions are affected?: Argoproj Argo CD 2.7.0 through 3.3.14, 3.4.0 through 3.4.9, 3.5.0 through 3.5.3, 3.6.0-rc1 and earlier.
Is there a fix for CVE-2026-113708?: Yes: fixed in Argo CD 3.3.15, 3.4.10, 3.5.4, 3.6.0-rc2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-113708 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-113708?: Check whether you run Argoproj Argo CD at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: Argo CD 3.3.15, 3.4.10, 3.5.4, 3.6.0-rc2

Technical details

Kustomize passes unsanitized ref or version query parameters from remote resource URLs to git fetch without an end-of-options separator, allowing leading-hyphen values to be interpreted as git options like --upload-pack. When the remote uses a file:// transport (supported by Kustomize 5.0.0+), git executes the supplied command inside the repo-server pod. The command runs as the repo-server user with access to repository credentials and can return output through manifest-generation errors. Exploitation requires either committing to a repository or using the POST /api/v1/applications/manifestsWithFiles endpoint with only Application get permission.

Affected products

Argoproj Argo CD 2.7.0 through 3.3.14, 3.4.0 through 3.4.9, 3.5.0 through 3.5.3, 3.6.0-rc1 and earlier

Timeline

2026-10-20: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.