← Übersicht Argo CD

An oversized OCI manifest can exhaust repo-server memory

GHSA-w996-f2wq-x9c6

Mittel · CVSS 6.5 Netzwerk · mit Login Fix verfügbar

Veröffentlicht
07.10.2026 17:58
Zuletzt geändert
07.10.2026
EPSS (30 Tage)
unbekannt
CVSS-Vektor
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Beschreibung

Originaltext der Quelle, nicht übersetzt.

### Impact Argo CD reads an OCI image manifest into memory with no size limit. A registry can return a manifest large enough to exhaust the repo-server. Kubernetes then kills the process, and manifest generation stops for every Application until the pod restarts. The same request can be sent again after the restart. All versions from v3.1.0 onward are affected, including every currently supported release. v3.0.23 and earlier are not. The behavior was introduced in [18c4d9d568](https://github.com/argoproj/argo-cd/commit/18c4d9d56869531f7ae017d610d4e79aaa5525c3) (2025-06-06, [#18646](https://github.com/argoproj/argo-cd/pull/18646)), the change that added OCI as an application source, and was first released in v3.1.0. Argo CD downloads the manifest when it renders an Application whose source is an OCI registry, and when it loads that source's metadata. Resolving a tag to a digest does not download the manifest. The `--oci-manifest-max-extracted-size` flag (default 1G) limits the unpacked image archive. It does not limit the manifest document. See [argocd-repo-server](https://argo-cd.readthedocs.io/en/stable/operator-manual/server-commands/argocd-repo-server/). Someone who can make Argo CD pull from a registry they control can trigger this. That includes creating an Application with an `oci://` source, which the `default` project's `sourceRepos: ['*']` allows. See [OCI](https://argo-cd.readthedocs.io/en/stable/user-guide/oci/) and [the default project](https://argo-cd.readthedocs.io/en/stable/user-guide/projects/#the-default-project). A person who can push to a registry an Application already uses can do the same. This is the OCI counterpart of the Helm index limit in [GHSA-jhwx-mhww-rgc3](https://github.com/argoproj/argo-cd/security/advisories/GHSA-jhwx-mhww-rgc3). ### Patches A patch for this vulnerability has been released in the following Argo CD versions: * v3.6.0-rc2 * v3.5.4 * v3.4.10 * v3.3.15 The fix rejects an OCI manifest larger than 4 MiB. Argo CD 3.1 and 3.2 are affected and out of support. They will not receive a patch. Upgrade to a patched 3.3 or newer release. ### Workarounds There is no setting that caps the OCI manifest document. * Allow only registries you trust in the AppProject `sourceRepos` list. The `default` project allows every source until that list is changed. See [Projects](https://argo-cd.readthedocs.io/en/stable/user-guide/projects/). * Do not grant untrusted users permission to create Applications or repositories that point at other registries. See [RBAC resources](https://argo-cd.readthedocs.io/en/stable/operator-manual/rbac/#rbac-model-structure). A user who can push to a registry already listed in `sourceRepos` can still publish an oversized manifest. ### Credits The Argo CD team would like to thank @andrejtomci for responsibly disclosing this issue according to our [security reporting guidelines](https://github.com/argoproj/argo-cd/blob/master/SECURITY.md#reporting-a-vulnerability). ### References * Introducing commit: [18c4d9d56869531f7ae017d610d4e79aaa5525c3](https://github.com/argoproj/argo-cd/commit/18c4d9d56869531f7ae017d610d4e79aaa5525c3) ([#18646](https://github.com/argoproj/argo-cd/pull/18646)), first released in v3.1.0 * [OCI](https://argo-cd.readthedocs.io/en/stable/user-guide/oci/) * [GHSA-jhwx-mhww-rgc3](https://github.com/argoproj/argo-cd/security/advisories/GHSA-jhwx-mhww-rgc3), the Helm index size limit ### For more information * Open an issue in [the Argo CD issue tracker](https://github.com/argoproj/argo-cd/issues) or [discussions](https://github.com/argoproj/argo-cd/discussions) * Join us on [Slack](https://argoproj.github.io/community/join-slack) in channel #argo-cd

Betroffene Pakete im beobachteten Stack

Gogithub.com/argoproj/argo-cd/v33.3.15 || >= 3.4.0, 3.4.0 → 3.4.10 || >= 3.5.0, 3.5.0 → 3.6.0-rc2GHSA-w996-f2wq-x9c6

Empfohlene Prüfung

  1. Feststellen, ob und in welcher Version die betroffenen Pakete in Ihren Systemen, Images und Abhängigkeiten vorkommen.
  2. Wo eine Fix-Version genannt ist: aktualisieren. Wo nicht: Hersteller-Advisory und Referenzen auf Workarounds prüfen.
  3. Erreichbarkeit beachten: Der Angriffsweg (Netzwerk · mit Login) ist aus dem CVSS-Vektor abgeleitet.

Diese Seite sagt nichts darüber, ob Ihre Systeme betroffen sind. Das klärt erst eine Prüfung Ihrer Versionen.