Argo CD: A Jsonnet import can read files from the repo-server

Exploitation

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

CVSS

not scored

EPSS

• CVE-2026-113672: 0.84% estimated exploitation activity in the next 30 days; percentile 57.80 (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 0.9.0 until 3.3.15, 3.4.10, 3.5.4, and 3.6.0, 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.…

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-113672

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

# Patch Next advisory brief: CVE-2026-113672

Advisory: Argo CD: A Jsonnet import can read files from the repo-server
IDs: CVE-2026-113672
Record: https://patchnext.com/advisories/cve-2026-113672 (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.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Bitnami argo-cd: affected >= 0.9.0, < 3.3.1; >= 3.4.0, < 3.4.10; >= 3.5.0, < 3.5.4; fixed in 3.5.4, 3.3.1, 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-113672 (OSV record BIT-argo-cd-2026-113672 lists affected ranges: Bitnami argo-cd >=0.9.0 =3.4.0 =3.5.0 <3.5.4 (fixed))

Commands are suggestions: review each one before running it.