Improper access control allows admin privilege escalation in Argo CD

Exploitation

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

CVSS

9.9 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

EPSS

• CVE-2022-24768: 1.25% estimated exploitation activity in the next 30 days; percentile 69.42 (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.

Impact Impacts for versions starting with v1.0.0 All unpatched versions of Argo CD starting with v1.0.0 are vulnerable to an improper access control bug, allowing a malicious user to potentially escalate their privileges to admin-level. To perform the following exploits, an authorized Argo CD user must have push access to an Application's source git or Helm repository or sync and override access to an Application. Once a user has that access, different exploitation levels are possible depending on their other RBAC privileges: 1. If that user has update access to the Application, they can modify any resource on the Application's destination cluster. If the destination cluster is or can be made to be the same as the cluster hosting Argo CD, the user can escalate their Argo CD permissions to admin-level. 2. If the user has delete access to the Application, they can delete any resource on the Application's destination cluster. (This exploit is possible starting with v0.8.0.) 3. If the…

Published by the source

24 Mar 2022, 00:18 UTC

Last modified by the source

27 Jun 2023, 18:36 UTC

Source last checked

26 Oct 2026, 14:58 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-2f5v-8r3f-8pww

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

# Patch Next advisory brief: CVE-2022-24768

Advisory: Improper access control allows admin privilege escalation in Argo CD
IDs: CVE-2022-24768, GHSA-2f5v-8r3f-8pww
Record: https://patchnext.com/advisories/cve-2022-24768 (revision 1, source checked 26 Oct 2026, 14:58 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.9)
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 2.3.2, 2.2.8, 2.1.14. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/argoproj/argo-cd: affected >= 0.5.0, < 2.1.14; >= 2.2.0, < 2.2.8; >= 2.3.0, < 2.3.2; fixed in 2.2.8, 2.1.14, 2.3.2

## Suggested inspection (read-only)
- Go github.com/argoproj/argo-cd: 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.
- 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-2f5v-8r3f-8pww (GitHub-reviewed advisory GHSA-2f5v-8r3f-8pww lists affected ranges: Go github.com/argoproj/argo-cd >=0.5.0 =2.2.0 =2.3.0 <2.3.2)

Commands are suggestions: review each one before running it.