How severe is GHSA-g88p-r42r-ppp9?

GHSA-g88p-r42r-ppp9 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-g88p-r42r-ppp9?

GHSA-g88p-r42r-ppp9 affects the following packages: github.com/argoproj/argo-cd/v2 (Go), github.com/argoproj/argo-cd/v3 (Go), github.com/argoproj/argo-cd/v3 (Go), github.com/argoproj/argo-cd/v3 (Go). Ecosystems affected: Go.

How do I fix GHSA-g88p-r42r-ppp9?

Update github.com/argoproj/argo-cd/v2 to 2.14.20 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g88p-r42r-ppp9 is resolved across your whole dependency graph.

How do I detect GHSA-g88p-r42r-ppp9 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/v2. 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-g88p-r42r-ppp9 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-g88p-r42r-ppp9?

O3 pinpoints whether GHSA-g88p-r42r-ppp9 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-g88p-r42r-ppp9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-g88p-r42r-ppp9 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-g88p-r42r-ppp9?

GHSA-g88p-r42r-ppp9 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 34th 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 GHSA-g88p-r42r-ppp9?

GHSA-g88p-r42r-ppp9 is classified as CWE-362 (CWE-362). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-g88p-r42r-ppp9 published, and has it been updated?

GHSA-g88p-r42r-ppp9 was published on September 30, 2025 and was last updated on October 23, 2025. 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-g88p-r42r-ppp9

MEDIUM

Repository Credentials Race Condition Crashes Argo CD Server

Also known asBIT-argo-cd-2025-55191CVE-2025-55191GO-2025-3994

Published

Sep 30, 2025

Updated

Oct 23, 2025

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk34th percentile+0.39%

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

4 pkgs affected

🐹github.com/argoproj/argo-cd/v2🐹github.com/argoproj/argo-cd/v3🐹github.com/argoproj/argo-cd/v3🐹github.com/argoproj/argo-cd/v3

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

Summary

A race condition in the repository credentials handler can cause the Argo CD server to panic and crash when concurrent operations are performed on the same repository URL.

Details

The vulnerability is located in numerous repository related handlers in the util/db/repository_secrets.go file. For example, in the secretToRepoCred function. The issue manifests as a concurrent map access panic:

concurrent map read and map write
...
goroutine 1104 [running]:
github.com/argoproj/argo-cd/v2/util/db.(*secretsRepositoryBackend).secretToRepoCred(0xc000e50ea8?, 0xc000c65540)
        /go/src/github.com/argoproj/argo-cd/util/db/repository_secrets.go:404 +0x31e

The race condition occurs due to:

Concurrent repository credential operations (create/update/delete) accessing the same map
Kubernetes informer re-syncs happening simultaneously
Background watchers updating the same secret data
No mutex protection for map access

A valid API token with repositories resource permissions (create, update, or delete actions) is required to trigger the race condition.

Impact

This vulnerability causes the entire Argo CD server to crash and become unavailable. Attackers can repeatedly and continuously trigger the race condition to maintain a denial-of-service state, disrupting all GitOps operations. Default ArgoCD configuration is vulnerable.

The affected code was originally introduced in PR #6103 and released in v2.1.0.

This data race was addressed by deep-copying the Secret objects before reading/writing.

Credits

This vulnerability was found, reported and fixed by:

@thevilledev

The Argo team would like to thank him for his responsible disclosure and constructive communications during the resolve of this issue.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/argoproj/argo-cd/v2`	≥ 2.1.0&&< 2.14.20	2.14.20
🐹Go	`github.com/argoproj/argo-cd/v3`	≥ 3.2.0-rc1&&< 3.2.0-rc2	3.2.0-rc2
🐹Go	`github.com/argoproj/argo-cd/v3`	≥ 3.1.0-rc1&&< 3.1.8	3.1.8
🐹Go	`github.com/argoproj/argo-cd/v3`	≥ 3.0.0-rc1&&< 3.0.19	3.0.19

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/v2. 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/v2 to 2.14.20 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g88p-r42r-ppp9 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-g88p-r42r-ppp9 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-g88p-r42r-ppp9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary A race condition in the repository credentials handler can cause the Argo CD server to panic and crash when concurrent operations are performed on the same repository URL. ### Details The vulnerability is located in numerous repository related handlers in the `util/db/repository_secrets.go` file. For example, in the `secretToRepoCred` function. The issue manifests as a concurrent map access panic: ``` concurrent map read and map write ... goroutine 1104 [running]: github.com/argoproj/argo-cd/v2/util/db.(*secretsRepositoryBackend).secretToRepoCred(0xc000e50ea8?, 0xc000c65540)

O3 Security · Impact-Aware SCA

Is GHSA-g88p-r42r-ppp9 in your dependencies?

O3 detects GHSA-g88p-r42r-ppp9 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