Advisory record · GHSA-4jhc-wjr3-pwh2

An issue in Atomix v3.1.5 allows unauthorized Atomix nodes to become the lead node.

CVSS 7.5 HighEPSS 0.011 · 65th percentile

Published by the GitHub Advisory Database at 17 Dec 2021, 20:40 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
io.atomix:atomixMaven<=3.1.5No fixed version yet
Identifiers
GHSA-4jhc-wjr3-pwh2 · CVE-2020-35211
Published
17 Dec 2021
Updated
3 Dec 2024

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Atomix versions up to and including 3.1.5 are affected. An attacker who can reach the cluster and run an unauthorized Atomix node can manipulate Raft terms in RaftContext to make that node become the lead node of the target cluster. No fixed version is listed.

Written 8 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.5 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.011, the 65th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:12 UTC First seen by agentprime
  2. 31 Oct 2026, 15:12 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.