Summary
A critical vulnerability — CVE-2026-114938, known as "Java4Shell" — has been disclosed in the OpenJDK Java runtime. It is a heap buffer overflow in the hardware-accelerated (AVX-512) Base64 decoder the JVM uses on x86-64 processors, and can cause crashes and, under some conditions, remote code execution.
Conduktor products run on the JVM and are affected. Patched builds are being released today, and an immediate mitigation is available below.
At a glance
Vulnerability
CVE-2026-114938 ("Java4Shell") — OpenJDK Base64 decoder heap overflow
Affected
Conduktor Console, Gateway and Schema Registry Proxy running on x86 / x86-64
Not affected
Any deployment running on Arm (aarch64)
Patch
Patched builds of the latest release ship today, 19 Nov 2026
Mitigation
Set the JVM flag -XX:-UseBASE64Intrinsics on each component and restart
Am I affected?
- x86 / x86-64 (Intel / AMD): Yes — apply the patch or the mitigation below.
- Arm (aarch64 — e.g. AWS Graviton, Apple Silicon): No. The vulnerable code path exists only in the x86 AVX-512 implementation. No action required.
Recommended action — upgrade
Patched builds of the latest release of each affected product are being published today. Upgrade to these (or later) versions and restart:
Conduktor Console
1.48.2
Conduktor Gateway
3.22.4
Conduktor Schema Registry Proxy
1.0.2
Mitigation without a patch
If you cannot upgrade immediately, disable the vulnerable Base64 intrinsic with the JVM flag -XX:-UseBASE64Intrinsics. This is a stopgap, not a fix — please still plan to upgrade.
Set the flag through each component's JVM-options environment variable and restart it. Console reads its options from CONSOLE_JAVA_OPTS; Gateway and Schema Registry Proxy use the standard JAVA_TOOL_OPTIONS:
Conduktor Console
CONSOLE_JAVA_OPTS=-XX:-UseBASE64Intrinsics
Conduktor Gateway
JAVA_TOOL_OPTIONS=-XX:-UseBASE64Intrinsics
Conduktor Schema Registry Proxy
JAVA_TOOL_OPTIONS=-XX:-UseBASE64Intrinsics
The flag is recognised on both x86 and Arm, so applying it fleet-wide is safe. On Arm it provides no security benefit — the vulnerability is specific to the x86 Base64 intrinsic. It does still disable the (unaffected) Arm Base64 intrinsic, falling back to the standard Java implementation, which is at most a negligible performance difference; Arm-only deployments can simply omit it.
Docker / Docker Compose — add to each service's environment: block:
ervices:
conduktor-console:
environment:
CONSOLE_JAVA_OPTS: "-XX:-UseBASE64Intrinsics"
conduktor-gateway:
environment:
JAVA_TOOL_OPTIONS: "-XX:-UseBASE64Intrinsics"
schema-registry-proxy:
environment:
JAVA_TOOL_OPTIONS: "-XX:-UseBASE64Intrinsics"Kubernetes / Helm — set the same variables in each container's env: (or your Helm values) and roll the pods.
Verify it is active
The mitigation only takes effect after a restart, and only if the flag reaches the running JVM. Check the live process for any component:
jcmd <pid> VM.flags | grep UseBASE64Intrinsics # expect: -UseBASE64IntrinsicsFor Gateway and Schema Registry Proxy you can also confirm from the startup logs, which show:
Picked up JAVA_TOOL_OPTIONS: -XX:-UseBASE64IntrinsicsConsole uses CONSOLE_JAVA_OPTS and does not print that line — use the jcmd check above for Console.
⚠️ Do not use
-XX:UseAVX=2on Arm. Some third-party advisories suggest-XX:UseAVX=2as an alternative. It is x86-only: on Arm the JVM does not recognise the option and fails to start (Unrecognized VM option 'UseAVX=2'). Use-XX:-UseBASE64Intrinsics, which is safe on every architecture.
Comments
0 comments
Article is closed for comments.