The Ledger
Teku 26.10.3 Removes Four eMudhra-Linked Trust Roots
Teku’s 26.10.3 release changes its Docker images to stop trusting four certificate roots after eMudhra intermediate keys were compromised. Teku says most default mainnet nodes need no action, but Docker users connecting to HTTPS endpoints should update.

Teku’s 26.10.3 Docker images stop trusting four certificate roots after the compromise of eMudhra intermediate keys. Consensys released the update on October 27, describing it as a recommended fix for the eMudhra incident. The change matters most to node operators whose Teku setups make HTTPS connections to other services.
Four roots removed from Teku’s Docker images
The release notes list the emSign ECC Root CA - G3, emSign Root CA - G1, emSign Root CA - G2 and AAA Certificate Services roots. Teku says OpenJDK removed these roots after eMudhra intermediate certificate authorities were compromised in October. The release does not say those four root keys were themselves compromised; it says Teku’s Docker images no longer trust them.
“This is a recommended update addressing the recent CVE-2026-111943 (eMudhra compromised keys)”
Teku 26.10.3 release notes
The release notes also flag that the Eclipse Temurin base images do not yet include the same fix. Teku’s own Docker image update therefore matters independently of changes made to Java distributions: the release describes the trust-root removal in Teku’s images, while the underlying Temurin base images remain a separate component.
HTTPS connections determine which nodes face risk
Teku’s security notice says a default mainnet node is not affected if its configuration contains no HTTPS URLs. Exposure depends on Teku connecting to an HTTPS endpoint, such as a remote beacon node, execution client, external signer, relay, or a URL supplying startup data. Peer-to-peer networking through libp2p and discv5 does not use certificate authorities and is not affected.
An attacker would need to intercept traffic between Teku and the endpoint to impersonate that service with a certificate signed using a compromised key. Teku says no exploitation has been reported. The notice identifies remote beacon-node connections as a meaningful concern: impersonation could feed a validator client misleading data, cause missed or incorrect attestations, or influence where a proposed block pays fees.
Docker users should update; other installs depend on Java
Teku’s notice says Docker images through version 26.10.2—including the JDK 25 and JDK 26 tags—still trusted the emSign ECC Root CA - G3. Operators using those images and HTTPS endpoints should move to 26.10.3. Updating Java on the host does not change the runtime inside a container, the notice says.
Teku’s binary distribution uses the Java runtime installed by the operator, so the Teku release alone does not establish whether that setup has a corrected trust store. The project points users to OpenJDK or their Java vendor’s guidance for checking and updating that runtime. Eclipse Adoptium separately lists October 2026 Temurin releases with the eMudhra fix, while noting that Temurin’s trust-store changes are distinct from Teku’s Docker-image release.
Operators still need to check their endpoint setup
For operators, the first question is whether Teku connects to any remote service over HTTPS and how its Java runtime is supplied. A mainnet node with no HTTPS URLs falls outside Teku’s stated exposure; a Docker node using a remote signer or beacon node does not. The 26.10.3 release addresses the container’s trust in the named roots, while non-container installs must rely on their installed Java runtime’s status.
Sources
- Original source · Release notes Teku on GitHub github.com
Other pages read
- Teku security notice hackmd.io
- Eclipse Adoptium adoptium.net