java4shell-java-applications

Oracle and OpenJDK have fixed “Java4Shell,” a vulnerability in Java that allowed applications such as Jira, Confluence, and Jenkins to be taken over without a password. Ask who manages your servers.

The vulnerability, CVE-2026-114938 (score 8.1 according to Oracle, 9.2 according to researchers) is a write-out-of-bounds vulnerability in the Java virtual machine’s Base64 decoder—that is, in the code that decodes text such as that found in authentication headers. A specially crafted message can crash the application or, under certain conditions, execute code on the server without any user privileges. The U.S. Cybersecurity and Infrastructure Security Agency (CISA) has called for immediate application of the patches, and Oracle and OpenJDK have released the updates. So far, there is no evidence of exploitation in actual attacks, but the technical details are public.

The gap occurs only when two conditions are met:

  • Java 17.0.6 or later (including 21, 25, and 27), in unpatched versions; standard Java 8 and 11 are not affected;
  • an x86-64 processor with AVX-512 VBMI instructions: most Intel Xeon servers from recent years and AMD EPYC or Ryzen processors from the Zen 4 generation and newer. ARM servers are not affected.

Researchers have demonstrated that, by default, Atlassian Jira and Confluence, Jenkins, Keycloak, JFrog Artifactory, and PingFederate are vulnerable to unauthenticated access. Kafka, Solr, Elasticsearch, and others are only vulnerable if the attacker already has an account. Java often comes “bundled” with purchased software, hardware, and containers, so a server can be compromised without anyone having installed Java separately.

Here's what this means for you: A small company usually doesn't run Jira or Jenkins on its own server, but many management programs, customer portals, or applications provided by a vendor run on Java. If everything you use is in the cloud (for example, Jira Cloud), the vendor is responsible for the fix.

What you need to do:

  • Ask your IT provider if you have any servers or applications running on Java 17 or later and if they have received the patched version (Oracle Java SE 17.0.21.1, 21.0.13.1, 25.0.5.1, or the equivalent patch for the distribution you’re using), followed by restarting the application.
  • Until the update is applied, Java applications such as Jira, Confluence, Jenkins, or Keycloak should not be exposed directly to the internet but should run behind a VPN.
  • If the update is not immediately possible, the provider can start Java with the -XX:-UseBASE64Intrinsics option, which bypasses the vulnerable code; this is a temporary solution, not a replacement for the fix.

This article was generated with AI assistance.

Request a quote

← All news