CVE-2022-24768: Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. All unpatched versions of Argo CD starting with 1.0.0 are vulnerable to an i...

Description

Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. All unpatched versions of Argo CD starting with 1.0.0 are vulnerable to an improper access control bug, allowing a malicious user to potentially escalate their privileges to admin-level. Versions starting with 0.8.0 and 0.5.0 contain limited versions of this issue. To perform 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. A patch for this vulnerability has been released in Argo CD versions 2.3.2, 2.2.8, and 2.1.14. Some mitigation measures are available but do not serve as a substitute for upgrading. To avoid privilege escalation, limit who has push access to Application source repositories or `sync` + `override` access to Applications; and 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.

Metrics

CVSS 3.1

8.8/10

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

EPSS Probability

1.20%

64.3th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

Vendor	Product	Versions
Argoproj	Argo Cd	>= 0.5.0, < 2.1.14
Argoproj	Argo Cd	>= 2.2.0, < 2.2.8
Argoproj	Argo Cd	>= 2.3.0, < 2.3.2

References

https://github.com/argoproj/argo-cd/commit/af03b291d4b7e9d3ce9a6580ae9c8141af0e05cfPatch, Third Party Advisory
https://github.com/argoproj/argo-cd/releases/tag/v2.1.14Release Notes, Third Party Advisory
https://github.com/argoproj/argo-cd/releases/tag/v2.2.8Release Notes, Third Party Advisory
https://github.com/argoproj/argo-cd/releases/tag/v2.3.2Release Notes, Third Party Advisory
https://github.com/argoproj/argo-cd/security/advisories/GHSA-2f5v-8r3f-8pwwMitigation, Third Party Advisory
https://github.com/argoproj/argo-cd/commit/af03b291d4b7e9d3ce9a6580ae9c8141af0e05cfPatch, Third Party Advisory
https://github.com/argoproj/argo-cd/releases/tag/v2.1.14Release Notes, Third Party Advisory
https://github.com/argoproj/argo-cd/releases/tag/v2.2.8Release Notes, Third Party Advisory
https://github.com/argoproj/argo-cd/releases/tag/v2.3.2Release Notes, Third Party Advisory
https://github.com/argoproj/argo-cd/security/advisories/GHSA-2f5v-8r3f-8pwwMitigation, Third Party Advisory

Timeline

Published: Mar 23, 2022
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2022-24768?

Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. All unpatched versions of Argo CD starting with 1.0.0 are vulnerable to an improper access control bug, allowing a malicious user to potentially escalate their privileges to admin-level. Versions starting with 0.8.0 and 0.5.0 contain limited versions of this issue. To perform 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. A patch for this vulnerability has been released in Argo CD versions 2.3.2, 2.2.8, and 2.1.14. Some mitigation measures are available but do not serve as a substitute for upgrading. To avoid privilege escalation, limit who has push access to Application source repositories or `sync` + `override` access to Applications; and 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.

How severe is CVE-2022-24768?

CVE-2022-24768 has a CVSS score of 8.8/10 (HIGH severity). The EPSS model estimates a 1.20% probability of exploitation in the next 30 days.

How do I fix CVE-2022-24768?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.