CVE-2026-114938 (Java4Shell)
Etlworks Cloud is not affected by CVE-2026-114938 (Java4Shell). Self-hosted Etlworks 10.x and Integration Agents on x86-64 CPUs that expose AVX-512 VBMI are affected through the bundled Java 25 runtime: update the Java runtime, or apply the interim mitigation until you can.
Am I affected?
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.
| Deployment | Status | Notes |
|---|---|---|
| Etlworks Cloud (10.x operated by Etlworks) | Not affected | Runs on ARM64. No action for the hosted application. |
| Self-hosted 10.x on x86-64 with AVX-512 VBMI | Action required | Windows x64, Linux AMD64, Docker on AMD64 hosts, Kubernetes with AMD64 workers. |
| Integration Agent on such hardware | Action required | Native Agent or Agent container. |
| ARM64, or x86-64 without AVX-512 VBMI | Not affected | Not on the vulnerable path; no mitigation needed for this CVE. |
| Java 8 lane (legacy 9.x runtime) | Not affected | Its OpenJDK distribution is not on the vulnerable path. A custom JVM must be checked against its vendor's advisory. |
An Etlworks version or an operating system name is not enough: check the Java build and the CPU of the machine that runs the service. On native installations, etlworks-cli java status prints the runtime the service uses; in Docker, run java -version inside the container.
What to do
| Deployment | Fix | Permanent fix | If the patch must wait |
|---|---|---|---|
| Native Etlworks on Linux or Windows | Fix available | Refresh the host CLI and run java update on the Etlworks Java 25 service. | java options add --option=-XX:-UseBASE64Intrinsics with the host CLI, then restart. |
| Native Integration Agent | Fix available | Update the Agent and updater to the approved pinned runtime (java update --component both). | Set the option with the Agent CLI on both services. |
| Standalone Etlworks in Docker | Fix pending | Replace the container with a patched image when it is published. | etlworks-java options add inside the container, then restart. |
| Integration Agent in Docker | Fix pending | Replace it with the patched Agent image when it is published. | Use the in-container Agent option command, then restart. |
| Customer-operated Kubernetes (self-managed, EKS, AKS, GKE) | Fix pending | Managed upgrade to a patched Etlworks release when it is published. | Contact Etlworks Support for a supported path. Don't edit pods or add JVM arguments by hand. |
| Etlworks Cloud | No action | No action for the hosted application. | Check any Integration Agent you run yourself. |
As of November 18, 2026, the Linux and Windows installer and CLI bundles on the downloads page pin the patched build. The public etlworks/etlworks-app and etlworks/integration-agent Docker images and the managed Kubernetes release are not yet updated: apply the interim mitigation and contact Etlworks Support.
Interim mitigation
-XX:-UseBASE64Intrinsics turns off the hardware-accelerated Base64 path. The current Etlworks commands add the required -XX:+UnlockDiagnosticVMOptions automatically. The flag takes effect when the JVM restarts and does not install the patch; remove it once every affected process runs a patched build.
Patched Java builds
- Azul Zulu 25.38.201 (Java 25.0.5.1): native application, standalone Docker application, Integration Agent on Linux and Windows
- Amazon Corretto 25.0.5.1.2: native Integration Agent on macOS
Full instructions
Step-by-step commands, how to check each runtime and CPU, and updates as patched images ship are in the support article, which is the reference for this advisory.
Read the full advisory on support.etlworks.com
Etlworks guides
Questions, or need a patched package for your deployment? Write to support@etlworks.com with your java -version output, architecture and deployment type. To report a vulnerability, write to security@etlworks.com.