Skip to content

26.11.0

Latest

Choose a tag to compare

@github-actions github-actions released this 18 Nov 02:08
Immutable release. Only release title and notes can be modified.
5273593

Security

  • Guava upgraded to 33.7.2-jre to fix CVE-2026-102554, and snappy-java pinned to 1.1.10.9 to fix CVE-2026-93451 and CVE-2026-108106 (transitive via besu and teku). #1285
  • Web3Signer now starts with -XX:-UseBASE64Intrinsics to mitigate CVE-2026-114938, a heap overflow in the JVM's Base64 decoder on x86-64 CPUs with AVX-512. Set WEB3SIGNER_OPTS=-XX:+UseBASE64Intrinsics to turn the intrinsic back on. The distroless image sets the flags in its entrypoint, so they can only be changed there by overriding the entrypoint. #1299

Upcoming Breaking Changes

These options are deprecated and will be removed in a future release. Using them logs a warning. A truststore can hold CA certificates as well as client or server certificates. #1282

  • --tls-known-clients-file and --tls-allow-ca-clients: use --tls-truststore-file and --tls-truststore-password-file.
  • --downstream-http-tls-known-servers-file: use --downstream-http-tls-truststore-file and --downstream-http-tls-truststore-password-file.
  • --downstream-http-tls-ca-auth-enabled: remove it. Without a truststore, the JVM's default CAs are used.
  • Hashicorp signing metadata tlsKnownServersPath: use tlsTruststoreFile and tlsTruststorePasswordFile.

Features Added

  • TLS trust can be configured with a truststore instead of certificate fingerprint files. Supported formats are PKCS#12 (preferred), JKS and PEM. The format is detected from the file content. PKCS#12 and JKS need a password file; PEM does not. The truststore holds the trusted certificates or their CAs. Like javax.net.ssl.trustStore, it replaces the JVM's default CAs. #1282
    • Inbound client authentication: --tls-truststore-file and --tls-truststore-password-file. Requires --tls-keystore-file. Cannot be combined with --tls-known-clients-file, --tls-allow-ca-clients or --tls-allow-any-client.
    • Eth1 downstream web3 provider: --downstream-http-tls-truststore-file and --downstream-http-tls-truststore-password-file. Requires --downstream-http-tls-enabled. Cannot be combined with --downstream-http-tls-known-servers-file or --downstream-http-tls-ca-auth-enabled.
    • Hashicorp Vault signing metadata: tlsTruststoreFile and tlsTruststorePasswordFile. Requires tlsEnabled: true. Cannot be combined with tlsKnownServersPath. Relative paths resolve against the key config directory.
  • Docker images can now be built without a local Java install: when the TAR_FILE build argument is omitted, docker/Dockerfile and docker/Dockerfile.distroless build the distribution from source inside Docker. Building from a pre-built TAR_FILE remains the recommended path. See docker/README.md. #1249

Bugs Fixed

  • Hashicorp key files for the same Vault shared one HTTP client, even with different TLS settings. The first key file loaded decided the trust for all of them. Key files with different TLS settings now get separate clients. #1282
  • The deprecated Hashicorp tlsKnownServersPath is now loaded relative to the key config directory, not the working directory. The existence check already used the key config directory. #1282

Breaking Changes

CI/Build Enhancements

  • Besu upgraded to 26.10.2. #1285
  • Compiler warnings fail the build again. #1283
  • Hashicorp Vault acceptance tests run against the hashicorp/vault 2.2.1 image via Testcontainers instead of a downloaded 1.9.2 binary. #1277
  • Removed the Cloudsmith and jitpack Maven repositories; errorprone-checks now resolves from Maven Central (io.consensys.protocols:errorprone-checks:1.1.2) and the unused java-cid dependency was dropped. #1288
  • Gradle wrapper upgraded to 9.9.1. #1297
  • AWS tests run in CI against MiniStack, which replaces LocalStack. #1276
  • GCP Secret Manager acceptance tests run again in CI, against a Testcontainers instance of the offline gcp-secret-manager-emulator instead of real Google Cloud. #1275
  • The default Docker image copies its JRE from the digest-pinned eclipse-temurin:25-jre image (Temurin 25.0.5+8) instead of downloading the Adoptium release tarball, now that the official image carries the eMudhra CA fix. #1249

Downloads

Binaries

Binary Checksum
web3signer.tar.gz Checksum
web3signer.zip Checksum

Docker

Default image (Ubuntu + Eclipse Temurin JRE 25):
docker pull consensys/web3signer:26.11.0

Hardened image (Google Distroless, read-only-filesystem compatible):
docker pull consensys/web3signer:26.11.0-distroless

Verify

Binaries, with the GitHub CLI:

# the file is the one published with this release
gh release verify-asset 26.11.0 web3signer-26.11.0.tar.gz --repo Consensys-Incorporated/web3signer
# the file was built by this repository's CI workflow
gh attestation verify web3signer-26.11.0.tar.gz --repo Consensys-Incorporated/web3signer

Docker images: see Verifying image signatures and attestations.


Full Changelog: 26.10.2...26.11.0