Vendor disclosure: November 17, 2026. Last updated: November 18, 2026.
Summary
CVE-2026-114938 (also called Java4Shell) is a memory-corruption vulnerability in OpenJDK's accelerated Base64 decoder. On a vulnerable Java build running on an x86-64 CPU that exposes AVX-512 VBMI, processing attacker-controlled Base64 input can crash the JVM or, depending on the deployment, allow code execution. Apply a patched build from your Java vendor or the corresponding Etlworks package. If you cannot patch immediately, use the applicable interim mitigation below.
All Etlworks 10.x installations operated by Etlworks run on ARM64 and are unaffected by this vulnerability. If you run Etlworks on your own hosts or Kubernetes workers, or run your own Integration Agent, check the Java build and architecture of that workload.
Am I affected?
The vulnerable path is the Etlworks 10.x Java 25 runtime on x86-64 hardware that exposes AVX-512 VBMI:
- Native Etlworks on Windows x64 or Linux AMD64.
- Standalone Etlworks in Docker on Linux AMD64 hosts.
- Managed Kubernetes deployments with AMD64 workers (self-managed, Amazon EKS, Azure AKS, or Google GKE).
- A native Integration Agent, or an Agent container, running on such hardware.
Outside the vulnerable path:
- ARM64 deployments, and x86-64 CPUs that do not expose AVX-512 VBMI, are not exposed and do not need the mitigation flag for this CVE.
- The ordinary Etlworks Java 8 lane (legacy 9.x runtime) uses an OpenJDK distribution that is not on the vulnerable path. Oracle's advisory separately lists a special Java 8 performance build, so a custom or self-supplied JVM must be checked against its own vendor's advisory.
An Etlworks version or an operating system name alone — for example, RHEL 9 — is not enough to determine exposure: check the actual Java build and the actual CPU of the machine that runs the workload. The vendor advisories linked below carry each vendor's severity assessment.
How to check your runtime and CPU
- Native Etlworks: run sudo ./etlworks-cli.sh java status (Linux) or etlworks-cli.bat java status (Windows) from the installation's CLI folder. It prints the version and path of the Java runtime used by the running Etlworks Tomcat service.
- Native Integration Agent: run java status and doctor from the Agent launcher to see the Agent and updater runtime selections and the host architecture.
- Docker: run docker exec <container> java -version against the application or Agent container.
- Kubernetes: check every application pod and the worker architecture — see Update the Java runtime in the Kubernetes guide.
- CPU features: on Linux, follow Red Hat's check against /proc/cpuinfo on the relevant machine or VM (see the Red Hat advisory below). On Windows, identify the installed CPU and confirm its exposed features with the platform or CPU vendor's tools.
Note: a host's default java on the PATH, or the architecture of your own workstation, says nothing about the runtime of another service or an emulated workload. Always check the JVM the service actually uses, on the machine that runs it.
Choose a remediation
| Deployment | Permanent fix | If the patch must wait |
|---|---|---|
| Native Etlworks on Linux or Windows | Refresh the host CLI and run java update on the Etlworks Java 25 service. Verify the active JVM on each affected node. See Update the Java runtime (10.x). | Run java options add --option=-XX:-UseBASE64Intrinsics with the host CLI and verify the restart — same procedure. |
| Standalone Etlworks in Docker | Replace the application container with a verified patched image, preserving its data and configuration. See Update the Java runtime through the image. | Use etlworks-java options add inside the app container and restart; for older images, use the supported JAVA_TOOL_OPTIONS procedure — see Add a Java option to an existing Docker installation. |
| Native Integration Agent | Use the approved pinned runtime and update the Agent and updater (java update --component both). Verify maintenance completion and service status. See Private JVM maintenance. | Apply the option with the native Agent CLI and verify both services — see Set a JVM option on the installed services. |
| Integration Agent in Docker | Replace it with the verified patched Agent image — see Java maintenance in Docker. | Use the in-container Agent option command and restart; for older images use the supported Docker environment procedure — same section. |
| Customer-operated Kubernetes (self-managed, EKS, AKS, GKE) | Use the managed upgrade to a verified patched Etlworks release and verify all application pods. See Update the Java runtime and, for cloud workers, Java runtime and worker architecture. | Contact Etlworks Support for a supported path if a patched release for your deployment is unavailable. Do not edit pods or add JVM arguments outside the managed operation. |
| Etlworks 10.x operated by Etlworks | No customer action for the hosted application for this CVE (ARM64). | Assess separately any Integration Agent you operate yourself. |
About the interim mitigation
-XX:-UseBASE64Intrinsics temporarily disables hardware acceleration for Base64. -XX:+UnlockDiagnosticVMOptions lets the JVM accept that diagnostic option, and must come first. The current Etlworks commands (java options add, etlworks-java options add) add the unlock automatically; apply manual flags only to the affected services, using the documented procedure for that platform.
- The flags take effect when the affected JVMs restart. They do not install the vendor patch.
- After all affected processes have moved to a verified fixed build, remove the workaround through the same supported configuration channel, if appropriate. For a setting persisted by the Etlworks CLI, confirm the supported removal procedure with Etlworks Support.
Patched Java builds and availability
The reference patched Java 25 vendor builds for Etlworks deployments are Azul Zulu 25.38.201 (Java 25.0.5.1) for the native application, the standalone Docker application, and the Integration Agent on Linux and Windows, and Amazon Corretto 25.0.5.1.2 for the native Agent on macOS. These identify the vendor builds that contain the fix (see the vendor advisories below); whether a given Etlworks package already contains them is listed here:
- Available now: the current Linux and Windows installer and CLI bundles on the downloads page pin the patched build; refreshing the CLI and running java update installs it on a native 10.x installation (verified November 18, 2026).
- Not yet published as of November 18, 2026: the public etlworks/etlworks-app and etlworks/integration-agent Docker images and the current managed Kubernetes release still bundle a pre-fix Java build. For those deployments, apply the interim mitigation now and contact Etlworks Support for the patched package; this advisory will be updated when patched images and releases are published.
When contacting Support, include the full vendor build version (the java -version output), the architecture, the deployment type, and the image digest or installer version.
Vendor advisories
- Red Hat RHSB-2026-018 — architecture details, detection, and mitigation.
- Oracle November 2026 Java security advisory — affected Oracle builds, including a special Java 8 performance build.
- Azul Zulu November 2026 security fixes and build versions
- Amazon Corretto November 2026 security releases and the Amazon Linux 2023 Corretto 25 advisory