Security

Java4Shell: CISA urges immediate patching of a critical Java vulnerability

CISA told organizations on Tuesday, November 17, to patch Java4Shell right away. The flaw in Java's Base64 decoder, tracked as CVE-2026-114938, could let an attacker run code on a server without logging in. Java runs inside many business apps that never show up as "Java" in an inventory, so finding every copy is the hard part.

By Techieslite ·

Techieslite graphic with the OpenJDK logo and the headline "Java4Shell: CISA urges immediate Java patching"

What the flaw does

CISA describes Java4Shell as a memory corruption bug in the Base64 decoder of the HotSpot Java virtual machine on x86-64 processors. Specially crafted Base64 input can crash the JVM and could allow unauthenticated remote code execution, the agency says.

Security firm Calif, which found and reported the bug, says the problem sits in a hardware-accelerated decoding path that uses the AVX-512 VBMI instructions. Only x86-64 processors with that feature are exposed. Calif names Intel Xeon chips from the Ice Lake, Sapphire Rapids, Emerald Rapids and Granite Rapids families, plus AMD processors from Zen 4 onward. Calif says ARM64 systems are not affected.

Oracle, which assigned the CVE, rates the flaw 8.1 out of 10 on the CVSS 3.1 scale and describes it as difficult to exploit. Calif scores it 9.2 under CVSS 4.0. As of November 17, the flaw was not in CISA's Known Exploited Vulnerabilities catalog, and CISA's own assessment in the CVE record lists no known exploitation.

Which Java versions are affected

Oracle's CVE record lists these releases as affected:

Calif says OpenJDK 17.0.6 and newer are vulnerable. That includes builds based on OpenJDK such as Amazon Corretto, Eclipse Temurin, Azul Zulu and the Microsoft Build of OpenJDK. The standard Java 8 and Java 11 releases are not on Oracle's affected list.

Oracle released fixed builds on November 17. According to Tenable, they are versions 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1. Amazon also shipped Corretto 21.0.13.1.2 that day with the fix. Other vendors are on their own schedules, so check each one's release notes.

Which apps are exposed

Calif says its tests reached remote code execution without a login in Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins and PingFederate in their default setups. It also lists Apache Kafka, Apache Solr, Elasticsearch, Gerrit and Spinnaker as exploitable after login, and calls the list incomplete.

Calif says it is holding back its working exploits for specific products to give people time to update. Its public proof of concept triggers the bug without taking control of a system.

What it means for you

The apps Calif tested are server software, so admins of self-hosted business tools have the most urgent work. If your company or small business runs Jira, Confluence, Jenkins or another Java-based tool on its own hardware or cloud servers, ask whoever maintains it whether the Java runtime has been updated. Calif also says a client-side exploit works against Java programs that open TLS connections to malicious servers, so the risk isn't limited to server software.

CISA's advice for admins:

As a stopgap, Calif suggests starting Java with the -XX:-UseBASE64Intrinsics option, which turns off the accelerated decoder, but it recommends updating Java as the fix. Older servers without AVX-512 VBMI support, and ARM-based servers, aren't exposed to this bug, but they should still get the update.

Sources