CVE-2026-113672
Last modified
CVE-2026-113672 is a critical-severity vulnerability rated 9.9/10 on the CVSS scale. 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.
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.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| 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 |
References
Timeline
- Published
- Last Modified
- Status
- Undergoing Analysis
Frequently Asked Questions
What is CVE-2026-113672?
How severe is CVE-2026-113672?
How do I fix CVE-2026-113672?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-113667ApostropheCMS is an open-source Node.js content management s…5.3
- CVE-2026-113668ApostropheCMS is an open-source Node.js content management s…5.3
- CVE-2026-113669ApostropheCMS is an open-source Node.js content management s…5.3
- CVE-2026-11367The PixMagix – WordPress Image Editor plugin for WordPress i…6.5
- CVE-2026-113670Rejected reason: This CVE is a duplicate of another CVE.
- CVE-2026-113671ApostropheCMS is an open-source Node.js content management s…4.3
- CVE-2026-113676Froxlor from 0.10.0 before 2.3.15 contains an authorization …4.3
- CVE-2026-113677Froxlor from 0.10.0 before 2.3.15 contains a missing authori…5.4
- CVE-2026-113678Froxlor before 2.3.15 contains a symlink following vulnerabi…9.9
- CVE-2026-113679HarfBuzz 8.0.0 through 14.6.0 contains an out-of-bounds writ…7
- CVE-2026-11368The Bluetooth host ATT layer (subsys/bluetooth/host/att.c) a…6.5
- CVE-2026-113680HarfBuzz from 8.0.0 through 14.6.0 contains a NULL pointer d…5.5
Are you affected by CVE-2026-113672?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
