Technologie
Besu 26.11.1 disables a Java optimization to mitigate CVE-2026-114938
The release published on November 18 changes the Ethereum client’s startup options. The measure targets HotSpot’s Base64 decoder on certain x86-64 processors.

An option added at startup
Besu published version 26.11.1 on November 18, 2026. Its release note announces that a Java virtual machine Base64 decoder optimization is disabled by default through -XX:-UseBASE64Intrinsics. The project describes this as a mitigation for CVE-2026-114938, a heap overflow affecting the decoder’s optimized implementation. The patch therefore concerns the options used to start the software rather than a change to Ethereum’s network rules.
Pull request 11994, merged on November 17 at 23:13 UTC, details the technical scope. It describes a vulnerability in HotSpot’s AVX-512 implementation on x86-64 processors supporting AVX-512 VBMI. It specifically mentions Intel generations from Ice Lake and AMD generations from Zen 4. This hardware scope matters: the presence of Java software alone does not establish that this particular decoder implementation is being used.
Besu scripts and Docker are covered
The change adds the flag to applicationDefaultJvmArgs in build.gradle. That list feeds the besu and besu-untuned launch scripts and their Windows .bat versions. The Docker image starts through /opt/besu/bin/besu, so it receives the option as well. The pull request specifies, however, that evmtool’s script is unchanged because that tool has its own Java options. The announced effect thus depends on the startup path used for each component.
An operator can reenable the optimization by setting BESU_OPTS=-XX:+UseBASE64Intrinsics. The change documentation explains why: JAVA_OPTS and BESU_OPTS are appended after the defaults in the startup script. An explicit configuration can therefore override the value introduced by this release. This possibility describes how the launcher works; it is not a recommendation from the project to reenable a function targeted by the mitigation.
A mitigation with stated testing limits
The pull request reports generating all four scripts and checking the effective flag with PrintFlagsFinal. Its author says those checks were performed on Apple Silicon, where the optimization is already inactive. The author explicitly states that they did not verify on an x86 machine with AVX-512 VBMI that the flag closes the heap overflow. The evidence described therefore establishes that the option takes effect at startup, with an explicit limitation on validation on affected hardware.
The same document envisages a later step: updating the version and digest of the Eclipse Temurin image used by the Docker files, then removing this flag once a fixed version is incorporated. This is the follow-up described in the pull request, not a step that the 26.11.1 release note announces as completed. For this release, the published change remains the default disabling of the Base64 optimization, with the startup scope and testing caveats documented by the project.
