CVE-2020-10590: Replicated Classic 2.x versions have an improperly secured API that exposes sensitive data from the Replicated

This month

HIGH 7.5REMOTEUPGRADE

CVE-2020-10590 is a high-severity flaw (CVSS 7.5) affecting replicated classic. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Replicated Classic 2.x versions have an improperly secured API that exposes sensitive data from the Replicated Admin Console configuration. An attacker with network access to the Admin Console port (8800) on the Replicated Classic server could retrieve the TLS Keypair (Cert and Key) used to configure the Admin Console.

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.3% (top 29%)
CISA exploited list	No
Published	2021-07-30
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: replicated

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2021-07-30 14:15 UTCPublished CVE record published
2026-06-17 02:48 UTCUpdated Record last modified

replicated replicated classic UPGRADE

Affected: >= 2.10.0 and <= 2.32.3 · >= 2.33.0 and <= 2.36.0 · >= 2.37.0 and <= 2.37.1 · >= 2.38.0 and <= 2.38.5 · >= 2.39.0 and <= 2.39.3 · >= 2.40.0 and <= 2.40.3 · >= 2.42.0 and <= 2.42.3 · 2.41.0

Fixed in: newer than 2.42.3

Safe to downgrade to: a release before 2.10.0

1. Check installed version

apt-cache policy replicated-classic || rpm -q replicated-classic || replicated-classic --version

2. UPGRADE to newer than 2.42.3 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade replicated-classic

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade replicated-classic

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 2.10.0 (Debian / Ubuntu)

apt-cache madison replicated-classic sudo apt install replicated-classic=<VERSION_BEFORE_2.10.0> sudo apt-mark hold replicated-classic

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list replicated-classic sudo dnf downgrade replicated-classic-<VERSION_BEFORE_2.10.0> sudo dnf versionlock add replicated-classic

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-10590?

replicated classic: upgrade to newer than 2.42.3. Exact commands for each OS are on this page.

Is CVE-2020-10590 being exploited?

CVE-2020-10590 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-10590 affect?

CVE-2020-10590 affects replicated classic. Severity is high (CVSS 7.5). Replicated Classic 2.x versions have an improperly secured API that exposes sensitive data from the Replicated Admin Console configuration. An attacker with network access to the Admin Console port (8800) on the Replicated Classic server co

How urgent is CVE-2020-10590?

Priority 49/100. High severity; Remotely exploitable, no login, no user action

Related CVEs

CVE-2021-43058 MEDIUM 6.1 UPGRADE An open redirect vulnerability exists in Replicated Classic versions prior to 2.53.1 that could lead to spoofi

References

← Back to latest CVEs