Java4Shell (CVE-2026-114938): Interim Mitigation

v2 / updated: Nov 18, 2026: corrected the Designer check, clarified Ignition 7.9 and earlier, added a Linux processor check

A critical vulnerability in Java, called Java4Shell (CVE-2026-114938), was published on November 17, 2026. It is a memory corruption flaw in the routine Java uses to decode Base64 data on some Intel and AMD processors. An attacker who can send crafted data to a Java program may be able to crash it or run code in it.

Ignition bundles an affected version of Java. Ignition 8.1.56 and 8.3.11 will bundle a fixed version, and so will an upcoming Ignition 2027 beta. Until you can upgrade, add one Java option to each affected Ignition runtime, as described below.

Affected. Both of these must be true:

  1. The software is Ignition 8.1.33 through 8.1.55, Ignition 8.3.0 through 8.3.10, or the Ignition 2027 beta. This covers every edition (Ignition, Edge, Maker, Cloud Edition) and every component that runs Java: the Gateway, Designer, Vision Client, launchers, and Perspective Workstation.
  2. It runs on a 64-bit Intel or AMD processor with the AVX-512 VBMI feature: Intel Xeon processors from the "Ice Lake" generation (2021) on, some 10th and 11th generation Intel Core processors, and AMD processors from "Zen 4" on (Ryzen 7000, EPYC 9004). Virtual machines and cloud instances on these processors count.

If you aren't sure about the processor, apply the mitigation. It is safe on any processor.

On Linux, this command shows whether the processor is an affected one. It prints avx512vbmi if it is, and nothing if it isn't:

grep -m1 -o avx512vbmi /proc/cpuinfo

Not affected: Ignition 8.0 through 8.1.32, which bundle Java 11; ARM systems, including Apple silicon Macs and Raspberry Pi; Perspective sessions in a web browser; and the Perspective mobile apps. Ignition 7.9 and earlier don't bundle Java, so it depends on the Java installed for them. The flaw is in Java 17.0.6 and later; the Java 8 those versions normally run on is not affected.

Priority. Start with Gateways, above all any that can be reached from the internet or from networks you don't fully control: Ignition decodes Base64 data in some requests before a user logs in. Client machines come next. A Designer, Vision Client, launcher, or Workstation is exposed only to the servers it connects to.

The mitigation. Add this Java option to each affected runtime and restart it:

-XX:-UseBASE64Intrinsics

It turns off the accelerated Base64 routine that has the flaw, and Java uses its standard routine instead. Nothing else changes, except that Base64 encoding and decoding run slower. We don't expect a noticeable effect on Ignition. Other public guidance also lists -XX:UseAVX=2. Don't use that one for Ignition: on an ARM system, Java won't start with it.

Gateway

  1. Open ignition.conf in the Gateway's data folder. By default that folder is C:\Program Files\Inductive Automation\Ignition\data on Windows, /usr/local/bin/ignition/data on Linux, and /usr/local/ignition/data on macOS.
  2. Under "Java Additional Parameters", add a line with a number that no other wrapper.java.additional line uses (7 in an unchanged file):
wrapper.java.additional.7=-XX:-UseBASE64Intrinsics
  1. Restart the Gateway service.

Do this on every Gateway, including redundant backups, EAM agents, and Edge Gateways.

The Gateway's command-line tools (gwcmd and, on 8.3 and later, ignition-secrets-tool) need no change. They run on the Gateway's Java for a few seconds at a time and take no input from the network.

Gateway in Docker. Add the option after -- at the end of the container's arguments, then recreate the container:

docker run ... inductiveautomation/ignition:8.3.10 -n my-gateway -- -XX:-UseBASE64Intrinsics

In a Compose file:

command: -n my-gateway -- -XX:-UseBASE64Intrinsics

Client machines (Designer, Vision Client, launchers, Perspective Workstation). There are two ways. Use the first unless the machine also runs Java 8 programs.

Option 1: one setting for the whole machine. Set the environment variable JAVA_TOOL_OPTIONS to -XX:-UseBASE64Intrinsics. Every Java program started on that machine afterward reads it: launchers, Workstation, Designers, and Vision Clients, including Vision Clients after a retarget.

Windows (Command Prompt, run as Administrator):

setx /M JAVA_TOOL_OPTIONS "-XX:-UseBASE64Intrinsics"

Linux: add this line to /etc/environment:

JAVA_TOOL_OPTIONS=-XX:-UseBASE64Intrinsics

Then sign out, sign back in, and relaunch.

