# CVE-2026-113672: Argo CD: A Jsonnet import can read files from the repo-server


- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 20 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** BIT-argo-cd-2026-113672

## What is CVE-2026-113672?

CVE-2026-113672 is a critical vulnerability in argoproj argo-cd, published on 20 Oct 2026. 

### Official description

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 --server-side-generate. Directory applications evaluate every .jsonnet file in the application directory. The upload path requires only Application get permission on an existing directory Application, without Application update or sync permission or repository write access. This issue is fixed in versions 3.3.15, 3.4.10, 3.5.4, and 3.6.0-rc2.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-113672?

1 open source package ship an affected version, including argo-cd.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `argo-cd` | Bitnami | From 0.9.0 | 3.3.1, 3.4.10, 3.5.4 |

## How do I fix CVE-2026-113672?

Upgrade argo-cd to a fixed version for your release line: 3.3.1, 3.4.10 or 3.5.4.

## Is CVE-2026-113672 being exploited?

There is no known exploitation of CVE-2026-113672 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-113672 and fix it if it is affected.

What it is: CVE-2026-113672 is a critical vulnerability in argoproj argo-cd, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-113672 in the wild and no public exploit code.

Affected packages and fixed versions:
- argo-cd (Bitnami): affected from 0.9.0; fixed in 3.3.1, 3.4.10, 3.5.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-113672/ (Markdown: https://insights.sbomify.com/CVE-2026-113672/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-113672
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-113672
- OSV: https://osv.dev/vulnerability/CVE-2026-113672

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-113672/
Summaries are generated and may contain mistakes; the official description above is the record.