CVE-2026-113708: Flaw in argoproj argo-cd Scores 9.9 on CVSS
A newly published critical vulnerability in argoproj argo-cd carries a CVSS score of 9.9. Here is what is affected and how to respond.
Key points
- CVE-2026-113708 affects argoproj argo-cd.
- CVSS 9.9 (Critical).
- No exploitation confirmed yet.
argoproj argo-cd is affected by CVE-2026-113708, a security flaw that the National Vulnerability Database rates 9.9 out of 10.
At a glance
- CVE
- CVE-2026-113708
- Product
- argoproj argo-cd
- CVSS
- 9.9 Critical
- Weakness
- CWE-88
- Exploited
- No known exploitation
What is the vulnerability?
The NVD entry states: 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/
Affected versions
| Vendor | Product | Versions |
|---|---|---|
| Argoproj | argo-cd | >= 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 |
CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H.
Is it being exploited?
There is no public confirmation of exploitation at the time of publication. It does not appear in CISA's Known Exploited Vulnerabilities catalog. We will update this report if that changes.
What should you do?
- Identify whether the affected product and versions run in your environment.
- Apply the vendor update listed in the advisory as soon as it is available.
- Limit network exposure of the affected service until it is patched.
- Monitor the vendor advisory for updated guidance or exploitation reports.
What to do and how to stay safe: CVE-2026-113708
- Vulnerability severity scores ignore your specific architecture and context.
- Exploitability depends on network exposure and user behavior, not just code flaws.
- Prioritization requires continuous asset inventory and threat intelligence alignment.
Risk-based vulnerability management focuses your limited resources on the flaws that actually threaten your business. Start by mapping your critical assets and checking for active exploits to prioritize your backlog.
Step-by-step guide: Risk-Based Vulnerability Management: Prioritize Fixes by Actual Danger
General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
What is CVE-2026-113708?
CVE-2026-113708 is a CWE-88 vulnerability in argoproj argo-cd.
How severe is CVE-2026-113708?
It has a CVSS score of 9.9 Critical.
Is CVE-2026-113708 being exploited?
There is no public confirmation of exploitation at the time of publication.
