{"id":"GHSA-w996-f2wq-x9c6","aliases":[],"summary":"An oversized OCI manifest can exhaust repo-server memory","published_at":"2026-10-07T15:58:49Z","modified_at":"2026-10-07T15:58:49Z","products":[{"slug":"argo-cd","name":"Argo CD","category":"gitops-cicd"}],"rating":{"severity":"medium","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","attack_path":"internet_authenticated","user_interaction":false,"malicious":false},"fix_available":true,"kev":{"listed":false,"ransomware":false},"public_exploit":false,"exploits":[],"priority":7.5,"record_count":1,"vendors":["GitHub"],"details":"### Impact\n\nArgo 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.\n\nAll 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.\n\nArgo 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/).\n\nSomeone 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).\n\n### Patches\n\nA patch for this vulnerability has been released in the following Argo CD versions:\n\n* v3.6.0-rc2\n* v3.5.4\n* v3.4.10\n* v3.3.15\n\nThe fix rejects an OCI manifest larger than 4 MiB.\n\nArgo 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.\n\n### Workarounds\n\nThere is no setting that caps the OCI manifest document.\n\n* 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/).\n* 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).\n\nA user who can push to a registry already listed in `sourceRepos` can still publish an oversized manifest.\n\n### Credits\n\nThe 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).\n\n### References\n\n* 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\n* [OCI](https://argo-cd.readthedocs.io/en/stable/user-guide/oci/)\n* [GHSA-jhwx-mhww-rgc3](https://github.com/argoproj/argo-cd/security/advisories/GHSA-jhwx-mhww-rgc3), the Helm index size limit\n\n### For more information\n\n* 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)\n* Join us on [Slack](https://argoproj.github.io/community/join-slack) in channel #argo-cd","affected_stack":[{"ecosystem":"Go","package":"github.com/argoproj/argo-cd/v3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.3.15 || >= 3.4.0"}]},{"type":"ECOSYSTEM","events":[{"introduced":"3.4.0"},{"fixed":"3.4.10 || >= 3.5.0"}]},{"type":"ECOSYSTEM","events":[{"introduced":"3.5.0"},{"fixed":"3.6.0-rc2"}]}],"fixed":["3.3.15 || >= 3.4.0","3.4.10 || >= 3.5.0","3.6.0-rc2"],"provider":"github-repo-advisories","source":"GHSA-w996-f2wq-x9c6","relation":"self"}],"affected_other":[],"product_status":[],"records":[{"provider":"github-repo-advisories","source_id":"GHSA-w996-f2wq-x9c6","relation":"self","url":"https://github.com/argoproj/argo-cd/security/advisories/GHSA-w996-f2wq-x9c6","license":"GitHub Terms of Service","published_at":"2026-10-07T15:58:49Z","modified_at":"2026-10-07T15:58:49Z","summary":"An oversized OCI manifest can exhaust repo-server memory","details":"### Impact\n\nArgo 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.\n\nAll 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.\n\nArgo 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/).\n\nSomeone 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).\n\n### Patches\n\nA patch for this vulnerability has been released in the following Argo CD versions:\n\n* v3.6.0-rc2\n* v3.5.4\n* v3.4.10\n* v3.3.15\n\nThe fix rejects an OCI manifest larger than 4 MiB.\n\nArgo 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.\n\n### Workarounds\n\nThere is no setting that caps the OCI manifest document.\n\n* 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/).\n* 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).\n\nA user who can push to a registry already listed in `sourceRepos` can still publish an oversized manifest.\n\n### Credits\n\nThe 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).\n\n### References\n\n* 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\n* [OCI](https://argo-cd.readthedocs.io/en/stable/user-guide/oci/)\n* [GHSA-jhwx-mhww-rgc3](https://github.com/argoproj/argo-cd/security/advisories/GHSA-jhwx-mhww-rgc3), the Helm index size limit\n\n### For more information\n\n* 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)\n* Join us on [Slack](https://argoproj.github.io/community/join-slack) in channel #argo-cd","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","source":"GHSA-w996-f2wq-x9c6"}],"affected":[{"ecosystem":"Go","package":"github.com/argoproj/argo-cd/v3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.3.15 || >= 3.4.0"}]},{"type":"ECOSYSTEM","events":[{"introduced":"3.4.0"},{"fixed":"3.4.10 || >= 3.5.0"}]},{"type":"ECOSYSTEM","events":[{"introduced":"3.5.0"},{"fixed":"3.6.0-rc2"}]}],"fixed":["3.3.15 || >= 3.4.0","3.4.10 || >= 3.5.0","3.6.0-rc2"],"provider":"github-repo-advisories","source":"GHSA-w996-f2wq-x9c6","relation":"self"}],"product_status":[],"references":[{"type":"ADVISORY","url":"https://github.com/argoproj/argo-cd/security/advisories/GHSA-w996-f2wq-x9c6"}]}],"references":[{"type":"ADVISORY","url":"https://github.com/argoproj/argo-cd/security/advisories/GHSA-w996-f2wq-x9c6"}],"sources":[{"provider":"github-repo-advisories","source_id":"GHSA-w996-f2wq-x9c6","url":"https://github.com/argoproj/argo-cd/security/advisories/GHSA-w996-f2wq-x9c6","license":"GitHub Terms of Service","modified_at":"2026-10-07T15:58:49Z","relation":"self"}]}
