Unauthenticated Access to sensitive settings in Argo CD

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2024-37152: 2.35% estimated exploitation activity in the next 30 days; percentile 83.70 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.

Published by the source

6 Jun 2024, 21:27 UTC

Last modified by the source

17 Jun 2024, 15:26 UTC

Source last checked

26 Oct 2026, 15:04 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-87p9-x75h-p4j2

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-37152

Advisory: Unauthenticated Access to sensitive settings in Argo CD
IDs: CVE-2024-37152, GHSA-87p9-x75h-p4j2
Record: https://patchnext.com/advisories/cve-2024-37152 (revision 1, source checked 26 Oct 2026, 15:04 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/argoproj/argo-cd/v2/server 2.11.3, 2.10.12, 2.9.17. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/argoproj/argo-cd/v2/server: affected >= 2.9.3, < 2.9.17; >= 2.10.0, < 2.10.12; >= 2.11.0, < 2.11.3; fixed in 2.9.17, 2.10.12, 2.11.3

## Suggested inspection (read-only)
- Go github.com/argoproj/argo-cd/v2/server: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/argoproj/argo-cd/v2/server.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-87p9-x75h-p4j2 (GitHub-reviewed advisory GHSA-87p9-x75h-p4j2 lists affected ranges: Go github.com/argoproj/argo-cd/v2/server >=2.9.3 =2.10.0 =2.11.0 <2.11.3)

Commands are suggestions: review each one before running it.