
Ethereum clients Teku and Besu have released emergency security updates to address a certificate vulnerability that could allow attackers to redirect validator rewards to their own wallets. According to security advisories, the vulnerability originated from weak cryptographic keys associated with eight certificate authorities operated by Indian company eMudhra, which could allow attackers to create fraudulent certificates. Teku released version 26.10.3 on October 27, while Besu introduced version 26.10.2 a day earlier, both removing trust for affected eMudhra certificates from their Docker images. The vulnerability could affect validators that rely on external services for signing transactions, communicating with beacon nodes or receiving block-building information, though Teku confirmed default mainnet configurations were not affected and no exploitation had been reported. As reported by Kudelski Security, the weakness allowed private keys to be recovered in microseconds, with the affected intermediate keys created during an April 30, 2025 key ceremony where a flawed wrap and unwrap step produced weak copies alongside original strong keys.
Ethereum developers have successfully merged a fix for a deposit-handling flaw in the upcoming Glamsterdam upgrade that could have allowed a block builder to receive ETH intended for a new validator. According to reports from crypto.news and AMBCrypto, maintainer Justin Traglia merged the correction on October 26 after developer avsetsin identified a problem with how pending deposits would be processed during the Gloas fork. The change separates builder deposits from validator deposits according to their withdrawal credentials, preventing funds from entering the wrong account when both use the same public key. The correction was initially set aside on October 19 due to lack of client support, but developers reopened it on October 23 following further examination and additional testing.
The issue emerged from changes planned under Glamsterdam's enshrined proposer-builder separation, which assigns block construction and block proposal to different roles. Researcher avsetsin described the flaw on October 12, identifying a problem in the rules used to process deposits waiting when the network upgrades. The researcher outlined a scenario involving a staking operator receiving funds from a liquid staking protocol to establish a new validator, where by registering as a builder first, the operator could cause the protocol's validator deposit to enter the builder balance. As reported by AMBCrypto, depending on the circumstances, an operator controlling that builder account can then withdraw the funds that is supposed to be for staking, though these represent potential risks rather than confirmed attacks.
The specification update arrived while Ethereum developers were reviewing a separate problem affecting Glamsterdam's scheduled activation on the Hoodi testnet. As reported by crypto.news and AMBCrypto, the Ethereum Foundation postponed the October 26 upgrade after researchers identified compatibility risks involving EIP-8037. The decision removed both the Amsterdam execution changes and Gloas consensus changes from Hoodi's planned activation, with the proposed increase to a 200 million gas limit also postponed. The Foundation has not set a new Hoodi date yet, and no time has been set for the mainnet launch either. The October 26 postponement also removed the scheduled activation of the Amsterdam execution changes and Gloas consensus changes.
The merged deposit correction contains regression tests covering how deposits are classified during the Gloas transition. According to crypto.news and AMBCrypto, client teams must incorporate the specification change into their software and complete further testing before the updated rules can operate during a future network upgrade. Glamsterdam already activated on the Sepolia testnet on October 6, where developers examined block construction changes and higher transaction-processing capacity, though the subsequent Hoodi rehearsal remains unscheduled with no confirmed date for activation on Ethereum mainnet. Data from DefiLlama shows there are currently 17.13 million staked ETH, worth close to $40 billion, highlighting the potential impact of any deposit-handling issues on the network's staking infrastructure. The incident demonstrates how certificate authority failures can affect Ethereum validator operations through external service connections, with different operators facing varying exposure based on their specific configurations and runtime environments.