Key facts
- Oracle issued patched builds for Java4Shell on November 17, 2026.
- Calif rated Java4Shell 9.2 under CVSS 4.0, while Oracle rates it 8.1 under CVSS 3.1.
- Qualys reported on November 17, 2026 that it had seen no public confirmation of wild exploitation, and Cycode said no exploitation had been reported as of November 18, 2026.
- Oracle fixed Java SE builds are 17.0.21.1, 21.0.13.1, 25.0.5.1, and 27.0.1.1.
SANS Internet Storm Center kept Infocon at Green on Nov. 18, 2026, despite a major Microsoft 365 outage and the disclosure of critical Java and NGINX vulnerabilities that day.
Johannes B. Ullrich, Ph.D., dean of research at SANS.edu, wrote on Nov. 18, 2026 that keeping an alert status high at all times makes it meaningless and counterproductive. Organizations should expect a normal 9-to-5 day while Infocon remains Green, he wrote, and some organizations have used SANS infocon status to justify staffing and overtime. He wrote that defenders should not treat recent vulnerabilities as emergencies because they are the new normal.
SANS moved to Infocon Yellow about a month before Nov. 18, 2026 for the first time in years because of the php2shell vulnerability. Ullrich wrote that some organizations have used SANS infocon status to justify staffing and overtime. He wrote that current conditions call for new procedures and techniques instead of focusing on the latest vulnerability, and he wrote that patching nginx2shell across a large organization is not possible before anyone releases an exploit.
The disclosure builds on Calif’s earlier PHP2Shell work and the emergency PHP patches that came before it. Calif found memory flaws in both shared runtime investigations, though the PHP issues and Java4Shell stem from different causes and need separate fixes.
Java4Shell is tracked as CVE-2026-114938, a memory-corruption flaw in OpenJDK’s Base64 decoder that sits in HotSpot, the Java Virtual Machine used by many OpenJDK distributions.
Calif researcher Quang Luong identified the issue while examining OpenJDK HotSpot with help from an AI coding tool, and Calif rated Java4Shell 9.2 under CVSS 4.0, a vulnerability severity scoring system. Oracle attributes the report to Albert Yang and Quang Luong of Calif.io and rates the flaw 8.1 under CVSS 3.1.
Oracle issued patched builds for Java4Shell on Nov. 17, 2026. The fixed Java SE builds are 17.0.21.1, 21.0.13.1, 25.0.5.1, and 27.0.1.1. Oracle says standard Java 8 and Java 11 are not affected, with one exception: the 8u511b33-perf Enterprise Performance Pack build of Java SE 8.
The flaw can be triggered only on x86-64 processors with AVX-512 VBMI, such as Intel Xeon chips from Ice Lake through Granite Rapids and AMD EPYC processors from Zen 4 onward. ARM64 systems are not affected by the vulnerable code path. Thetechhacker says ARM64 machines such as Apple Silicon Macs and AWS Graviton servers are reportedly not affected, but teams should patch anyway because images and servers move between hardware. End-of-life Java releases 18 to 20, 22 to 24, and 26 contain the same vulnerable code and will receive no fix.
No confirmed exploitation in the wild had been reported as of Nov. 18, 2026. Qualys said on Nov. 17, 2026 that it had seen no public confirmation of wild exploitation, and Cycode said none had been reported as of Nov. 18, 2026. Check Point said as of Nov. 18, 2026 that it was not aware of confirmed exploitation, and Thetechhacker reported that Aikido did not list the flaw in CISA’s Known Exploited Vulnerabilities catalog.
SANS itself had seen many attacks against its Java-specific honeypots but none exploiting Java4Shell as of Nov. 18, 2026. The root cause and a triggering input have been public since Sept. 9, 2026, according to Check Point.
Researchers used AI to find the bug in roughly one hour and produced a first working exploit two hours later at a cost below $200 in AI tokens. They are withholding product-specific exploit code to give organizations time to upgrade and intend to release it later.
The researchers disclosed that information about the vulnerability became public before a fix existed. Calif said there is no single exploit that works across all Java applications, and WatchTowr expects attackers to tailor attacks to individual products because the CPU, JDK, and Base64 usage vary by target; the demonstrations establish code execution is possible but are not evidence of attacks against production systems.
A short malformed Base64 input makes the decoder write past the end of its buffer before Java rejects the input. Qualys states the flawed decoder writes 62 bytes past the end of a buffer, while Check Point describes the overflow as 62 or 63 bytes depending on padding.
The flaw can crash the JVM, creating availability risk, and can expose heap memory such as private keys, tokens, and personal data. A remote attacker without credentials can damage Java heap memory, extract secrets, and achieve remote code execution. Calif demonstrated pre-authentication remote code execution on default installations of Keycloak, Jira, Confluence, Artifactory, Jenkins, and PingFederate, and it also achieved code execution in sample applications based on Apache Struts and Spring Boot, saying authentication was needed for tests against Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit, and Spinnaker.
Applications often decode Base64 before authentication, including in HTTP Basic headers, SAML artifacts, CSRF tokens, and file uploads. Calif described a client-side attack in which attackers compromise a Java program after it opens a TLS connection to a malicious server, and it compared the memory exposure to Heartbleed because an attack could expose session tokens or private keys, though the two issues have different origins. Base64 represents binary data as text so applications can pass it through systems that expect text, and it is common in sign-in flows, file uploads, and network messages.
On its own, the overflow usually crashes Java because the bytes written are fixed, Check Point says. Calif reported shaping server memory so the overflow enlarges a neighboring array, which then gives read and write access and leads to code execution.
Check Point lists three requirements for exposure: an unpatched runtime, a particular processor, and Base64 controlled by an attacker that reaches Java’s standard decoder. Qualys says no universal exploit exists since every product requires its own chain, and network conditions affect the technique; this slows mass exploitation but leaves a chosen target such as an identity provider exposed. Qualys makes the same point about product-specific chains and network conditions.

