CVE Intelligence
Critical Info disclosure exploit reference

CVE-2025-55190 — Argo CD: Project API Token Exposes Repository Credentials

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.

Published Sep 4, 2025 · Updated Oct 18, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: GitHub_M

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

Detection templates (Nuclei) · 1
How the score was calculated
  • Public exploit/PoC (nuclei)+4
  • EPSS 5.7% (30-day exploitation probability)+14
  • Technical severity (critical)+10

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
5.66%
ahead of 93% of scored CVEs · Oct 30, 2026
Affects
Argoproj
Argo Cd and 2 more
CVSS base
9.9
Critical · 3 source(s)
Prioritization reference: 10.0 provisional

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Documented patch — github.com (NIST National Vulnerability Database)
  • Go Github.com/argoproj/argo-cd/v2: fixed in version 2.13.9 — github.com (GitHub Security Advisories)
  • Go Github.com/argoproj/argo-cd/v2: fixed in version 2.14.16 — github.com (GitHub Security Advisories)
  • Go Github.com/argoproj/argo-cd/v3: fixed in version 3.0.14 — github.com (GitHub Security Advisories)
  • Go Github.com/argoproj/argo-cd/v3: fixed in version 3.1.2 — github.com (GitHub Security Advisories)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Argoproj Argo Cd, Go Github.com/argoproj/argo-cd/v2, Go Github.com/argoproj/argo-cd/v3).
  2. Apply the fixed version or the patch documented under Remediation.
  3. EPSS ahead of 93% of scored CVEs: prioritize it in the patch queue.
  4. Search available logs for exploit probes matching the vulnerability class (info disclosure), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Argoproj Argo Cd ≥ 2.2.0 and < 2.13.9≥ 2.14.0 and < 2.14.16≥ 3.0.0 and < 3.0.14≥ 3.1.0 and < 3.1.2 Vulnerable NIST National Vulnerability Database
Argoproj Argo Cd version >= 2.13.0, < 2.13.9version >= 2.14.0, < 2.14.16version >= 3.0.0, < 3.0.14version >= 3.1.0-rc1, < 3.1.2 Vulnerable CVE Program (cve.org) e CISA ADP
Go Github.com/argoproj/argo-cd/v2 ≥ 2.13.0 and < 2.13.9≥ 2.14.0 and < 2.14.16 Vulnerable GitHub Security Advisories
Go Github.com/argoproj/argo-cd/v3 < 3.0.14≥ 3.1.0-rc1 and < 3.1.2 Vulnerable GitHub Security Advisories

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
10.0 CVSS 3.1 Critical — — GitHub_M via CVE Program (cve.org) e CISA ADP
9.9 CVSS 3.1 Critical 3.1 6.0 security-advisories@github.com via NIST National Vulnerability Database
9.9 CVSS 3.1 Critical — — GitHub, Inc. via GitHub Security Advisories
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H (score shown at the top: security-advisories@github.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-200 · Exposure of Sensitive Information

Other CVEs with this weakness →

Public exploits, PoCs and detection templates

Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.

Detection templates (Nuclei)

Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.

EPSS over time FIRST

Oct 18, 2026 → Oct 30, 2026 · 13 reading(s) · max 5.66%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Look for anomalous data read/export volumes and access to sensitive records.
web/proxy/WAF logsnetwork IDS/IPSapplication logsauthentication logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • Fix documented
    Oct 18, 2026 · GitHub Security Advisories
  • Affected products added · go/github.com/argoproj/argo-cd/v2, go/github.com/argoproj/argo-cd/v3
    Oct 18, 2026 · GitHub Security Advisories
  • Affected products added · argoproj/argo-cd
    Oct 18, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 18, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 18, 2026
  • Fix documented
    Oct 18, 2026 · NIST National Vulnerability Database
  • Affected products added · argoproj/argo cd
    Oct 18, 2026 · NIST National Vulnerability Database
  • CVSS changed · 9.9
    Oct 18, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 18, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 18, 2026 · Alertas do Telegram
  • 2025
  • CVE published
    Sep 4, 2025 · GitHub_M

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 18, 2026 – Oct 18, 2026
  • 1× Official description updated · Oct 18, 2026 – Oct 18, 2026

References

4 on the record

Elsewhere on this site

Argoproj
every CVE for this vendor
Info disclosure
same class
CWE-200
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-113708 Argo CD: A Kustomize remote ref can run commands in the repo-server 10d
  • CVE-2026-113709 Argo CD: A Kustomize Helm config home can run commands in the repo-server 10d
  • CVE-2026-113672 Argo CD: A Jsonnet import can read files from the repo-server 10d
  • CVE-2026-77459 Argo CD: AppProject destination-namespace and resource restrictions bypassed by PreDelete/PostDelete resource hooks 17d
  • CVE-2026-55797 Argo CD repo-server command injection via crafted SSH repository SOCKS5 proxy URL 21d
  • CVE-2026-45738 Argo CD: Stored XSS in application link annotations enables developer-to-admin privilege escalation Jul 15, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2025-55190 is "Argo CD: Project API Token Exposes Repository Credentials", rated Critical. It affects Argo Cd (Argoproj); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 9.9 describes technical severity. EPSS 5.66% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.