Besu consensus-validation flaw was addressed in client release 25.3.0
What was reported
The Ethereum Foundation reported that Besu 25.2.2 contained a consensus issue in its handling of EIP-196 and EIP-197 elliptic-curve precompiles. According to the disclosure, the issue was isolated to Besu and addressed in release 25.3.0; Rug.Tools has not independently reproduced the test vector.
Why it matters
Different validation behavior between execution clients can create consensus risk if one client accepts data that others reject. Operators using an affected historical release should rely on official Besu guidance and current supported software rather than treating this archived report as a live network-status alert.
Evidence and limitations
- The official disclosure identifies Besu 25.2.2 and states that release 25.3.0 fixed the issue.
- The source says other Ethereum execution clients were not affected by this specific discrepancy.
Rug.Tools reviewed the official disclosure but did not independently reproduce CVE-2025-30147. Reported allegations remain attributed to Ethereum Foundation Blog; they are not presented as deterministic Rug.Tools findings.
Original source
Source publication time:
Read Ethereum Foundation BlogThis report summarizes attributed source material and automated editorial checks. It is not a legal finding or investment advice. Rug.Tools does not identify a person or organization as responsible without independently verified evidence, and a token is never labeled safe merely because no incident appears in this feed. Reports may be corrected or unpublished when source information changes.