Apache Tomcat was not tested and no advisory links it to this CVE, but it runs a large share of Java web applications and Spring Boot embeds Tomcat by default, so teams should include every Tomcat server in their inventory. Check Point places every Spring Boot service on an affected runtime within scope because researchers reached code execution in sample applications where login handling, tokens, and file uploads decode Base64 before authentication.
The risk applies to self-managed Atlassian Jira and Confluence Data Center deployments. Atlassian runs the Java runtime for Atlassian Cloud, and Atlassian installers usually include a bundled runtime, which means operating system patches by themselves cannot repair a self-managed instance. Elasticsearch ships with a bundled Java runtime, and Calif demonstrated code execution against it after login. Because that attack works in a single complete request, request buffering by a reverse proxy such as nginx does not stop it; teams should treat clusters with anonymous access or weak credentials as exposed without a login.
CISA released an alert pressing organizations to apply Java4Shell patches without delay, advising teams to focus on internet-facing systems and to look for runtimes bundled with third-party software, container images, and appliances. CISA also says to restrict unauthenticated access, check Base64 input before it reaches the decoder, and enforce input-size limits while teams prepare updates.
These controls are temporary, not replacements for patching the runtime, and size limits alone will not stop the bug because the malformed input is short; the JVM flag is the more direct stopgap. Qualys says request buffering breaks some exploit chains, so it cannot serve as a general mitigation, and teams should not depend on a reverse proxy as a control.
Qualys recommends reducing exposure by taking identity, build, and collaboration consoles off the open internet, or putting them behind a VPN, until teams patch them, and it is hosting a Java4Shell briefing on Nov. 19 at 12:00 p.m. ET. Check Point released an IPS protection that detects and blocks the public proof-of-concept for CVE-2026-114938; teams should set it to Prevent on Quantum gateways, especially for traffic to internet-facing Java services, though it targets the known triggering input and not every possible variant.
A JVM startup flag, -XX:-UseBASE64Intrinsics, turns off the vulnerable fast Base64 decoder as a temporary workaround. An alternative flag, -XX:UseAVX=2, turns off AVX-512 on x86-64 only; Java on ARM does not accept it and will not start. Check Point warns against using -XX:DisableIntrinsic=_base64_decodeBlock on its own because it can stop Java from starting.
A patch or flag takes effect only after the JVM restarts, so teams should verify the running process rather than only the installed package. Check Point advises confirming the running version with jcmd <pid> VM.version and jcmd <pid> VM.flags; VM.version should show a fixed build such as 17.0.21.1 for Oracle. Teams should watch for unexpected restarts of services and new hs_err_pid<pid>.log files, Check Point says, because failed attempts often crash Java; the JVM writes these files after a fatal crash, and crashes during garbage collection also signal this corruption.
As of Nov. 18, 2026, fixed builds had shipped from Oracle, Amazon Corretto, and Azul Zulu, with Oracle patching only builds ending in .1. Red Hat and Eclipse Temurin had not yet released fixes, while Microsoft Build of OpenJDK and BellSoft Liberica were unconfirmed.
Oracle’s November 2026 Critical Security Patch Update lists CVE-2026-114938 under the Compiler component of Oracle Java SE, Oracle GraalVM for JDK, and Oracle GraalVM Enterprise Edition. Oracle rates attack complexity as high and says attackers can exploit it remotely without authentication by supplying data to affected APIs, for example through a web service.
Amazon Corretto released fixed build 17.0.21.1.2 as of Nov. 17, 2026. Thetechhacker reports Amazon Corretto fixed builds as 17.0.21.1.2, 21.0.13.1.2, 25.0.5.1.2, and 27.0.1.1.4, and Eclipse Temurin fixed builds as 17.0.21.1+2, 21.0.13.1+2, 25.0.5.1+2, and 27.0.1.1+4. Cycode’s Nov. 18, 2026 update says Amazon, Azul, and Oracle GraalVM had released fixed builds, and Eclipse Temurin had fixed builds for Java 21, 25, and 27; Temurin for Java 17, Red Hat, and Microsoft had not published fixed builds when checked, and Debian had fixed packages only in unstable.
For containers already running, pulling a new tag does nothing, Thetechhacker says, so teams must rebuild images from a fixed base image and redeploy them. Corretto images on Docker Hub keep the same version tags, so users should pull them again after the fix. Organizations should assign an owner and a remediation deadline to every Java system still waiting on a vendor build.
Qualys recommends beginning remediation with internet-facing identity systems like Keycloak and PingFederate, followed by internet-facing Jira, Confluence, Jenkins, and Artifactory. Check Point advises patching identity providers first, then Jira, Confluence, Jenkins, and Artifactory, then other internet-facing Java services, then internal systems and Java clients. If teams cannot rule out that attacker input reaches Java’s built-in Base64 decoder, they should assume it does; vendor advisories cover only Java 17, 21, 25, and 27, so teams should move any other release to a fixed build rather than assume it is safe.
Ullrich recommended automating patching for less critical systems, reducing exposure, building defensible architecture, avoiding chasing squirrels, improving tooling and resources, and embracing AI tooling. SANS advised selecting less critical systems at the end of the patch priority list for automated patching and accepting possible downtime rather than risking ransomware, and it also advised reducing supply chain exposure and questioning whether tools such as Optimizely provide enough value to justify the risk. Thetechhacker notes that supply-chain and web attacks moved fast this month, citing the Optimizely hack that hit 178 organizations.
Patches are available for Oracle Java SE, Amazon Corretto, and Azul Zulu builds, while Red Hat, Eclipse Temurin for Java 17, Microsoft, and Debian stable had not published complete fixes as of Nov. 18, 2026, and end-of-life Java 18 to 20, 22 to 24, and 26 will not be fixed. Defenders should confirm the running JVM version after any restart and prioritize internet-facing identity and collaboration services for patching or network isolation.

Join the discussion