{"id":"GHSA-9mrf-wvv5-62p9","aliases":[],"summary":"Unauthenticated pprof endpoints on the controller and API server metrics ports","published_at":"2026-11-20T03:38:50Z","modified_at":"2026-11-20T03:38:50Z","products":[{"slug":"argo-cd","name":"Argo CD","category":"gitops-cicd"}],"rating":{"severity":"medium","score":5.4,"vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L","attack_path":"adjacent","user_interaction":false,"malicious":false},"fix_available":true,"kev":{"listed":false,"ransomware":false},"public_exploit":false,"exploits":[],"priority":6.4,"record_count":1,"vendors":["GitHub"],"details":"### Impact\n\nThe application controller and the API server served Go's `pprof` profiling endpoints (`/debug/pprof/`) on their metrics ports, always on and with no authentication. Anyone who could reach those ports could download CPU and heap profiles and other runtime details, which can contain sensitive data, and could trigger profiling that uses extra resources on the component.\n\nAll versions from v2.2.0 onward are affected, up to the patched version below. The endpoints were added in [49b71522c](https://github.com/argoproj/argo-cd/commit/49b71522c447da73d9e395de2aabd8d4c5176c3e) ([#7533](https://github.com/argoproj/argo-cd/pull/7533)).\n\nThe metrics ports are usually not exposed through an Ingress, so an attacker typically needs network access from inside the cluster.\n\n### Patches\n\nA patch for this vulnerability has been released in the following Argo CD version:\n\n* v2.13.0\n\nSince v2.13.0 the profiling endpoints are off by default and return 401 unless explicitly enabled with `controller.profile.enabled`, `server.profile.enabled`, `reposerver.profile.enabled` or `applicationsetcontroller.profile.enabled` in [`argocd-cmd-params-cm`](https://argo-cd.readthedocs.io/en/stable/operator-manual/argocd-cmd-params-cm-yaml/).\n\n### Workarounds\n\nRestrict network access to the application controller and API server [metrics](https://argo-cd.readthedocs.io/en/stable/operator-manual/metrics/) ports, for example with Kubernetes NetworkPolicies, so that only your monitoring system can reach them.\n\n### Credits\n\nThe Argo CD team would like to thank @agilgur5 for responsibly disclosing this issue.\n\n### References\n\n* Fix: [26fb098ae](https://github.com/argoproj/argo-cd/commit/26fb098ae85e00dd453eabd010c557f2b34fec3a) ([#19327](https://github.com/argoproj/argo-cd/pull/19327))\n* Introducing commit: [49b71522c](https://github.com/argoproj/argo-cd/commit/49b71522c447da73d9e395de2aabd8d4c5176c3e) ([#7533](https://github.com/argoproj/argo-cd/pull/7533)), first released in v2.2.0\n* [Your pprof is showing](https://mmcloughlin.com/posts/your-pprof-is-showing)\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/v2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.2.0"},{"fixed":"2.13.0"}]}],"fixed":["2.13.0"],"provider":"github-repo-advisories","source":"GHSA-9mrf-wvv5-62p9","relation":"self"}],"affected_other":[],"product_status":[],"records":[{"provider":"github-repo-advisories","source_id":"GHSA-9mrf-wvv5-62p9","relation":"self","url":"https://github.com/argoproj/argo-cd/security/advisories/GHSA-9mrf-wvv5-62p9","license":"GitHub Terms of Service","published_at":"2026-11-20T03:38:50Z","modified_at":"2026-11-20T03:38:50Z","summary":"Unauthenticated pprof endpoints on the controller and API server metrics ports","details":"### Impact\n\nThe application controller and the API server served Go's `pprof` profiling endpoints (`/debug/pprof/`) on their metrics ports, always on and with no authentication. Anyone who could reach those ports could download CPU and heap profiles and other runtime details, which can contain sensitive data, and could trigger profiling that uses extra resources on the component.\n\nAll versions from v2.2.0 onward are affected, up to the patched version below. The endpoints were added in [49b71522c](https://github.com/argoproj/argo-cd/commit/49b71522c447da73d9e395de2aabd8d4c5176c3e) ([#7533](https://github.com/argoproj/argo-cd/pull/7533)).\n\nThe metrics ports are usually not exposed through an Ingress, so an attacker typically needs network access from inside the cluster.\n\n### Patches\n\nA patch for this vulnerability has been released in the following Argo CD version:\n\n* v2.13.0\n\nSince v2.13.0 the profiling endpoints are off by default and return 401 unless explicitly enabled with `controller.profile.enabled`, `server.profile.enabled`, `reposerver.profile.enabled` or `applicationsetcontroller.profile.enabled` in [`argocd-cmd-params-cm`](https://argo-cd.readthedocs.io/en/stable/operator-manual/argocd-cmd-params-cm-yaml/).\n\n### Workarounds\n\nRestrict network access to the application controller and API server [metrics](https://argo-cd.readthedocs.io/en/stable/operator-manual/metrics/) ports, for example with Kubernetes NetworkPolicies, so that only your monitoring system can reach them.\n\n### Credits\n\nThe Argo CD team would like to thank @agilgur5 for responsibly disclosing this issue.\n\n### References\n\n* Fix: [26fb098ae](https://github.com/argoproj/argo-cd/commit/26fb098ae85e00dd453eabd010c557f2b34fec3a) ([#19327](https://github.com/argoproj/argo-cd/pull/19327))\n* Introducing commit: [49b71522c](https://github.com/argoproj/argo-cd/commit/49b71522c447da73d9e395de2aabd8d4c5176c3e) ([#7533](https://github.com/argoproj/argo-cd/pull/7533)), first released in v2.2.0\n* [Your pprof is showing](https://mmcloughlin.com/posts/your-pprof-is-showing)\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:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L","source":"GHSA-9mrf-wvv5-62p9"}],"affected":[{"ecosystem":"Go","package":"github.com/argoproj/argo-cd/v2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.2.0"},{"fixed":"2.13.0"}]}],"fixed":["2.13.0"],"provider":"github-repo-advisories","source":"GHSA-9mrf-wvv5-62p9","relation":"self"}],"product_status":[],"references":[{"type":"ADVISORY","url":"https://github.com/argoproj/argo-cd/security/advisories/GHSA-9mrf-wvv5-62p9"}]}],"references":[{"type":"ADVISORY","url":"https://github.com/argoproj/argo-cd/security/advisories/GHSA-9mrf-wvv5-62p9"}],"sources":[{"provider":"github-repo-advisories","source_id":"GHSA-9mrf-wvv5-62p9","url":"https://github.com/argoproj/argo-cd/security/advisories/GHSA-9mrf-wvv5-62p9","license":"GitHub Terms of Service","modified_at":"2026-11-20T03:38:50Z","relation":"self"}]}
