GHSA-87p9-x75h-p4j2 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 GHSA-87p9-x75h-p4j2.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-87p9-x75h-p4j2 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,238 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
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 |
Detection & 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 GHSA-87p9-x75h-p4j2 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-87p9-x75h-p4j2 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-87p9-x75h-p4j2. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
How to detect GHSA-87p9-x75h-p4j2
A community-maintained Nuclei template exists for this CVE. You can scan for it directly:
nuclei -id ghsa-87p9-x75h-p4j2 -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 GHSA-87p9-x75h-p4j2 in your dependencies?
O3 Security finds GHSA-87p9-x75h-p4j2 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.