CVE-2024-37152 is a medium-severity (CVSS 5.3) Improper Authentication vulnerability in github.com/argoproj/argo-cd/v2/server. A fix is available for github.com/argoproj/argo-cd/v2/server — see the affected versions and patch details below.
Unauthenticated Access to sensitive settings in Argo CD
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-37152.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/argoproj/argo-cd/v2/server🐹github.com/argoproj/argo-cd/v2/server🐹github.com/argoproj/argo-cd/v2/serverReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Summary
The CVE allows unauthorized access to the sensitive settings exposed by /api/v1/settings endpoint without authentication.
Details
Unauthenticated Access:
Endpoint: /api/v1/settings
Description: This endpoint is accessible without any form of authentication as expected. All sensitive settings are hidden except passwordPattern.
Patches A patch for this vulnerability has been released in the following Argo CD versions:
v2.11.3 v2.10.12 v2.9.17
Impact
Unauthenticated Access:
- Type: Unauthorized Information Disclosure.
- Affected Parties: All users and administrators of the Argo CD instance.
- Potential Risks: Exposure of sensitive configuration data, including but not limited to deployment settings, security configurations, and internal network information.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/argoproj/argo-cd/v2/server | ≥ 2.9.3&&< 2.9.17 | 2.9.17go get github.com/argoproj/argo-cd/v2/server@v2.9.17 |
| 🐹Go | github.com/argoproj/argo-cd/v2/server | ≥ 2.10.0&&< 2.10.12 | 2.10.12go get github.com/argoproj/argo-cd/v2/server@v2.10.12 |
| 🐹Go | github.com/argoproj/argo-cd/v2/server | ≥ 2.11.0&&< 2.11.3 | 2.11.3go get github.com/argoproj/argo-cd/v2/server@v2.11.3 |
Affected Products
argo cdargoprojDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/argoproj/argo-cd/v2/server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/argoproj/argo-cd/v2/server to 2.9.17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-37152 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
How to detect CVE-2024-37152
A community-maintained Nuclei template exists for this CVE. You can scan for it directly:
nuclei -id cve-2024-37152 -u https://target- Template
- Argo CD Unauthenticated Access to sensitive setting
- Severity
- medium
- Impact
- Unauthenticated attackers can access sensitive password patterns and application settings exposed by the /api/v1/settings endpoint.
- Remediation
- Update Argo CD to a version that patches CVE-2024-37152.
Template by ProjectDiscovery nuclei-templates (DhiyaneshDk), MIT licensed. View the full template. Scan only systems you are authorised to test.
Frequently Asked Questions
Is CVE-2024-37152 in your dependencies?
Find it across Go, including transitive dependencies.