CVE-2020-35211: An issue in Atomix v3.1.5 allows unauthorized Atomix nodes to become the lead node in a target cluster via man

This week

HIGH 7.5REMOTEDOWNGRADE

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

An issue in Atomix v3.1.5 allows unauthorized Atomix nodes to become the lead node in a target cluster via manipulation of the variable terms in RaftContext.

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

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

Publisher (CNA): MITRE · Vendor: atomix

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

Am I affected?

Timeline

2021-12-16 20:15 UTCPublished CVE record published
2026-06-17 03:13 UTCUpdated Record last modified

atomix atomix DOWNGRADE

Affected: 3.1.5

Fixed in: no fixed release known

Safe to downgrade to: a release before 3.1.5

1. Check installed version

apt-cache policy atomix || rpm -q atomix || atomix --version

2. No fixed release: DOWNGRADE to a release before 3.1.5 (Debian / Ubuntu)

apt-cache madison atomix sudo apt install atomix=<VERSION_BEFORE_3.1.5> sudo apt-mark hold atomix

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list atomix sudo dnf downgrade atomix-<VERSION_BEFORE_3.1.5> sudo dnf versionlock add atomix

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-35211?

atomix: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2020-35211 being exploited?

CVE-2020-35211 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-35211 affect?

CVE-2020-35211 affects atomix. Severity is high (CVSS 7.5). An issue in Atomix v3.1.5 allows unauthorized Atomix nodes to become the lead node in a target cluster via manipulation of the variable terms in RaftContext.

How urgent is CVE-2020-35211?

Priority 52/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

Related CVEs

CVE-2020-35216 MEDIUM 5.9 DOWNGRADE An issue in Atomix v3.1.5 allows attackers to cause a denial of service (DoS) via false member down event mess
CVE-2020-35215 MEDIUM 6.5 DOWNGRADE An issue in Atomix v3.1.5 allows attackers to access sensitive information when a malicious Atomix node querie
CVE-2020-35214 HIGH 8.1 DOWNGRADE An issue in Atomix v3.1.5 allows a malicious Atomix node to remove states of ONOS storage via abuse of primiti
CVE-2020-35213 HIGH 8.1 DOWNGRADE An issue in Atomix v3.1.5 allows attackers to cause a denial of service (DoS) via false link event messages se
CVE-2020-35210 MEDIUM 6.5 UPGRADE A vulnerability in Atomix v3.1.5 allows attackers to cause a denial of service (DoS) via a Raft session floodi

References

← Back to latest CVEs