CVE-2025-55190

CRITICALNVD 9.99.9
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 9.9 from GitHub Security Advisory (severity: CRITICAL) published 2025-09-04. NVD baseline CVSS 9.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2025-26875 (ENISA EUVD) · GHSA-786q-9hcg-v9ff (GitHub Security Advisories) · GO-2025-3934 (OSV.dev)Source: ENISA EUVD

9.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 5.7%CVSS: 9.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. In versions 2.13.0 through 2.13.8, 2.14.0 through 2.14.15, 3.0.0 through 3.0.12 and 3.1.0-rc1 through 3.1.1, 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. 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. This issue is fixed in versions 2.13.9, 2.14.16, 3.0.14 and 3.1.2.

CVSS v3
9.9
EG Score
9.9CRITICALmedium confidence
EG Risk
47
EG Risk 47/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity99% × 45%
Impact severity (EG Severity): CVSS 9.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation5.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
5.7%
EPSS %ILE
93rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.9): severity, escalated by confirmed exploitation. This CVE's 9.9 is its impact severity (EG Severity), not escalated.

EG Severity
9.9 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
5.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 4, 2025

Last Modified

October 18, 2026

Advisory Details (2)

Auto-updated Nov 9, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Project API Token Exposes Repository Credentials · Advisory · argoproj/argo-cd · GitHub

https://github.com/argoproj/argo-cd/security/advisories/GHSA-786q-9hcg-v9ff
GitHub commit

commit e8f86101f537 (argoproj/argo-cd)

Fix landed in argoproj/argo-cd commit e8f86101f537 — awaiting tagged release

https://github.com/argoproj/argo-cd/commit/e8f86101f5378662ae6151ce5c3a76e9141900e8

Patch Availability(10)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatopenshift-gitops-1/gitops-rhel8:17691654222026-01-28redhat
redhatopenshift-gitops-1/gitops-rhel8:17688249602026-01-22redhat
redhatopenshift-gitops-1/gitops-rhel8:17688810342026-01-22redhat
redhatopenshift-gitops-1/gitops-rhel8-operator:1.152025-09-04redhat
redhatopenshift-gitops-1/gitops-rhel8-operator:1.172025-09-04redhat
redhatopenshift-gitops-1/gitops-rhel8-operator:1.162025-09-04redhat
gogithub.com/argoproj/argo-cd/v2 @ 2.14.16 (fixes >= 2.14.0, < 2.14.16)—ghsa
gogithub.com/argoproj/argo-cd/v2 @ 2.13.9 (fixes >= 2.13.0, < 2.13.9)—ghsa
gogithub.com/argoproj/argo-cd/v3 @ 3.0.14 (fixes < 3.0.14)—ghsa
gogithub.com/argoproj/argo-cd/v3 @ 3.1.2 (fixes >= 3.1.0-rc1, < 3.1.2)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 1 ecosystem)
Go(3)
PackageVulnerable rangeFix by version rangeDependents
github.com/argoproj/argo-cd—
  • every version on: no fix on record
—
github.com/argoproj/argo-cd/v2—
  • 2.13.0 up to 2.13.9: fixed in 2.13.9
  • 2.14.0 up to 2.14.16: fixed in 2.14.16
—
github.com/argoproj/argo-cd/v3—
  • every version up to 3.0.14: fixed in 3.0.14
  • 3.1.0-rc1 up to 3.1.2: fixed in 3.1.2
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(3)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 20× in last 7d / 74× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 281 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 181 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:50 UTCEPSS rescoreEPSS 5.7% · 93rd percentile
  2. 2026-11-12 21:32 UTCEchelonGraph re-scored
  3. 2026-11-12 21:32 UTCGHSA enrichmentGHSA-786q-9hcg-v9ff · GitHub severity CRITICAL · GitHub CVSS 9.9
  4. 2026-11-12 16:32 UTCEPSS rescoreEPSS 5.7% · 93rd percentile
  5. 2026-11-11 22:34 UTCEchelonGraph re-scored
  6. 2026-11-11 22:34 UTCVendor advisory
  7. 2026-11-11 22:34 UTCGHSA enrichmentGHSA-786q-9hcg-v9ff · GitHub severity CRITICAL · GitHub CVSS 9.9
  8. 2026-11-11 16:36 UTCEPSS rescoreEPSS 5.7% · 93rd percentile
  9. 2026-11-10 23:33 UTCEchelonGraph re-scored
  10. 2026-11-10 23:33 UTCVendor advisory
  11. 2026-11-10 23:33 UTCGHSA enrichmentGHSA-786q-9hcg-v9ff · GitHub severity CRITICAL · GitHub CVSS 9.9
  12. 2026-11-10 16:40 UTCEPSS rescoreEPSS 5.7% · 93rd percentile
  13. 2026-11-10 00:32 UTCEchelonGraph re-scored
  14. 2026-11-10 00:32 UTCVendor advisory
  15. 2026-11-10 00:32 UTCGHSA enrichmentGHSA-786q-9hcg-v9ff · GitHub severity CRITICAL · GitHub CVSS 9.9
  16. 2026-11-09 16:33 UTCEPSS rescoreEPSS 5.7% · 93rd percentile
  17. 2026-11-09 01:34 UTCEchelonGraph re-scored
  18. 2026-11-09 01:34 UTCVendor advisory
  19. 2026-11-09 01:34 UTCGHSA enrichmentGHSA-786q-9hcg-v9ff · GitHub severity CRITICAL · GitHub CVSS 9.9
  20. 2026-11-08 16:37 UTCEPSS rescoreEPSS 5.7% · 93rd percentile
  21. 2026-11-08 02:36 UTCEchelonGraph re-scored
  22. 2026-11-08 02:36 UTCVendor advisory
  23. 2026-11-08 02:36 UTCGHSA enrichmentGHSA-786q-9hcg-v9ff · GitHub severity CRITICAL · GitHub CVSS 9.9
  24. 2026-11-07 16:37 UTCEPSS rescoreEPSS 5.7% · 93rd percentile
  25. 2026-11-07 03:38 UTCEchelonGraph re-scored
