How severe is GHSA-2f5v-8r3f-8pww?

GHSA-2f5v-8r3f-8pww has a CVSS score of 9.9/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-2f5v-8r3f-8pww?

GHSA-2f5v-8r3f-8pww 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 GHSA-2f5v-8r3f-8pww?

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 GHSA-2f5v-8r3f-8pww is resolved across your whole dependency graph.

How do I detect GHSA-2f5v-8r3f-8pww 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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-2f5v-8r3f-8pww if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-2f5v-8r3f-8pww?

O3 pinpoints whether GHSA-2f5v-8r3f-8pww is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-2f5v-8r3f-8pww actively exploited in the wild?

No public exploit code has been indexed for GHSA-2f5v-8r3f-8pww 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 GHSA-2f5v-8r3f-8pww?

GHSA-2f5v-8r3f-8pww has an EPSS (Exploit Prediction Scoring System) score of 1.2%, placing it in the 64th 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.

When was GHSA-2f5v-8r3f-8pww published, and has it been updated?

GHSA-2f5v-8r3f-8pww was published on March 24, 2022 and was last updated on March 13, 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

GHSA-2f5v-8r3f-8pww

CRITICAL

Improper access control allows admin privilege escalation in Argo CD

Also known asCVE-2022-24768GO-2022-0359

Published

Mar 24, 2022

Updated

Mar 13, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

1.2%probability of exploitation in next 30 days

Lower Risk64th percentile+0.80%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

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	`github.com/argoproj/argo-cd`	≥ 2.2.0&&< 2.2.8	2.2.8
🐹Go	`github.com/argoproj/argo-cd`	≥ 2.3.0&&< 2.3.2	2.3.2

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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 GHSA-2f5v-8r3f-8pww is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-2f5v-8r3f-8pww is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-2f5v-8r3f-8pww. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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 GHSA-2f5v-8r3f-8pww in your dependencies?

O3 detects GHSA-2f5v-8r3f-8pww across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

CVSS Score

9.9/10

CVSS v3 base score

Vector breakdown

AV:Attack Vector

Network

AC:Attack Complexity

Low

PR:Privileges Required

Low

UI:User Interaction

None

S:Scope

Changed

C:Confidentiality

High

I:Integrity

High

A:Availability

High

Raw vector

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

Weaponization

No known public exploit tooling found.

OpenSSF Scorecard

Package health score

argo-cd

7.6/10

Dependency-Update-Tool10/10

Maintained10/10

Code-Review10/10

Vulnerabilities0/10

Branch-ProtectionN/A

Assessed Jun 22, 2026

Timeline

Disclosed

Mar 24, 2022

Last updated

Mar 13, 2026

Identifiers

GHSA-2f5v-8r3f-8pww

GO-2022-0359

References

Advisorynvd.nist.gov Webgithub.com Webgithub.com Webgithub.com Webgithub.com Webgithub.com Packagegithub.com

Related CVEs

CVE-2022-1025

Data from OSV.dev, enriched by O3 Security. Refreshed hourly.

GHSA-2f5v-8r3f-8pww

EPSS Exploitation Probability

Blast Radius

Description

Impact

Impacts for versions starting with v1.0.0

Events exploit

Impacts for versions starting with v0.8.0

Impacts for versions starting with v0.5.0

Patches

Workarounds

Mitigations

References

For more information

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

How O3 protects you

Frequently Asked Questions

Is GHSA-2f5v-8r3f-8pww in your dependencies?