# Argo v3.4.14

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

Security 2 · Important fixes 1 · Dependency updates 3

## Check before upgrading

### Upgrade guide

- **Documentation for upgrading across minor versions**
  > ## Upgrading
  > 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 (2)

### Argo CD regex memory exhaustion fixed

- Affects: Argo CD projects using regexes in `AppProject spec.sourceNamespaces`
- [CVE-2026-77299](https://www.cve.org/CVERecord?id=CVE-2026-77299)

Before the upgrade, a regex with a large fixed-count quantifier on a zero-width subexpression could amplify memory without bound and OOM the application controller or API server. Matching now uses a bounded backtracking stack, and a match that exceeds the limit is treated as no match.

> * abbea8da4ed68afa3023ed7e583216ea949b40aa: fix(deps): upgrade dlclark/regexp2 to v2.13.0 (CVE-2026-77299) (#31005) (#31026) (@nmirasch)

### AppProject destination deny-pattern precedence fixed

- Affects: AppProjects with `!name` or `!server` destination deny patterns

When the namespace matched and a `!name` or `!server` pattern matched the destination while the other identifier matched, the other identifier’s allow match could previously permit a destination despite the explicit denial. A matching deny now vetoes the destination before allow evaluation; a deny pattern that does not match another cluster does not block an otherwise permitted destination.

> * 5177bd6e981ba56356661f1a2b2fd7dfe0e47f21: fix: AppProject destination deny (!name / !server) vetoes when it positively matches (cherry-pick #30884 for 3.4) (#30895) (@argo-cd-cherry-pick-bot[bot])

## Important fixes (1)

### Application controller stops retaining decoded OpenAPI documents

- Affects: Managed clusters with cached OpenAPI schemas (Inferred)

Before the fix, the controller kept each cluster’s full decoded OpenAPI v2 document in memory for as long as the cluster was cached. Now the decoded document can be garbage collected after `LoadOpenAPISchema` returns, while the models needed for `LookupResource()` and the GVK parser are retained.

> * b117092584d936f1ab05204eaa4c170b1bcb0877: fix(gitops-engine): stop retaining the decoded OpenAPI document per cluster (#30810) (cherry-pick #30811 for 3.4) (#30833) (@argo-cd-cherry-pick-bot[bot])

## Dependency updates (3)

3 more, none mentioning security

- `* 5659a9325f5e63f8fb7d986f3f92ee017b42d0f3: chore(deps): bump github.com/go-jose/go-jose/v4 from 4.1.4 to 4.1.6 [3.4] (#30918) (@ranakan19)`
- `* d14ad30d9f46328b68f816f0d139de7ae7d5192e: chore(deps): update group golang to v1.26.11 (release-3.4) (#30923) (@argoproj-renovate[bot])`
- `* 574fc47246478dfe0d8f365fd628c260a9dad8e9: chore(dep): upgrade git-lfs dependency from v3.7.1 to v3.8.1 (#31051) (#31053) (@anandf)`

---

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