eMudhra certificate flaw affects Ethereum clients Teku and Besu

eMudhra certificate flaw affects Ethereum clients Teku and Besu

N
News Editor
2026-10-29 05:40:00
An encryption security flaw tied to Indian certificate authority eMudhra has affected Ethereum clients Teku and Besu, according to ChainCatcher. Researchers said private keys for eight intermediate certificate authorities under eMudhra may be derivable because of insufficient randomness. That could let an attacker forge certificates and trick unpatched software into trusting malicious services. Teku has released version 26.1.3 and Besu has released version 26.1.2, with both removing trust in the affected certificates from their Docker images. The reported risk includes potential man-in-the-middle attacks that could cause some validators to send block fee rewards to an attacker-controlled address, with higher exposure in certain setups using an external signer. Teku said Ethereum mainnet Teku nodes running the default configuration are not affected and do not need to take action. It also said there have been no reports of the flaw being exploited so far. Operators running Teku or Besu directly on hosts without Docker may need to update Java and its trusted certificate store manually, while those still using unsupported Java 26 need to migrate to Java 25.

According to ChainCatcher, an encryption security flaw involving Indian certificate authority eMudhra has affected the Ethereum clients Teku and Besu.

Researchers found that private keys for eight intermediate certificate authorities under eMudhra may be derivable because of insufficient randomness. That creates a path for attackers to forge certificates and trick unpatched software into trusting malicious services.

Teku and Besu have released patched versions

Teku has released version 26.1.3, while Besu has released version 26.1.2. Both have removed trust in the affected certificates from their Docker images.

Risk centers on specific deployment setups

If an attacker carries out a man-in-the-middle attack, some validators could be tricked into sending block fee rewards to an attacker-controlled address. The risk may be higher in certain configurations that use an external signer.

The Teku team said Ethereum mainnet Teku nodes using the default configuration are not affected and do not need to take action. It also said there have been no reports so far that the flaw has been exploited.

Operators without Docker may need extra steps

For operators running Teku or Besu directly on hosts without Docker, updating the client alone may not be enough. They may also need to manually update Java and its trusted certificate list.

Operators still using unsupported Java 26 need to migrate to Java 25.

This article was originally published by Bit.Fan. For more cryptocurrency news and market insights, visit www.bit.fan.
8900

Disclaimer:

The market information, project data, and third-party content displayed on this platform are for industry information sharing only and do not constitute any form of investment advice or return commitment.

Cryptocurrency trading carries high risks. Users should fully assess their risk tolerance and make independent decisions. All profits, losses, and legal responsibilities are borne by the users themselves.