Show 75 more
  1. 2026-11-07 03:38 UTCVendor advisory
  2. 2026-11-07 03:38 UTCGHSA enrichmentGHSA-786q-9hcg-v9ff · GitHub severity CRITICAL · GitHub CVSS 9.9
  3. 2026-11-06 16:34 UTCEPSS rescoreEPSS 5.7% · 93rd percentile
  4. 2026-11-06 04:40 UTCEchelonGraph re-scored
  5. 2026-11-06 04:40 UTCVendor advisory
  6. 2026-11-06 04:40 UTCGHSA enrichmentGHSA-786q-9hcg-v9ff · GitHub severity CRITICAL · GitHub CVSS 9.9
  7. 2026-11-05 16:35 UTCEPSS rescoreEPSS 5.7% · 93rd percentile
  8. 2026-11-05 15:55 UTCOSV refresh
  9. 2026-11-05 05:42 UTCEchelonGraph re-scored
  10. 2026-11-05 05:42 UTCVendor advisory
  11. 2026-11-05 05:42 UTCGHSA enrichmentGHSA-786q-9hcg-v9ff · GitHub severity CRITICAL · GitHub CVSS 9.9
  12. 2026-11-04 16:33 UTCEPSS rescoreEPSS 5.7% · 92nd percentile
  13. 2026-11-04 06:44 UTCEchelonGraph re-scored
  14. 2026-11-04 06:44 UTCVendor advisory
  15. 2026-11-04 06:44 UTCGHSA enrichmentGHSA-786q-9hcg-v9ff · GitHub severity CRITICAL · GitHub CVSS 9.9
  16. 2026-11-03 16:45 UTCEPSS rescoreEPSS 5.7% · 92nd percentile
  17. 2026-11-03 07:46 UTCEchelonGraph re-scored
  18. 2026-11-03 07:46 UTCVendor advisory
  19. 2026-11-03 07:46 UTCGHSA enrichmentGHSA-786q-9hcg-v9ff · GitHub severity CRITICAL · GitHub CVSS 9.9
  20. 2026-11-02 08:47 UTCEchelonGraph re-scored
  21. 2026-11-02 08:47 UTCVendor advisory
  22. 2026-11-02 08:47 UTCGHSA enrichmentGHSA-786q-9hcg-v9ff · GitHub severity CRITICAL · GitHub CVSS 9.9
  23. 2026-11-01 16:33 UTCEPSS rescoreEPSS 5.7% · 92nd percentile
  24. 2026-11-01 09:49 UTCVendor advisory
  25. 2026-11-01 09:49 UTCGHSA enrichmentGHSA-786q-9hcg-v9ff · GitHub severity CRITICAL · GitHub CVSS 9.9
  26. 2026-11-01 08:04 UTCGHSA enrichmentGHSA-786q-9hcg-v9ff · GitHub severity CRITICAL · GitHub CVSS 9.9
  27. 2026-11-01 08:04 UTCEchelonGraph re-scored
  28. 2026-10-31 16:31 UTCEPSS rescoreEPSS 5.7% · 92nd percentile
  29. 2026-10-31 10:51 UTCEchelonGraph re-scored
  30. 2026-10-31 10:51 UTCVendor advisory
  31. 2026-10-30 16:33 UTCEPSS rescoreEPSS 5.7% · 92nd percentile
  32. 2026-10-30 11:53 UTCEchelonGraph re-scored
  33. 2026-10-30 11:53 UTCVendor advisory
  34. 2026-10-29 16:31 UTCEPSS rescoreEPSS 5.7% · 92nd percentile
  35. 2026-10-29 12:55 UTCEchelonGraph re-scored
  36. 2026-10-29 12:55 UTCVendor advisory
  37. 2026-10-28 16:30 UTCEPSS rescoreEPSS 5.7% · 92nd percentile
  38. 2026-10-28 13:58 UTCEchelonGraph re-scored
  39. 2026-10-28 13:58 UTCVendor advisory
  40. 2026-10-27 16:30 UTCEPSS rescoreEPSS 5.7% · 92nd percentile
  41. 2026-10-27 14:43 UTCEchelonGraph re-scored
  42. 2026-10-27 14:43 UTCVendor advisory
  43. 2026-10-26 16:30 UTCEPSS rescoreEPSS 5.7% · 92nd percentile
  44. 2026-10-26 15:40 UTCVendor advisory
  45. 2026-10-25 16:42 UTCEchelonGraph re-scored
  46. 2026-10-25 16:42 UTCVendor advisory
  47. 2026-10-25 16:31 UTCEPSS rescoreEPSS 5.7% · 92nd percentile
  48. 2026-10-25 16:18 UTCEchelonGraph re-scored
  49. 2026-10-24 17:42 UTCEchelonGraph re-scored
  50. 2026-10-24 17:42 UTCVendor advisory
  51. 2026-10-24 16:31 UTCEPSS rescoreEPSS 5.7% · 92nd percentile
  52. 2026-10-23 18:44 UTCEchelonGraph re-scored
  53. 2026-10-23 18:44 UTCVendor advisory
  54. 2026-10-23 16:30 UTCEPSS rescoreEPSS 5.7% · 92nd percentile
  55. 2026-10-22 19:42 UTCEchelonGraph re-scored
  56. 2026-10-22 19:42 UTCVendor advisory
  57. 2026-10-22 16:33 UTCEPSS rescoreEPSS 5.7% · 92nd percentile
  58. 2026-10-21 20:44 UTCEchelonGraph re-scored
  59. 2026-10-21 20:44 UTCVendor advisory
  60. 2026-10-21 16:31 UTCEPSS rescoreEPSS 5.7% · 92nd percentile
  61. 2026-10-20 21:41 UTCEchelonGraph re-scored
  62. 2026-10-20 21:41 UTCVendor advisory
  63. 2026-10-20 16:31 UTCEPSS rescoreEPSS 5.7% · 92nd percentile
  64. 2026-10-19 22:43 UTCEchelonGraph re-scored
  65. 2026-10-19 22:43 UTCVendor advisory
  66. 2026-10-19 16:31 UTCEPSS rescoreEPSS 5.7% · 92nd percentile
  67. 2026-10-18 21:30 UTCVendor advisory
  68. 2026-10-18 17:46 UTCEchelonGraph re-scored
  69. 2026-10-18 17:46 UTCVendor advisory
  70. 2026-10-18 16:31 UTCEPSS rescoreEPSS 5.7% · 92nd percentile
  71. 2026-10-18 05:25 UTCEchelonGraph re-scored
  72. 2026-10-17 18:48 UTCEchelonGraph re-scored
  73. 2026-10-17 18:48 UTCVendor advisory
  74. 2026-10-17 16:33 UTCEPSS rescoreEPSS 5.7% · 92nd percentile
  75. 2026-10-16 19:49 UTCEchelonGraph re-scored

Public detection templates

(1 reference)

A public Nuclei detection template is referenced for this CVE. A detection template checks whether a system is affected; it is not necessarily exploit code.

  • Nucleihttp/cves/2025/CVE-2025-55190.yaml
    Published Nov 4, 2025

    ArgoCD Project API Token Repository Credentials Exposure

    Open source ↗

Frequently asked(5)

What is CVE-2025-55190?
CVE-2025-55190 is a critical-severity vulnerability; its CVE record was published on September 4, 2025. Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. In versions 2.13.0 through 2.13.8, 2.14.0 through 2.14.15, 3.0.0 through 3.0.12 and 3.1.0-rc1 through 3.1.1, API tokens with project-level permissions are able to retrieve sensitive repository credentials (usernames,…
When was the CVE record for CVE-2025-55190 published?
The CVE record for CVE-2025-55190 was published on September 4, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 18, 2026; the record at its source may have been updated since.
Is CVE-2025-55190 actively exploited?
CVE-2025-55190 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 5.7% probability of exploitation in the next 30 days (93rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-55190?
CVE-2025-55190 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2025-55190?
A fix for CVE-2025-55190 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-55190 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-55190

Explore →

Is Your Infrastructure Affected by CVE-2025-55190?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.