November 17, 2026
← All advisories

Java4Shell (CVE-2026-114938): Critical Java Flaw Hides Inside OT Software

Red Tiger Security infographic titled Java4Shell: Find the Java Hiding Inside Your OT Software, about CVE-2026-114938, a Base64 flaw in the Java Virtual Machine, from the CISA alert and Oracle fix of 17 November 2026. A large red callout shows a severity of 8.1 out of 10 (Oracle, CVSS 3.1; researchers rate it 9.2 under CVSS 4.0) and says real risk needs an affected Java 17 or later build, an x86-64 processor with AVX-512, and a way to send it Base64 data. Six tiles show where Java hides from plant floor to cloud: cloud gateways, DMZ and remote access, and engineering servers such as Jenkins and Jira (patch first); historians, HMI and SCADA web servers, and OT security tools (check with your vendor). Four steps: find every runtime, patch from the outside in, cut off access, and watch for Java crashes. Not in the CISA KEV catalog and no attacks reported as of 17 November 2026.

The Cybersecurity and Infrastructure Security Agency (CISA) issued an alert on 17 November 2026 urging organizations to patch CVE-2026-114938 right away. The researchers who found it call it "Java4Shell." It is a memory-corruption bug in the Base64 decoder of the HotSpot Java Virtual Machine (JVM), the engine inside the Java Development Kit (JDK) and Java runtimes, on x86-64 processors. Base64 is a common way of packing data into plain text, and it shows up in login headers, tokens, file uploads and network messages. CISA says specially crafted Base64 input could crash the JVM and allow unauthenticated remote code execution, meaning an attacker could run their own commands without logging in. The Canadian Centre for Cyber Security contributed to the alert. Oracle fixed the flaw in its November 2026 Critical Security Patch Update, released the same day, and scores it 8.1 out of 10 on the Common Vulnerability Scoring System (CVSS) version 3.1. Calif, the research firm that reported it, rates it 9.2 under CVSS version 4.0. As of 17 November, the flaw is not in CISA's Known Exploited Vulnerabilities (KEV) catalog, and no exploitation in the wild has been reported.

What is affected

Oracle lists these supported versions as affected: Oracle Java SE 8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3 and 27.0.1.0.3; Oracle GraalVM for JDK 17.0.21.0.3 and 21.0.13.0.3; and Oracle GraalVM Enterprise Edition 21.3.20.0.3. BleepingComputer reports that the bug sits in OpenJDK, the open-source code most Java builds come from, and affects OpenJDK 17.0.6 and later along with the builds made from it, including Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu and Red Hat OpenJDK.

Three things have to line up before a system is at real risk.

  1. The system runs an affected Java build.
  2. It runs on an x86-64 processor that supports the Advanced Vector Extensions 512 (AVX-512) instructions used by the faster, hardware-accelerated version of the decoder. Older processors and ARM processors do not run that code.
  3. An attacker can get their own Base64 data into that decoder. There is no single exploit that works everywhere, so the path depends on the application.

Calif reports that it achieved remote code execution without a login against Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins and PingFederate in their default configurations. It has published only a proof of concept that shows the memory corruption and is holding back the working attacks for now. Oracle notes that the flaw is reached by feeding data to the affected Java component, for example through a web service.

Where Java hides, plant floor to cloud

Red Tiger's view is that the hardest part of this one for industrial sites is finding the Java in the first place. Plant asset lists usually show product names, not the runtime underneath them. Many OT products ship their own private copy of Java inside the installation folder, and that copy never appears in the Windows installed programs list or in a normal patch report. CISA makes the same point about inventories.

On a typical site, Java can be running inside human-machine interface (HMI) and supervisory control and data acquisition (SCADA) web servers and thin-client portals, process historians and reporting servers, engineering and asset-management tools, and OT security and network monitoring appliances. Controls engineering groups often run Jenkins and Jira on their own servers to build and track projects, sometimes on the same network as the plant. Higher up, Java runs in the data gateways that move plant data to the business network and the cloud, in single sign-on services such as Keycloak, and in the container images behind cloud analytics platforms.

CISA and Oracle do not name any industrial control products in their advisories, and whether a given OT product carries an affected Java build is something only its vendor can confirm. Check with your vendor rather than assuming either way. For Java bundled inside an OT product, plan on the vendor's tested update instead of swapping the runtime yourself, because an untested change can break the application or your support agreement.

Start with the systems that can be reached from somewhere less trusted: anything in the demilitarized zone (DMZ) between the plant and business networks, remote access portals, historians that replicate to the business side, and cloud connectors. A Java-based engineering tool on a well-firewalled plant network sits lower on the list, but a JVM crash on an HMI or SCADA server is still an operations problem, so handle those with the same care.

What to do now

  1. Find every Java runtime, including the hidden ones. Search servers and workstations for java and javaw programs and for jre and jdk folders inside vendor installation directories, and check container images and appliance release notes. Ask each OT vendor in writing whether their product bundles Java 17 or later and when a fixed build will ship. Note which systems run on x86-64 hardware with AVX-512 support.
  2. Patch from the outside in. Start with internet-facing and DMZ systems, remote access portals, single sign-on services, and engineering servers such as Jenkins and Jira, using Oracle's November 2026 update or the fixed build from your Java distribution. Schedule vendor-supplied updates for HMI, SCADA and historian servers with operations, and keep a rollback plan.
  3. Where you cannot patch yet, cut down who can reach it. Block internet and business-network access to Java services that do not need it, and put remote access behind a virtual private network (VPN) with multifactor authentication. Calif suggests a temporary Java startup setting that turns off the vulnerable decoder (-XX:-UseBASE64Intrinsics). Use it on OT systems only with the vendor's agreement and after testing on a non-production system.
  4. Watch for the warning signs CISA lists. Look for unexpected JVM crashes and restarts, Java crash log files (named hs_err_pid followed by a number), unfamiliar Java processes, and Java runtimes that were not there before. Send those logs to whoever monitors your OT network.

Red Tiger can help with this beyond the assessment itself. During our onsite facility assessments, our team inventories the software on HMI, SCADA, historian and engineering systems, including bundled runtimes that do not show up on standard lists. We work with operators and vendors on a patching plan that keeps the plant running, and we can install a firewall and sensor at the site, connect them to the Red Tiger 24x7 security operations center (SOC), and monitor the plant for ongoing detection and response, with regular metrics and reports. Our team has completed more than 500 assessments and trained more than 4,500 people.

We are here to help, so check out our resources online at www.redtigersecurity.com and book a follow-up call with our team if you have any questions: https://calendly.com/jonathanpollet/30min

Source: CISA Alert, Critical Java Vulnerability Requires Immediate Patching, 17 November 2026: https://www.cisa.gov/news-events/alerts/2026/11/17/critical-java-vulnerability-requires-immediate-patching

← All advisories

Cite this advisory: Red Tiger Security, "Java4Shell (CVE-2026-114938): Critical Java Flaw Hides Inside OT Software", November 17, 2026, https://www.redtigersecurity.com/advisory/java4shell-cve-2026-114938-jvm-rce

Read the original source →

We are here to help.

Check out our resources and book a follow-up call with our team.

+1.877.387.7733