Two cautions. Java 8 doesn't know this option and won't start while the variable is set, so don't use Option 1 on a machine that also runs Java 8 programs, including Ignition 7.9 clients. And if JAVA_TOOL_OPTIONS already has a value, add the option to that value instead of replacing it; the setx command above replaces it.

Option 2: each application separately

Designer and Vision Client: in the Designer Launcher or Vision Client Launcher, open the application's three-dot menu, select Manage, and add -XX:-UseBASE64Intrinsics to JVM Arguments. If the field already has arguments, separate them with a semicolon and no spaces. Save and relaunch. Repeat for each application in each launcher.

Launchers and Perspective Workstation on Windows: in the launcher's install folder, next to its .exe file, create a text file with the same name and the extension .l4j.ini, containing the single line -XX:-UseBASE64Intrinsics. The file names are designerlauncher.l4j.ini, visionclientlauncher.l4j.ini, and perspectiveworkstation.l4j.ini. Then close and reopen the launcher.

Launchers and Perspective Workstation on Linux and Intel Macs: use Option 1.

Vision Clients that retarget. A retarget starts a new Java process. That process doesn't keep the launcher's JVM Arguments, and it uses the runtime of the Gateway it retargets to. On machines whose clients retarget, use Option 1. A Vision Client can also restart itself this way while it launches, so Option 1 is the dependable choice for Vision Clients in general.

Check

Gateway: confirm the option is on the running Java process. Each command prints the Gateway's Java process when the option is active, and nothing when it isn't.

Windows (PowerShell, run as Administrator):

Get-CimInstance Win32_Process -Filter "Name='java.exe'" | Where-Object CommandLine -match 'UseBASE64Intrinsics' | Select-Object ProcessId, Name

Linux and macOS:

ps -ef | grep "[U]seBASE64Intrinsics"

Docker: the container log shows Collected JVM arg: -XX:-UseBASE64Intrinsics at startup.

Designer: run this in the Script Console. It reports on the Java the Designer itself is running, on that machine, not on the Gateway. false means that Java is not using the accelerated routine, so nothing more is needed there. You will see false after applying the mitigation, and also before it on Ignition 8.1 and 8.3 when the processor isn't an affected one. true means the routine is in use: apply the mitigation. The same script works in a Vision Client, for example on a button.

from java.lang.management import ManagementFactory
from com.sun.management import HotSpotDiagnosticMXBean
print ManagementFactory.getPlatformMXBean(HotSpotDiagnosticMXBean).getVMOption("UseBASE64Intrinsics").getValue()

To undo: remove the line, variable, argument, or file you added, and restart.

What comes next. Ignition 8.1.56, Ignition 8.3.11, and an upcoming Ignition 2027 beta will bundle a fixed Java runtime. After you upgrade a Gateway, Designers and Vision Clients download the fixed runtime the next time they launch from it. Launchers and Perspective Workstation carry their own runtime, so download and install them again from the upgraded Gateway. A Vision Client uses the runtime of the Gateway it is connected to, so upgrade every Gateway that clients retarget to. Once everything is upgraded, remove the option (see To undo). It no longer protects anything, it slows Base64 work, and an option left behind can stop a later Java version from starting if that version no longer has it. On client machines, keep the option until every Gateway they connect to is upgraded and their launchers are reinstalled.

We will update this post when the releases are available.

4 Likes

Running the Python code provided in the script console is giving me false despite not yet having applied the mitigation. This is on Ignition 8.3.9 running in Docker on Ubuntu 24.04.2:

image

The script console runs in your Designer in a different JVM than the Gateway, you would have to apply those as launch arguments in the launchers as well to see it there.

2 Likes

Is there a central location of known Ignition CVE's that I can track to see which versions are affected and when I should update? Thanks!

We've updated the post above to v2. What changed:

  • The Designer check was described incorrectly. As Kevin said, the script reports on the Java your Designer is running, not the Gateway's. false means that Java isn't using the accelerated Base64 routine. On 8.1 and 8.3 that is also the default when the processor doesn't have AVX-512, which is why @lucs100 saw false before applying anything: the machine running that Designer isn't an affected one. It says nothing about the Gateway's machine.
  • There is now a one-line check for Linux that shows whether a processor is an affected one. That is the way to check a Gateway host.
  • Ignition 7.9 and earlier don't bundle Java, so it depends on the Java installed for them.

@drewdin Security advisories for Ignition are posted on our Security Trust Portal, in the Trust Center Updates section: https://security.inductiveautomation.com/. You can subscribe to updates there.

1 Like