Sorting by

×

Java4Shell Vulnerability Allows Remote Code Execution Without Login

A newly discovered security flaw called the Java4Shell vulnerability (CVE-2026-114938) is putting several widely used enterprise applications at risk. The flaw could allow attackers to execute their own code on vulnerable servers, even without having a user account.

The affected applications include Atlassian Jira, Confluence, Jenkins, Keycloak, JFrog Artifactory and PingFederate. Security researchers at Calif disclosed the issue on November 18, 2026, and rated it 9.2 out of 10 under CVSS 4.0.

The vulnerability affects certain Java versions running on supported Intel and AMD processors. Oracle and several Java vendors have already released security updates.

How Does the Java4Shell Vulnerability Work?

The problem exists in Java’s optimized Base64 decoder. This decoder is designed to process data faster on certain x86-64 processors that support the AVX-512 VBMI feature.

However, a specially crafted Base64 string ending with an extra equal sign (=) can cause the decoder to write beyond its allocated memory. Java detects the invalid input, but only after the memory has already been changed.

Attackers may exploit this weakness through login headers, SAML data and other tokens that applications process before checking user authentication.

Researchers say they can use this memory corruption to access sensitive data and potentially reach code execution. However, each application requires a different attack method, and the researchers have not released their complete exploit code.

Which Applications and Java Versions Are Affected?

The vulnerability affects Java 17.0.6 and later, along with certain Java 21, 25 and 27 builds. Standard Java 8 and Java 11 are not affected, although a special Java 8 Performance Pack build is vulnerable.

Application or platformAttack requirement
Jira and ConfluenceNo login required under default settings
JenkinsNo login required under default settings
KeycloakNo login required under default settings
JFrog ArtifactoryNo login required under default settings
PingFederateNo login required under default settings
Apache Kafka and ElasticsearchLogin required

The vulnerable code only runs on supported x86-64 processors with the required CPU features. ARM64 systems are not affected by this specific code path.

Java4Shell Fixes and Security Updates

Oracle has released patched versions, including Java 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1. Amazon Corretto and Azul Zulu have also published fixes.

Red Hat was still preparing updates for its affected OpenJDK builds at the time of the report. Organizations using Red Hat systems should monitor its security advisories.

Administrators should update Java, restart affected services and rebuild container images to ensure applications use the patched runtime.

Temporary Protection and Detection

If an update is not immediately possible, administrators can temporarily disable the vulnerable optimized decoder by starting the Java Virtual Machine with:

-XX:-UseBASE64Intrinsics

Another option is -XX:UseAVX=2, which disables AVX-512 support on x86-64 systems.

Security teams should also monitor unusual Base64 tokens, repeated Java decoder errors and unexpected JVM crash logs. These signs do not confirm an attack, but they may help identify suspicious activity.

Why Organizations Should Act Quickly

The Java4Shell vulnerability is serious because attackers may reach vulnerable applications without authentication. Although confirmed real-world exploitation had not been reported in the supplied update, organizations should identify affected Java installations and apply available patches as soon as possible.

Leave a Reply

Your email address will not be published. Required fields are marked *