Argo CD v3.3.18 was published on October 22, 2026. This is a single change patch release: a security fix that removes a compromised emudhra CA certificate from the trust Argo CD ships with. If you run 3.3.x in production, this is the release to apply this week.
The full release notes and downloads are on the GitHub release page.
What changed ¶
The changelog holds exactly one functional commit:
4692a04fix(security): emudhra CA certs compromise for release 3.3 (#30349)
That commit pulls the emudhra root CA certificates out of the certificate bundle that Argo CD embeds for TLS verification and repo server connections. The emudhra CA hierarchy was publicly reported as compromised, which means any certificate chaining to those roots cannot be trusted. Argo CD uses its trust store when validating external HTTPS endpoints, including Helm repositories and cluster connections, so a stale trusted root there is a real supply chain exposure, not a cosmetic cleanup.
The rest of the release is housekeeping. One bot commit bumps the version string to 3.3.18 on the release-3.3 branch. There is nothing else in the notes worth reciting.
Why this matters foroperators ¶
Argo CD acts as a TLS client in several paths:
- The repo server fetching Helm charts and remote manifests over HTTPS.
- The application controller talking to cluster API servers with custom trust configuration.
- Webhook and OIDC endpoints reached by the API server.
Any of these paths that could validate a chain forged against the compromised emudhra roots becomes an attack surface. A patch that narrows the embedded trust store cuts that off at the image level, which is faster than waiting on every downstream consumer to fix their own CA bundles. The tradeoff is the usual one: if you intentionally relied on an emudhra issued certificate for an internal endpoint, that connection will start failing after this upgrade. Check your repo server logs for TLS verification errors after applying.
Upgrade notes ¶
There are no breaking changes or migration steps in the notes. The release is tagged against the release-3.3 branch and is a drop in patch for existing 3.3.x installs. The standard apply commands from the notes, with server side apply to handle conflicts:
kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.3.18/manifests/install.yaml
HA installs use manifests/ha/install.yaml from the same tag. If you are coming from a different minor version, read the upstream upgrading documentation first instead of jumping straight to this tag.
One operational aside: verify the images you pull. All Argo CD container images from this release are signed with cosign and CLI binaries ship with SLSA Level 3 provenance. If you already enforce signature verification in your admission policy, this release fits into that pipeline without special casing.
Where to get it ¶
- Release page: https://github.com/argoproj/argo-cd/releases/tag/v3.3.18
- Repository: https://github.com/argoproj/argo-cd
- Tag:
v3.3.18