How severe is CVE-2022-24768?

CVE-2022-24768 has a CVSS score of 9.9/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-24768?

CVE-2022-24768 affects the following packages: github.com/argoproj/argo-cd (Go), github.com/argoproj/argo-cd (Go), github.com/argoproj/argo-cd (Go). Ecosystems affected: Go.

How do I fix CVE-2022-24768?

Update github.com/argoproj/argo-cd to 2.1.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-24768 is resolved across your whole dependency graph.

How do I detect CVE-2022-24768 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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-24768 if there is no patch (or I can't update yet)?

Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Is CVE-2022-24768 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-24768 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 CVE-2022-24768?

CVE-2022-24768 has an EPSS (Exploit Prediction Scoring System) score of 1.3%, placing it in the 70th 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 CVE-2022-24768?

CVE-2022-24768 is classified as Information Exposure (CWE-200), CWE-862 (CWE-862). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-24768 published, and has it been updated?

CVE-2022-24768 was published on March 23, 2022 and was last updated on October 28, 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

CRITICAL severity

CVE-2022-24768 — argo-cd

CRITICALFix: argoproj/argo-cd@af03b29

CVE-2022-24768 is a critical-severity (CVSS 9.9) Information Exposure vulnerability in github.com/argoproj/argo-cd. A fix is available for github.com/argoproj/argo-cd — see the affected versions and patch details below.

Improper access control allows admin privilege escalation in Argo CD

Also known asCVE-2022-1025 GHSA-2f5v-8r3f-8pww GHSA-96jv-vj39-x4j6GO-2022-0359GO-2022-0516

Published

Mar 23, 2022

Updated

Oct 28, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
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 CVE-2022-24768.

EPSS Exploitation Probability

via FIRST.org ↗

1.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs70th percentile — riskier than 70% 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🐹github.com/argoproj/argo-cd🐹github.com/argoproj/argo-cd

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

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:

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.
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.)
If the user has get access to the Application, they can view any resource on the Application's destination cluster (except for the contents of Secrets) and list actions available for that resource.
If the user has get access to the Application, they can view the logs of any Pods on the Application's destination cluster.
If the user has action/{some action or *} access on the Application, they can run an action for any resource (which supports the allowed action(s)) on the Application's destination cluster. (Some actions are available in Argo CD by default, and others may be configured by an Argo CD admin.)

See the Argo CD RBAC documentation for an explanation of the privileges available in Argo CD.

Events exploit

A related exploit is possible for a user with get access to an Application even if they do not have access to the Application's source git or Helm repository or sync and override access to the Application. The user can access any Event in the Application's destination cluster if they know the involved object's name, UID, and namespace.

Impacts for versions starting with v0.8.0

The same bug exists starting with v0.8.0, but only the following exploits were possible before v1.0.0:

The delete exploit (#⁠2 above).
The logs exploit (#⁠4 above).
The Events exploit described above.

Impacts for versions starting with v0.5.0

The same bug exists starting with v0.5.0 (when RBAC was implemented), but only the Events exploit described above was possible before v0.8.0.

Patches

A patch for this vulnerability has been released in the following Argo CD versions:

v2.3.2
v2.2.8
v2.1.14

Versions 2.0.x and earlier users: See the changelog for links to upgrade instructions for your version. It is imperative to upgrade quickly, but some limited mitigations are described in the next section.

argo-helm chart users: Argo CD users deploying v2.3.x with argo-helm can upgrade the chart to version 4.2.2. Argo CD 2.2 and 2.1 users can set the global.image.tag value to the latest in your current release series (v2.2.8, or v2.1.14). Since charts for the 2.2 and 2.1 series are no longer maintained, you will need to either leave the value override in place or upgrade to the 4.x chart series (and therefore to Argo CD 2.3).

Workarounds

The only certain way to avoid the vulnerability is to upgrade.

Mitigations

To avoid privilege escalation:
- Limit who has push access to Application source repositories or sync + override access to Applications.
- Limit which repositories are available in projects where users have update access to Applications.
To avoid unauthorized resource inspection/tampering:
- Limit who has delete, get, or action access to Applications.

These mitigations can help limit potential damage, but they are not a substitute for upgrading. It is necessary to upgrade immediately.

References

Argo CD RBAC configuration documentation

For more information

Open an issue in the Argo CD issue tracker or discussions Join us on Slack in channel #argo-cd

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/argoproj/argo-cd`	≥ 0.5.0&&< 2.1.14	2.1.14`go get github.com/argoproj/argo-cd@v2.1.14`
🐹Go	`github.com/argoproj/argo-cd`	≥ 2.2.0&&< 2.2.8	2.2.8`go get github.com/argoproj/argo-cd@v2.2.8`
🐹Go	`github.com/argoproj/argo-cd`	≥ 2.3.0&&< 2.3.2	2.3.2`go get github.com/argoproj/argo-cd@v2.3.2`

Affected Products

1 product · 3 configurations

Application

argo cdargoproj

≥ 2.3.0 && < 2.3.2

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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/argoproj/argo-cd to 2.1.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-24768 is resolved across your whole dependency graph.
Workarounds
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is CVE-2022-24768 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

9.9/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Raw vector

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

CWE Classification

CWE-200Information Exposure CWE-862CWE-862

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

OpenSSF Scorecard

Package health score

argo-cd

8.9/10

Code-Review10/10

Maintained10/10

Dependency-Update-Tool10/10

Vulnerabilities0/10

Branch-Protection8/10

Assessed Nov 6, 2026

Timeline

Disclosed

Mar 23, 2022

Last updated

Oct 28, 2026

Identifiers

CVE-2022-24768

GHSA-2f5v-8r3f-8pww

GO-2022-0359

GO-2022-0516

References

Advisorygithub.com · CVE 2022 24768.json Advisorygithub.com · GHSA 2f5v 8r3f 8pww Advisorynvd.nist.gov · CVE 2022 24768 Fixgithub.com · af03b291d4b7e9d3ce9a6580ae9c8141af0e05cf Webgithub.com · v2.1.14 Webgithub.com · v2.2.8 Webgithub.com · v2.3.2 Packagegithub.com · argo cd

Related vulnerabilities

This CVE is critical severity; 2 of 8 other CVEs affecting argo-cd are rated as high or higher (top: critical).

CVE-2026-45738CVE-2025-59531CVE-2025-59537CVE-2025-47933CVE-2025-23216CVE-2024-40634CVE-2024-36106CVE-2024-31989

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026