How severe is GHSA-87p9-x75h-p4j2?

GHSA-87p9-x75h-p4j2 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-87p9-x75h-p4j2?

GHSA-87p9-x75h-p4j2 affects the following packages: github.com/argoproj/argo-cd/v2/server (Go), github.com/argoproj/argo-cd/v2/server (Go), github.com/argoproj/argo-cd/v2/server (Go). Ecosystems affected: Go.

How do I fix GHSA-87p9-x75h-p4j2?

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.

How do I detect GHSA-87p9-x75h-p4j2 in my Go dependencies?

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.

How do I mitigate GHSA-87p9-x75h-p4j2 if there is no patch (or I can't update yet)?

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.

Is GHSA-87p9-x75h-p4j2 actively exploited in the wild?

No public exploit code has been indexed for GHSA-87p9-x75h-p4j2 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-87p9-x75h-p4j2?

GHSA-87p9-x75h-p4j2 has an EPSS (Exploit Prediction Scoring System) score of 2.3%, placing it in the 84th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-87p9-x75h-p4j2?

GHSA-87p9-x75h-p4j2 is classified as Improper Authentication (CWE-287), Missing Authentication (CWE-306). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for GHSA-87p9-x75h-p4j2?

A Nuclei detection template exists for GHSA-87p9-x75h-p4j2, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was GHSA-87p9-x75h-p4j2 published, and has it been updated?

GHSA-87p9-x75h-p4j2 was published on June 6, 2024 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

MEDIUM severity

Unauthenticated Access to sensitive settings in Argo CDGHSA-87p9-x75h-p4j2

MEDIUMFix: argoproj/argo-cd@256d901

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.

Also known asBIT-argo-cd-2024-37152CVE-2024-37152GO-2024-2902

Published

Jun 6, 2024

Updated

Sep 10, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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

via FIRST.org ↗

2.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs84th percentile — riskier than 84% of all scored CVEsHighest risk

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

3 pkgs affected

🐹github.com/argoproj/argo-cd/v2/server🐹github.com/argoproj/argo-cd/v2/server🐹github.com/argoproj/argo-cd/v2/server

Real-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

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/argoproj/argo-cd/v2/server`	≥ 2.9.3&&< 2.9.17	2.9.17`go 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.12`go 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.3`go get github.com/argoproj/argo-cd/v2/server@v2.11.3`

Affected Products

1 product · 3 configurations

Application

argo cdargoproj

≥ 2.11.0 && < 2.11.3

range

Detection & mitigation playbook

Open-source dependency

Detect
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
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 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

# 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 admin

O3 Security · Impact-Aware SCA

Is GHSA-87p9-x75h-p4j2 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

5.3/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

CWE Classification

CWE-287Improper Authentication CWE-306Missing Authentication

Weaponization

OpenSSF Scorecard

Package health score

argo-cd

8.9/10

Code-Review10/10

Maintained10/10

Dependency-Update-Tool10/10

Branch-Protection8/10

Vulnerabilities0/10

Assessed Nov 8, 2026

Timeline

Disclosed

Jun 6, 2024

Last updated

Sep 10, 2026

Identifiers

GHSA-87p9-x75h-p4j2

BIT-argo-cd-2024-37152

GO-2024-2902

References

Advisorynvd.nist.gov · CVE 2024 37152 Webgithub.com · GHSA 87p9 x75h p4j2 Webgithub.com · 256d90178b11b04bc8174d08d7b663a2a7b1771b Webpkg.go.dev · GO 2024 2902 Packagegithub.com · argo cd

Related vulnerabilities

This CVE is medium severity; 8 of 8 other CVEs with CWE-287 are rated as high or higher (top: critical).

CVE-2026-62264GHSA-jf75-q64q-g65rCVE-2026-49272CVE-2026-114616CVE-2026-114607CVE-2026-114618GHSA-r4xp-prcw-77qfCVE-2026-73054Browse all CWE-287

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedSep 10, 2026

Unauthenticated Access to sensitive settings in Argo CDGHSA-87p9-x75h-p4j2

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Summary

Details

Unauthenticated Access:

Endpoint: /api/v1/settings

Impact

Unauthenticated Access:

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

How to detect GHSA-87p9-x75h-p4j2

Frequently Asked Questions

Is GHSA-87p9-x75h-p4j2 in your dependencies?