Skip to main content
VulnerabilityPublished

CVE-2026-113708: argoproj argo-cd · Argument Injection

Affects argoproj argo-cdSource CVE Database V5

0

Not known to be exploited · CVSS 9.9 Critical · fixed in 3.6.0-rc2 : patch argoproj argo-cd as a priority.

Data as of 26 Oct 2026, 11:07 UTC

CVSS 3.1 base score
9.9Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.6.0-rc2, 3.5.4, 3.4.10 +1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 24 Oct 2026.

What to do

Upgrade argo-cd and argoproj/argo-cd to 3.6.0-rc2, 3.5.4, 3.4.10 or 3.3.15.

Affected software

ProductAffectedFixed in
argoprojargo-cdAffected
  • >=3.6.0-rc1 <3.6.0-rc2
Fixed in
  • 3.6.0-rc2
argoprojargo-cdAffected
  • >=3.5.0-rc1 <3.5.4
Fixed in
  • 3.5.4
argoprojargo-cdAffected
  • >=3.4.0-rc1 <3.4.10
Fixed in
  • 3.4.10
argoprojargo-cdAffected
  • >=2.7.0 <3.3.15
Fixed in
  • 3.3.15
GitHubargoproj/argo-cdpkg:github/argoproj/argo-cdOther threatsAffected
  • >=2.7.0 <3.3.15
  • >=3.4.0-rc1 <3.4.10
  • >=3.5.0-rc1 <3.5.4
  • >=3.6.0-rc1 <3.6.0-rc2
Fixed in
  • 3.3.15
  • 3.4.10
  • 3.5.4
  • 3.6.0-rc2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Argo CD to one of the fixed versions: 3.3.15, 3.4.10, 3.5.4, or 3.6.0-rc2. These versions include the necessary fix to properly neutralize argument delimiters and prevent command injection. Replacing only the Kustomize component with a newer version is insufficient to mitigate this issue. No other mitigations are indicated by the vendor advisory.

Description

Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. From 2.7.0 until 3.3.15, 3.4.10, 3.5.4, and 3.6.0-rc2, Kustomize passes ref or version query values from remote resource, base, or component URLs to git fetch without an end-of-options separator. A leading-hyphen value can be parsed as --upload-pack and execute a command inside argocd-repo-server when the remote uses a local transport such as file://. Git does not run the supplied command for an https:// remote. The local transport does not leave the pod, so blocking repo-server egress does not prevent the execution. The command runs as the repo-server user, can read repository credentials and other process-accessible data, and can return output through manifest-generation errors. An attacker can commit a Kustomization to a Git repository that an Application builds or upload files through POST /api/v1/applications/manifestsWithFiles, also exposed by argocd app diff --local --server-side-generate. The upload path requires only Application get permission on an existing Application, without Application update or sync permission or repository write access. Kustomize 5.0.0 introduced acceptance of file://, whereas 4.5.7 rejects that transport; replacing the affected Kustomize with a newer version alone does not correct the missing option separator. This issue is fixed in versions 3.3.15, 3.4.10, 3.5.4, and 3.6.0-rc2.

References

Community reviews

Loading reviews…