- Enterprise
· Updated · ASC Editorial Team
Java4Shell: Find Every Java Runtime, Including the Ones Inside Products You Bought
On 17 November 2026, Oracle released fixes for CVE-2026-114938, a flaw the researchers who found it have named "Java4Shell". The same day, CISA, the US cyber security agency, told organisations to patch immediately, with input from Canada's Cyber Centre. The flaw is in the Base64 decoder of the HotSpot Java virtual machine on x86-64 processors. CISA says specially crafted Base64 input could crash Java and allow remote code execution without logging in.
According to the researchers and the security firms that have analysed it, the flaw affects Java builds from 17.0.6 onwards, including Java 21, 25 and 27. It can only be exploited on x86-64 processors that support a feature called AVX-512 VBMI, which recent Intel Xeon and AMD Zen 4 and later processors have. Older Java 8 and 11 releases are reported as not affected. Oracle's advisory lists the affected products and versions.
No attacks had been confirmed by 18 November. But the cause of the flaw is public, and the researchers say details leaked before the patch was out. Base64 is used everywhere, so many applications decode text that an outsider can send them.
Patching Java on a server is the easy part. Java is also built into applications, container images and appliances, and CISA warns that these copies may not appear as separate entries in a software inventory. An operating system update won't fix a runtime that an application ships with its own installation. For those, you need a fix from the application's vendor.
The security vendors have started to respond: - Fortinet published advisory FG-IR-26-278 on 18 November and updated it on 19 November. It lists FortiOS, FortiProxy, FortiWeb, FortiManager, FortiClient and FortiNAC among the products not affected. It is still investigating more than 40 others, including FortiAnalyzer, FortiSIEM, FortiSandbox, FortiMail, FortiAuthenticator and FortiClient EMS. - Check Point published guidance on 18 November. It says a Check Point WAF signature blocks the public proof of concept, and that patching the Java runtime is the only complete fix. It does not say whether any Check Point products are affected. - Palo Alto Networks published an advisory on 19 November. Its firewalls and Panorama, which run PAN-OS, are not affected, and it is updating its cloud services itself. Several of its Idira privileged access products that customers run on their own servers are affected and need updating: Privilege Threat Analytics, Remote Access Connector and its CLI, and Secure Access with an HTML5 Gateway. Privilege Threat Analytics 15.0 has no fix, and Palo Alto advises moving to 15.2.3 or later.
CISA's advice, in order: - find every Java installation, including those bundled with other products; - apply Java and vendor patches as they become available, internet-facing systems first; - check Oracle's advisory for patching guidance; - watch for unexpected Java crashes, unfamiliar Java processes and runtimes nobody can account for.
Where you can't patch yet, CISA advises validating and limiting Base64 input where it enters your applications, and limiting access without a login. Check Point and other security firms describe a temporary Java startup setting that turns off the vulnerable decoder, `-XX:-UseBASE64Intrinsics`. Each Java process has to restart for it to take effect, and it may slow some applications. It doesn't replace the patch.
Start with the systems that face the internet, and with products whose vendors haven't yet said whether they are affected. If you run Idira on your own servers, apply Palo Alto's fixes. If you run any of the Fortinet products still under investigation, watch FG-IR-26-278 for updates.
Could you list today every Java runtime in your estate, including the ones inside products you bought?
Source: CISA: Critical Java vulnerability requires immediate patching
Get Insights by email
A short round-up of new articles every Monday morning. Nothing else.