Argo CD: A Kustomize remote ref can run commands in the repo-server

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

• CVE-2026-113708: 0.67% estimated exploitation activity in the next 30 days; percentile 51.90 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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, 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…

Published by the source

29 Oct 2026, 08:38 UTC

Last modified by the source

29 Oct 2026, 10:45 UTC

Source last checked

30 Oct 2026, 07:30 UTC

1. Revision 1 · created · 30 Oct 2026

   Published from osv record BIT-argo-cd-2026-113708

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-113708

Advisory: Argo CD: A Kustomize remote ref can run commands in the repo-server
IDs: CVE-2026-113708
Record: https://patchnext.com/advisories/cve-2026-113708 (revision 1, source checked 30 Oct 2026, 07:30 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: argo-cd 3.5.4, 3.4.10, 3.3.15. A vendor fix does not mean a deployment is fixed.

## Affected components
- Bitnami argo-cd: affected >= 2.7.0, < 3.3.15; >= 3.4.0, < 3.4.10; >= 3.5.0, < 3.5.4; fixed in 3.5.4, 3.3.15, 3.4.10

## Suggested inspection (read-only)
- Bitnami argo-cd: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on argo-cd.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/BIT-argo-cd-2026-113708 (OSV record BIT-argo-cd-2026-113708 lists affected ranges: Bitnami argo-cd >=2.7.0 =3.4.0 =3.5.0 <3.5.4 (fixed))

Commands are suggestions: review each one before running it.