Skip to main content
No exploitation reportedFix available

CVE-2020-8828

No exploitation reported by the sources we read.

  • Published2020-04-08
  • Fixed in1.5.0
  • WeaknessCWE-1188 · CWE-287

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

As of v1.5.0, the default admin password is set to the argocd-server pod name. For insiders with access to the cluster or logs, this issue could be abused for privilege escalation, as Argo has privileged roles. A malicious insider is the most realistic threat, but pod names are not meant to be kept secret and could wind up just about anywhere.

Timeline

dates in UTC
  1. 2020-04-0820:15CVE publishedNVD

Versions per branch

NVD · OSV
Argoproj argo cd
BranchAffectedFixed in
1.5< 1.5.01.5.0
argoproj/argo-cd
BranchAffectedFixed in
1.8≤ 1.8.0no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

  1. Update Argoproj argo cd to 1.5.0

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • NVDCVSS 3.18.8read 2026-10-23
  • NVDCVSS 2.06.5read 2026-10-23
  • NVDweakness (CWE)CWE-1188, CWE-287read 2026-10-23
  • FIRST EPSSEPSS score1.8 %2026-11-09
  • OSVaffected packages—
  • GitHub AdvisoriesadvisoryHIGH2021-07-26

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Published
2020-04-08
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-h8jc-jmrf-9h8f

Frequently asked questions

What is CVE-2020-8828?

As of v1.5.0, the default admin password is set to the argocd-server pod name. For insiders with access to the cluster or logs, this issue could be abused for privilege escalation, as Argo has privileged roles. A malicious insider is the most realistic threat, but pod names are not meant to be kept secret and could wind up just about anywhere.

Is CVE-2020-8828 actively exploited?

Active exploitation of CVE-2020-8828 has not been confirmed. Its EPSS score was 1.8% on 2026-11-09, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2020-8828?

CVE-2020-8828 has a CVSS v3 base score of 8.8 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record