Skip to content
Blockchain Posts

protocol

Teku 26.10.3 and Besu 26.10.2 drop eMudhra trust after Indian CA key blunder

ConsenSys and Hyperledger ship Docker patches after eight eMudhra intermediate CAs were found with keys derivable from public certs. External signers are the sharpest exposure.

by 4 min read
protocolethereuminfrastructuresecurity

Two Ethereum consensus-adjacent clients shipped emergency patches on October 28. Teku 26.10.3 and Besu 26.10.2 stop trusting eight intermediate certificate authorities operated by Indian issuer eMudhra after the private keys for those CAs were found to be derivable from their public certificates. In the worst-case configuration — a validator paired with a remote external signer — an attacker holding the derived keys could impersonate the signer and redirect block fee rewards.

What happened

The eight intermediate CA keys at eMudhra were generated without enough entropy, so anyone with the public certificates could recover the matching private keys. Browsers blocked the certificates about a day before eMudhra revoked them; eMudhra has since said it will exit the certificate business. Default operating-system trust stores dropped the CAs along with the browsers.

Java did not. Java's TLS runtime does not check certificate revocation by default, and Teku's and Besu's Docker images shipped a Java trust store that kept the eMudhra chains in place. A node running those images continued to trust certificates signed by the compromised intermediates.

Why validators care

The attack surface is a remote external signer — a common setup for staking operators who keep signing keys off the beacon node. In that setup the beacon node talks to the signer over TLS. An attacker positioned between the two who presents a forged certificate signed under a derived eMudhra key could:

  • Impersonate the signer and approve a fee-recipient change, redirecting block proposer rewards.
  • Impersonate the service the signer talks to and intercept configuration or key material.

A default Teku mainnet node that is not calling an external signer "is not affected and needs no action," per Teku's release note. The highest-risk operator profile is institutional stakers running Web3Signer or similar behind the Docker image.

What the patches do

  • Teku 26.10.3 (ConsenSys): removes the eight eMudhra intermediate CAs from the Docker image's Java trust store.
  • Besu 26.10.2 (Hyperledger): same change in the Besu Docker image.

Operators running the clients directly on a host, outside the Docker image, must update their Java runtime separately. Teku's note flags one wrinkle: Java 26 is end of life and will not receive a patched build, so Teku users on Java 26 should move to Java 25 to pick up the trust-store fix.

Action checklist

  1. Validator operators on Teku or Besu Docker images: pull 26.10.3 or 26.10.2 and restart.
  2. Validator operators running Teku or Besu bare metal: update the Java runtime, prefer Java 25.
  3. External-signer users: audit TLS configuration between the beacon node and the signer; if either end used system Java, assume the chain was trusting the bad CAs until the update.
  4. There is no CVE assigned in the public write-up; no exploitation has been reported.

Context

This is the second week in a row that Ethereum client teams have shipped patches that most operators did not need to touch but a narrow deployment class did. The October 24 Glamsterdam staking-deposit vulnerability landed in client PR 5736 after researchers found a path that let a crafted deposit redirect staking rewards; that fix also hit Teku and Besu first. The eMudhra patches are different — the root cause lives at a certificate authority outside Ethereum — but the delivery path is the same: Docker-image patching, external-signer paths flagged as the sharpest exposure, and a note telling the median mainnet operator they can wait on their next scheduled restart.

The broader pattern — Java's "trust everything in the store, don't check revocation" default colliding with a CA that fails — has nothing to do with Ethereum per se. The same eMudhra blunder sent patches through Node.js, Go and Python earlier this year. Ethereum operators are a late audience for it only because the Docker images shipped the trust store the Java runtime inherited.

Sources

Related stories