# Argo v3.3.15

2026-10-06 · [Original release notes](https://github.com/argoproj/argo-cd/releases/tag/v3.3.15) · [Full summary](https://ratatosk.io/en/releases/argo/v3.3.15)

Security 10 (critical 5 · high 2) · Important fixes 10 · Dependency updates 2 · Other changes 1

## Check before upgrading

### Upgrade guide

- **Upgrading from a different minor version**
  > If upgrading from a different minor version, be sure to read the [upgrading](https://argo-cd.readthedocs.io/en/stable/operator-manual/upgrading/overview/) documentation.

## Security (10)

### [critical] Kustomize remote URL command execution fixed

- Affects: Kustomize applications using remote resources, bases, or components (Inferred)
- [CVE-2026-113708](https://www.cve.org/CVERecord?id=CVE-2026-113708), [GHSA-9v9p-x54c-58gc](https://github.com/argoproj/argo-cd/security/advisories/GHSA-9v9p-x54c-58gc)

During manifest generation, a remote URL’s `ref` or `version` value beginning with `-` could be parsed as a Git option and run a command in repo-server when using a local transport such as `file://`. After the upgrade, remote bases continue to work, but the URL and ref cannot be parsed as Git options.

> * CRITICAL: A Kustomize remote ref can run commands in the repo-server ([GHSA-9v9p-x54c-58gc](https://github.com/argoproj/argo-cd/security/advisories/GHSA-9v9p-x54c-58gc))

### [critical] Kustomize Helm plugin execution blocked

- Affects: Kustomize Helm chart builds using plugins registered from `helmGlobals.configHome`
- [CVE-2026-113709](https://www.cve.org/CVERecord?id=CVE-2026-113709), [GHSA-fw5c-w8rc-j7fx](https://github.com/argoproj/argo-cd/security/advisories/GHSA-fw5c-w8rc-j7fx)

When Helm rendering was enabled, a repository-controlled `helmGlobals.configHome` could let Helm load and run a downloader plugin from that directory when its protocol was used. Kustomize now uses empty Helm config and data directories, so those plugins cannot run, while ordinary `http`, `https`, and `oci` chart repositories continue to work.

> * CRITICAL: A Kustomize Helm config home can run commands in the repo-server ([GHSA-fw5c-w8rc-j7fx](https://github.com/argoproj/argo-cd/security/advisories/GHSA-fw5c-w8rc-j7fx))
> * Kustomize builds that render Helm charts no longer honor `helmGlobals.configHome`. Ordinary `http`, `https`, and `oci` chart repositories still work. Builds that depended on a Helm plugin registered from that directory will not ([GHSA-fw5c-w8rc-j7fx](https://github.com/argoproj/argo-cd/security/advisories/GHSA-fw5c-w8rc-j7fx)).

### [critical] Jsonnet imports restricted to regular files inside the repository

- Affects: Applications that use `.jsonnet` files (Inferred)
- [CVE-2026-113672](https://www.cve.org/CVERecord?id=CVE-2026-113672), [GHSA-m3vr-7329-44ww](https://github.com/argoproj/argo-cd/security/advisories/GHSA-m3vr-7329-44ww)

When Argo CD evaluated `.jsonnet` files, the repo-server could read any path accessible to its process, including paths outside the repository and device files; importing `/dev/zero` could exhaust memory. Now imports outside the repository and non-regular files are rejected, while imports within the repository continue to work.

> * CRITICAL: A Jsonnet import can read files from the repo-server ([GHSA-m3vr-7329-44ww](https://github.com/argoproj/argo-cd/security/advisories/GHSA-m3vr-7329-44ww))

### [critical] `AppProject` checks enforced for `PreDelete` and `PostDelete` hooks

- Affects: Applications using `PreDelete` or `PostDelete` hooks in `AppProject`s with destination or resource restrictions (Inferred)
- [CVE-2026-77459](https://www.cve.org/CVERecord?id=CVE-2026-77459), [GHSA-fmxq-cgp8-87wp](https://github.com/argoproj/argo-cd/security/advisories/GHSA-fmxq-cgp8-87wp)

Before this release, these hooks bypassed checks for destination namespaces and servers and resource allow/deny lists, so deleting an Application could create a hook on the destination cluster.

> * CRITICAL: AppProject restrictions bypassed by PreDelete/PostDelete resource hooks ([GHSA-fmxq-cgp8-87wp](https://github.com/argoproj/argo-cd/security/advisories/GHSA-fmxq-cgp8-87wp), CVE-2026-77459)

### [critical] Eight Argo CD security flaws fixed

- Affects: Kustomize remote bases; Kustomize Helm with `--enable-helm`; Jsonnet; PreDelete or PostDelete hooks; local username/password accounts; SSH Git repositories with a proxy URL; proxy extensions with Applications-in-any-namespace enabled; or OCI image sources
- [CVE-2025-61560](https://www.cve.org/CVERecord?id=CVE-2025-61560), [CVE-2026-113672](https://www.cve.org/CVERecord?id=CVE-2026-113672), [CVE-2026-113708](https://www.cve.org/CVERecord?id=CVE-2026-113708), [CVE-2026-113709](https://www.cve.org/CVERecord?id=CVE-2026-113709), [CVE-2026-55797](https://www.cve.org/CVERecord?id=CVE-2026-55797), [CVE-2026-77459](https://www.cve.org/CVERecord?id=CVE-2026-77459), [GHSA-4439-h7jw-5cjj](https://github.com/argoproj/argo-cd/security/advisories/GHSA-4439-h7jw-5cjj), [GHSA-9v9p-x54c-58gc](https://github.com/argoproj/argo-cd/security/advisories/GHSA-9v9p-x54c-58gc), [GHSA-fmxq-cgp8-87wp](https://github.com/argoproj/argo-cd/security/advisories/GHSA-fmxq-cgp8-87wp), [GHSA-fw5c-w8rc-j7fx](https://github.com/argoproj/argo-cd/security/advisories/GHSA-fw5c-w8rc-j7fx), [GHSA-g3ff-q88g-chrj](https://github.com/argoproj/argo-cd/security/advisories/GHSA-g3ff-q88g-chrj), [GHSA-j6cw-g6p4-7hch](https://github.com/argoproj/argo-cd/security/advisories/GHSA-j6cw-g6p4-7hch), [GHSA-m3vr-7329-44ww](https://github.com/argoproj/argo-cd/security/advisories/GHSA-m3vr-7329-44ww), [GHSA-w996-f2wq-x9c6](https://github.com/argoproj/argo-cd/security/advisories/GHSA-w996-f2wq-x9c6)

Previously, a Git-option-like `ref` or `version` on a Kustomize remote (notably a `file://` remote), a repository-controlled Helm config home during Helm rendering, or an out-of-root or non-regular Jsonnet import could run commands or read repo-server files. Deleting an Application with hooks could bypass AppProject checks, concurrent logins could exceed failure limits, shell metacharacters in an SSH proxy URL could execute commands, extension authorization could ignore the Application namespace, and oversized OCI manifests could exhaust repo-server memory; this release blocks those paths, including by rejecting OCI manifests over 4 MiB.

> * 1149cdc6e932208c4402183cc3d7b7485239940c: fix(security): coordinated security fixes (release-3.3) (#30040) (@crenshaw-dev)

### [high] Concurrent local-login rate-limit bypass fixed

- Affects: Argo CD deployments with local username/password accounts enabled, including the built-in `admin` account; not SSO or OIDC logins
- [CVE-2025-61560](https://www.cve.org/CVERecord?id=CVE-2025-61560), [GHSA-4439-h7jw-5cjj](https://github.com/argoproj/argo-cd/security/advisories/GHSA-4439-h7jw-5cjj)

Concurrent password-login requests for the same username could check the failure count before it was incremented, allowing more guesses than the configured limit (5 failures per 5-minute window by default). Now the count is updated before the next same-user attempt is checked.

> * HIGH: Login failure rate limit can be bypassed via concurrent requests ([GHSA-4439-h7jw-5cjj](https://github.com/argoproj/argo-cd/security/advisories/GHSA-4439-h7jw-5cjj), CVE-2025-61560)

### [high] Argo CD SSH repository proxy command injection fixed

- Affects: SSH Git repositories with a proxy URL (`http`, `https`, or `socks5`), not HTTPS Git repositories using an HTTP proxy
- [CVE-2026-55797](https://www.cve.org/CVERecord?id=CVE-2026-55797), [GHSA-j6cw-g6p4-7hch](https://github.com/argoproj/argo-cd/security/advisories/GHSA-j6cw-g6p4-7hch)

When Argo CD cloned or fetched one, shell metacharacters in the proxy host could break out of the `ProxyCommand` and run commands in repo-server. The proxy host and port are no longer passed through a shell.

> * HIGH: Command injection via a repository proxy URL on SSH Git repositories ([GHSA-j6cw-g6p4-7hch](https://github.com/argoproj/argo-cd/security/advisories/GHSA-j6cw-g6p4-7hch), CVE-2026-55797)

### [medium] Proxy extension Application authorization check fixed

- Affects: installations with proxy extensions and Applications in any namespace enabled
- [GHSA-g3ff-q88g-chrj](https://github.com/argoproj/argo-cd/security/advisories/GHSA-g3ff-q88g-chrj)

An authenticated user with Application `get` on `project/name` or `project/*` could invoke an extension for a same-named Application in another namespace, even when a namespace-qualified deny rule applied. The extension check now builds the policy object consistently with the Application API, using the Argo CD namespace as the default.

> * MODERATE: Extension proxy RBAC ignores application namespace when applications-in-any-namespace is enabled ([GHSA-g3ff-q88g-chrj](https://github.com/argoproj/argo-cd/security/advisories/GHSA-g3ff-q88g-chrj))

### [medium] Argo CD rejects oversized OCI manifests

- Affects: Applications with an OCI registry source
- [GHSA-w996-f2wq-x9c6](https://github.com/argoproj/argo-cd/security/advisories/GHSA-w996-f2wq-x9c6)

Previously, downloading a sufficiently large manifest while rendering an Application or loading its source metadata could exhaust repo-server memory; Kubernetes would kill the process, stopping manifest generation for every Application until the pod restarted.

> * An OCI manifest larger than 4 MiB is now rejected ([GHSA-w996-f2wq-x9c6](https://github.com/argoproj/argo-cd/security/advisories/GHSA-w996-f2wq-x9c6)).
> * MODERATE: An oversized OCI manifest can exhaust repo-server memory ([GHSA-w996-f2wq-x9c6](https://github.com/argoproj/argo-cd/security/advisories/GHSA-w996-f2wq-x9c6))

### UI `js-yaml` merge-chain CPU issue fixed

- Affects: the `/ui` component using `js-yaml`
- [CVE-2026-59869](https://www.cve.org/CVERecord?id=CVE-2026-59869), [GHSA-52cp-r559-cp3m](https://github.com/advisories/GHSA-52cp-r559-cp3m)

In `js-yaml` versions 4.0.0 before 4.3.0, parsing a chain of mappings that merged the previous mapping could consume quadratic CPU time. The UI now uses version 4.3.1, beyond the advisory's stated fix version; the advisory describes a 10K merged-key limit as protection against the issue.

> * d697764be580f902fb73587bbceb63c4c268285e: chore(deps): bump js-yaml to 4.3.1 in /ui for CVE-2026-59869 (release-3.3) (#29386) (@aali309)

## Important fixes (10)

### [Silent failure] KubeVirt stopped VirtualMachine health status fixed

- Affects: KubeVirt `VirtualMachine` resources declared stopped with `spec.running: false` or `spec.runStrategy: Halted`, with no instance in `status.created`

Previously, these resources were reported as `Suspended` with the message `Stopped`, which could leave an Application sync running indefinitely. They now report `Healthy` once no created instance remains, stay `Progressing` while an instance is stopping, and retain existing behavior for other run strategies.

> * c397ddcc9d1669d5339548b8d42bb89ed7db1da6: fix(health): a KubeVirt VirtualMachine declared stopped is Healthy (cherry-pick #29664 for 3.3) (#29667) (@argo-cd-cherry-pick-bot[bot])

### Crossplane and Upbound health checks fixed for resources without conditions

- Affects: Crossplane and Upbound resources evaluated by bundled health checks

While a resource was provisioning without `.status`, its health check could report `Healthy` before checking whether its kind was allowlisted. Now only allowlisted kinds without `status.conditions` report `Healthy`; other resources without conditions remain `Progressing`.

> * 990ea5694003dc924b03bd6e72a48c6a80273719: fix(resource_customizations): Crossplane MRs should report Progressing (not Healthy) whilst provisioning [ISSUE:  #29381] (cherry-pick #29382 for 3.3) (#29519) (@argo-cd-cherry-pick-bot[bot])

### [Silent failure] Sync controller stale revision reuse fixed

- Affects: Argo CD Application sync operations targeting `HEAD`

When a sync targeting `HEAD` failed and was retried, including during a multi-stage sync, a JSON Merge Patch could leave the previous `operation.sync.revision` in place. The retry could then apply old manifests and silently roll the cluster back; the controller now replaces the entire `/status/operationState` subtree so an empty or omitted revision does not inherit the stale value.

> * a050c4f2d45514b5fb39b3a9d7e89f12cb5d6179: fix(sync): correctly set operationState values on retry (#26530) (cherry-pick #28778 for 3.3) (#29433) (@omkar619-dev)

### Source Hydrator destination resolution corrected

- Affects: Applications with a Source Hydrator

In 3.3, the destination repo is the dry source repo. The displayed branch is `hydrateTo.targetBranch` when set, otherwise the sync source branch.

> * 2cffaf528edb1e3fb8730f2075d3f128623ff4a0: fix(ui): use hydrateTo branch name when set (cherry-pick #29562 for 3.3) (#29565) (@crenshaw-dev)

### `GRPCRoute` health checks use current-generation parent conditions

- Affects: `gateway.networking.k8s.io/GRPCRoute` resources

When parent conditions have an `observedGeneration` that differs from `metadata.generation`, stale success could report `Healthy` before the controller observed the new generation, while an old failure could continue to report `Degraded` after it was resolved. Stale conditions no longer determine health; if all parent conditions are stale, the health check reports `Progressing`.

> * 0900428b854ce81e5a129a2ea7f74aebdb1efd81: fix: GRPCRoute health check ignores stale observedGeneration conditions (#28086) (cherry-pick #28087 for 3.3) (#29516) (@argo-cd-cherry-pick-bot[bot])

### [Silent failure] Cluster API health check no longer misreports provisioning as degraded

- Affects: Cluster API `Cluster` resources with `Ready: False` and severity `Info`

During normal provisioning, a `Ready: False` condition with severity `Info` was treated as `Degraded`. It now reports `Progressing` for that wait, while genuine `Error` conditions still degrade.

> * ec1fc4524dea1880e03b4d0a31d39d7fe441ddd9: fix: don't degrade Cluster API Cluster health while Ready is False during provisioning (cherry-pick #29237 for 3.3) (#29272) (@argo-cd-cherry-pick-bot[bot])

### GrafanaFolder health check handles UID mismatch polarity correctly

- Affects: GrafanaFolder resources evaluated with Grafana Operator v5.25.0

Previously, `FolderUIDMismatch=False` with reason `ConsistentUID` could mark a healthy folder as degraded. It now remains healthy, while `FolderUIDMismatch=True` marks a UID mismatch as degraded; other false conditions such as `FolderSynchronized=False` still follow the existing failure behavior.

> * 601f6112620b17708ffd65720ce055f42e3b7181: fix: handle GrafanaFolder negative-polarity condition (#29395) (cherry-pick #29397 for 3.3) (#29522) (@argo-cd-cherry-pick-bot[bot])

### Repo-server tgz stream temporary-directory leak fixed

- Affects: repo-server tgz archive streams, including CMP sidecar and manifest streams

Each stream to a Config Management Plugin (CMP) sidecar left an empty directory in `/tmp`; over time, these could exhaust filesystem inodes and cause failures. The owned temporary directory is now removed after streaming and on compression or downstream-send errors, including manifest-stream send failures.

> * c6e39fdecc8b9f59d810325ad955746a5fee38db: fix(cmp): clean up tgz stream temporary directories (#29148) (cherry-pick #29156 for 3.3) (#29774) (@argo-cd-cherry-pick-bot[bot])

### `FlinkDeployment` health check reports initially suspended jobs as healthy

- Affects: `FlinkDeployment` resources with `spec.job.state: suspended` before their first deployment and no recorded `lastReconciledSpec`

Previously, these resources could remain `Progressing` indefinitely, leaving their parent Application unsettled. They now report `Healthy`; after a prior deployment, suspended deployments remain `Progressing` while they converge.

> * 33ffc7d654d31d434ff844fb2d60322f182b0448: fix(health): report suspended FlinkDeployment as healthy (#26818) (cherry-pick #28995 for 3.3) (#29526) (@argo-cd-cherry-pick-bot[bot])

### Source hydrator notes-ref lock errors retried

- Affects: source hydration across application-controller shards

When multiple shards push concurrently to the same `refs/notes/hydrator.metadata` ref, a `cannot lock ref` error previously made hydration fail instead of entering the retry path. These pushes now re-fetch the notes ref and retry; other non-retryable errors remain permanent failures.

> * 3abe9eb1d7a1fc62b07231c1de811cd59fa10579: fix(hydrator): retry notes push on cannot lock ref errors (cherry-pick #28469 for 3.3) (#29906) (@argo-cd-cherry-pick-bot[bot])

## Dependency updates (2)

2 more, none mentioning security

- `* 3249c5cdb0a5d199f42aef23ffba7b66d52a5db4: chore(deps): bump go.opentelemetry.io/otel from 1.43 to 1.44 (release-3.3) (#29763) (@nmirasch)`
- `* 874a17c78c4e6d6bc3a4f213947717c41875f7fe: chore(deps): bump golang.org/x/crypto to 0.55.0 (release-3.3) (#29824) (@akhilnittala)`

## Other changes (1)

- Live Manifest viewer preserves view state on refresh

---

Summaries are produced by AI, so they can be wrong, and they are provided without warranty.
