Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.8

Argo CD improper access control bug can allow malicious user to escalate privileges to admin level

CVE-2022-1025GHSA-96jv-vj39-x4j6

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go github.com/argoproj/argo-cd/v2

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

  • Go github.com/argoproj/argo-cd

    Affected
    >= 0.5.0, <= 1.8.7
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.8 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
  • CVE-2022-1025: 1.34% estimated exploitation activity in the next 30 days; percentile 71.43 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-96jv-vj39-x4j6

Agent brief

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

# Patch Next advisory brief: CVE-2022-1025

Advisory: Argo CD improper access control bug can allow malicious user to escalate privileges to admin level
IDs: CVE-2022-1025, GHSA-96jv-vj39-x4j6
Record: https://patchnext.com/advisories/cve-2022-1025 (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: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/argoproj/argo-cd/v2 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/v2: affected < 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
- Go github.com/argoproj/argo-cd: affected >= 0.5.0, <= 1.8.7

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

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/argoproj/argo-cd/v2, 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-96jv-vj39-x4j6 (GitHub-reviewed advisory GHSA-96jv-vj39-x4j6 lists affected ranges: Go github.com/argoproj/argo-cd >=0.5.0 =0 =2.2.0 =2.3.0 <2.3.2)

Commands are suggestions: review each one before running it.

Loading voting…