How severe is GHSA-786q-9hcg-v9ff?

GHSA-786q-9hcg-v9ff has a CVSS score of 9.9/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-786q-9hcg-v9ff?

GHSA-786q-9hcg-v9ff affects the following packages: github.com/argoproj/argo-cd/v2 (Go), github.com/argoproj/argo-cd/v2 (Go), github.com/argoproj/argo-cd/v3 (Go), github.com/argoproj/argo-cd/v3 (Go). Ecosystems affected: Go.

How do I fix GHSA-786q-9hcg-v9ff?

Update github.com/argoproj/argo-cd/v2 to 2.13.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-786q-9hcg-v9ff is resolved across your whole dependency graph.

How do I detect GHSA-786q-9hcg-v9ff 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-786q-9hcg-v9ff 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-786q-9hcg-v9ff?

O3 pinpoints whether GHSA-786q-9hcg-v9ff 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-786q-9hcg-v9ff actively exploited in the wild?

No public exploit code has been indexed for GHSA-786q-9hcg-v9ff 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-786q-9hcg-v9ff?

GHSA-786q-9hcg-v9ff has an EPSS (Exploit Prediction Scoring System) score of 4.5%, placing it in the 90th 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-786q-9hcg-v9ff?

GHSA-786q-9hcg-v9ff is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for GHSA-786q-9hcg-v9ff?

A Nuclei detection template exists for GHSA-786q-9hcg-v9ff, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was GHSA-786q-9hcg-v9ff published, and has it been updated?

GHSA-786q-9hcg-v9ff was published on September 4, 2025 and was last updated on February 4, 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-786q-9hcg-v9ff

CRITICAL

Argo CD's Project API Token Exposes Repository Credentials

Also known asBIT-argo-cd-2025-55190CVE-2025-55190GO-2025-3934

Published

Sep 4, 2025

Updated

Feb 4, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

4.5%probability of exploitation in next 30 days

Lower Risk90th percentile-0.86%

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/v2🐹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

Argo CD API tokens with project-level permissions are able to retrieve sensitive repository credentials (usernames, passwords) through the project details API endpoint, even when the token only has standard application management permissions and no explicit access to secrets.

Component: Project API (/api/v1/projects/{project}/detailed)

Vulnerability Details

Expected Behavior

API tokens should require explicit permission to access sensitive credential information. Standard project permissions should not grant access to repository secrets.

Actual Behavior

API tokens with basic project permissions can retrieve all repository credentials associated with a project through the detailed project API endpoint.

Note: This vulnerability does not only affect project-level permissions. Any token with project get permissions is also vulnerable, including global permissions such as: p, role/user, projects, get, *, allow

Steps to Reproduce

Create an API token with the following project-level permissions:

p, proj:myProject:project-automation-role, applications, sync, myProject/*, allow
p, proj:myProject:project-automation-role, applications, action/argoproj.io/Rollout/*, myProject/*, allow
p, proj:myProject:project-automation-role, applications, get, myProject/*, allow

Call the project details API:

bashcurl -sH "Authorization: Bearer $ARGOCD_API_TOKEN" \
  "https://argocd.example.com/api/v1/projects/myProject/detailed"

Observe that the response includes sensitive repository credentials:

{
  "repositories": [
    {
      "username": "<REDACTED>",
      "password": "<REDACTED>",
      "type": "helm",
      "name": "test-helm-repo",
      "project": "myProject"
    }
  ]
}

Patches

v3.1.2
v3.0.14
v2.14.16
v2.13.9

Credits to @ashishgoyal111 for helping identify this issue.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/argoproj/argo-cd/v2`	≥ 2.13.0&&< 2.13.9	2.13.9
🐹Go	`github.com/argoproj/argo-cd/v2`	≥ 2.14.0&&< 2.14.16	2.14.16
🐹Go	`github.com/argoproj/argo-cd/v3`	all versions	3.0.14
🐹Go	`github.com/argoproj/argo-cd/v3`	≥ 3.1.0-rc1&&< 3.1.2	3.1.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/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.13.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-786q-9hcg-v9ff 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-786q-9hcg-v9ff 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-786q-9hcg-v9ff. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary Argo CD API tokens with project-level permissions are able to retrieve sensitive repository credentials (usernames, passwords) through the project details API endpoint, even when the token only has standard application management permissions and no explicit access to secrets. Component: `Project API (/api/v1/projects/{project}/detailed)` ## Vulnerability Details ### Expected Behavior API tokens should require explicit permission to access sensitive credential information. Standard project permissions should not grant access to repository secrets. ### Actual Behavior API tokens w

O3 Security · Impact-Aware SCA

Is GHSA-786q-9hcg-v9ff in your dependencies?

O3 detects GHSA-786q-9hcg-v9ff 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