argoproj argo-cd Path Traversal Flaw (CVE-2026-113672) Rated CVSS 9.9
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-113672 affects argoproj argo-cd.
- CVSS 9.9 (Critical).
- No exploitation confirmed yet.
argoproj argo-cd is affected by CVE-2026-113672, a path traversal that the National Vulnerability Database rates 9.9 out of 10.
At a glance
- CVE
- CVE-2026-113672
- Product
- argoproj argo-cd
- CVSS
- 9.9 Critical
- Weakness
- path traversal
- Exploited
- No known exploitation
What is the vulnerability?
The NVD entry states: Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. From 0.9.0 until 3.3.15, 3.4.10, 3.5.4, and 3.6.0-rc2, the repo-server evaluates .jsonnet files with an importer that does not confine import, importstr, or importbin to the repository root. Absolute paths, parent-directory traversal, and repository symlinks can open any file readable by the repo-server, including /proc/self/environ, projected service-account tokens, mounted private keys, and repository credentials. Although generated Secrets are redacted, placing imported contents in a ConfigMap returns the data to the caller. Using importstr on a non-terminating device such as /dev/zero can exhaust repo-server memory. An attacker can commit a .jsonnet file to a Git repository used by an Application or upload the file through POST /api/v1/applications/manifestsWithFiles, also exposed by argocd app diff --local --s
Affected versions
| Vendor | Product | Versions |
|---|---|---|
| Argoproj | argo-cd | >= 0.9.0, < 3.3.1, >= 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-113672
- 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-113672?
CVE-2026-113672 is a path traversal vulnerability in argoproj argo-cd.
How severe is CVE-2026-113672?
It has a CVSS score of 9.9 Critical.
Is CVE-2026-113672 being exploited?
There is no public confirmation of exploitation at the time of publication.
