Back to Homepage
Canton issues Java4Shell mitigation guidance for node operators
TECHNOLOGY

Canton issues Java4Shell mitigation guidance for node operators

The Canton team recommends disabling Java’s Base64 intrinsic while operators check their Java distribution and packaged components for patches. Vendor fixes are already available for affected builds.

2 min read

Java4Shell operator guidance, November 18, 2026. Graphic by CantonNews.

The Canton team has published mitigation guidance for Java4Shell, a vulnerability in Java’s optimised Base64 processing. Base64 is a common way to represent data as text, including in authentication tokens. Its November 18 advisory recommends running the Java runtime with -XX:-UseBASE64Intrinsics until the appropriate patches are deployed.

The flag disables the affected optimisation. Canton’s engineers say their verification found no adverse performance impact on Canton. The advisory also highlights software commonly deployed alongside a node, including the login and access-management service Keycloak, rather than treating the node process as the only component to review.

What the issue affects

CERT-EU’s November 18 advisory identifies the issue as CVE-2026-114938, with a severity score of 8.1. Under particular hardware and application conditions, malformed input can cause memory corruption, service disruption or remote code execution.

CERT-EU describes affected x86-64 processors with specific AVX-512 capabilities and says ARM64 systems are unaffected. Exposure depends on the runtime, hardware and application path. The Canton notice is an operator advisory; it does not report a Canton network breach.

Review the Java runtime and related components, apply Canton’s interim mitigation, and deploy the appropriate patched build.

Operator response. Sources: Canton and CERT-EU.

Vendor patches and Canton packages are separate checks

The original Canton post says OpenJDK and downstream vendors had not released fixes. That statement should not be used as a current blanket description: Oracle’s November 17 security update lists CVE-2026-114938, and CERT-EU confirms fixes from Oracle and OpenJDK on that date.

Operators therefore need to check the Java distribution and version inside their actual deployment, including container images and associated services. Availability of a vendor fix does not by itself establish that a particular Canton image has been rebuilt with it.

Where to find the deployment instructions

Canton’s post supplies separate Docker and Kubernetes instructions. The Docker examples add the mitigation to both validator and participant JVM options. The Kubernetes example uses the additionalJvmOptions setting in both Helm deployments.

The Canton 3.7.4 maintenance release also appeared on November 18. Its release notes describe performance and correctness changes; they should not be treated as confirmation of Java4Shell remediation in every bundled Java runtime.

Sources: Canton mitigation instructions, CERT-EU vulnerability advisory and Oracle November security update.

Have a question about this story?
Ask CantonNews AI for context, its impact on the Canton ecosystem, or the latest related news.
Explore Further
Developer ResourcesExplore Daml, CIP-56 & Zenith →