LiveActive security incident?Get immediate response
CVE Record

CVE-2020-26240: Erroneous Proof of Work calculation in geth

Go Ethereum, or "Geth", is the official Golang implementation of the Ethereum protocol. An ethash mining DAG generation flaw in Geth before version 1.9.24 could cause miners to erroneously calculate PoW in an upcoming epoch (estimated early January, 2021). This happened on the ETC chain on 2020-11-06. This issue is relevant only for miners, non-mining nodes are unaffected. This issue is fixed as of 1.9.24

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This flaw could make older Geth miners calculate Ethereum proof-of-work incorrectly during a future mining epoch. The business risk is mainly failed or invalid mining activity, not compromise of ordinary nodes. Sources state non-mining nodes are unaffected and the issue was fixed in Geth 1.9.24.

Executive priority

Treat this as a targeted mining-infrastructure integrity issue. It is not a general enterprise compromise risk, but unpatched miners could produce invalid work and disrupt revenue or operations. Prioritize only if the organization operated affected Geth mining systems.

Technical view

CVE-2020-26240 is a CWE-682 incorrect calculation flaw in Geth ethash mining DAG generation before 1.9.24. It affects proof-of-work calculation by miners only. CVSS is 5.3 with high attack complexity, no confidentiality impact, and high integrity impact.

Likely exposure

Exposure is limited to organizations running Geth versions earlier than 1.9.24 for mining. Non-mining Geth nodes are out of scope according to the advisory. Historical relevance is strongest for mining operations active around the affected epoch in late 2020 and early 2021.

Exploitation context

The bundle reports this issue occurred on the Ethereum Classic chain on 2020-11-06. It is not listed as KEV, and the supplied sources do not support current active exploitation. Evidence describes a protocol-calculation failure mode for miners, not a broad remote compromise path.

Researcher notes

The key boundary is role-based impact: miners are affected, non-mining nodes are not. Public sources identify the flaw, affected version range, fix version, PR, and commit. They do not provide evidence of KEV listing or current exploitation beyond the reported ETC occurrence.

Mitigation direction

  • Upgrade affected Geth miners to version 1.9.24 or later.
  • Prioritize mining infrastructure; non-mining nodes are stated unaffected.
  • Review the Ethereum release post and GitHub advisory for vendor guidance.
  • Pause or isolate mining operations that cannot be version-validated.

Validation and detection

  • Inventory all Geth deployments and identify mining roles.
  • Confirm miner hosts run Geth 1.9.24 or later.
  • Document non-mining Geth nodes as unaffected for this CVE.
  • Review mining incident records around 2020-11-06 if Ethereum Classic exposure matters.
Prepared
Confidence
high
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-682: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-26240 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N1.63.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2020-26240Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
ethereumgo-ethereum< 1.9.24Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-682 · source CWE mapping

Incorrect Calculation

Incorrect Calculation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.