Java4Shell: critical code execution in enterprise Java apps

18.11.2026, Wednesday

Disclosed on 17 November, CVE-2026-114938 allows code execution through a memory bug in Java's Base64 decoder. Jira, Confluence, Jenkins and Keycloak are affected in default configurations.

A vulnerability disclosed on 17 November 2026 and nicknamed Java4Shell affects a widely used component of the Java runtime. Calif, the research team that found CVE-2026-114938, rated it critical at 9.2 on the CVSS 4.0 scale; Oracle rated it 8.1 (High) under CVSS 3.1. Oracle shipped the fix the same day in its November 2026 Critical Patch Update.

Where the flaw sits and what it does

The bug is a memory-corruption flaw in Java's hardware-accelerated Base64 decoder. When a specially crafted Base64 string is processed, two outcomes are possible: reading data held in application memory, such as keys and session tokens, or executing attacker-supplied code on the server.

The affected base is OpenJDK 17.0.6 and later, which brings the distributions built from that code into scope: Oracle Java SE, Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu and Red Hat OpenJDK. The OpenJDK Vulnerability Group lists the Java 17, 21, 25 and 27 release lines as affected.

One important limit applies: the flaw only reaches the accelerated decoder on x86-64 processors with AVX-512 VBMI support. ARM64 systems are not affected.

Which applications are exposed

According to Calif's report, applications exposed to unauthenticated code execution in their default configuration include Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins and PingFederate. In authenticated scenarios, Apache Kafka, Apache Solr, Elasticsearch, Gerrit and Spinnaker are affected.

As reported by BleepingComputer, there were no reports of exploitation in real attacks at the time of writing, and the flaw is not in CISA's catalogue of actively exploited vulnerabilities. Proof-of-concept code has been published, though. Researchers note there is no universal exploit and that an attacker has to find a separate delivery path for each application, which buys time rather than providing assurance.

What this means for Turkish SMEs

"We don't use Java" is rarely accurate in practice. Java runs quietly behind ERP and accounting software, document management systems, e-invoice integrator applications, warehouse and logistics tools, and in-house development infrastructure. Because none of these look like a separate product, they seldom appear on an inventory.

The real risk here is that nobody owns the patch. Where the application came from a vendor, the authority and the responsibility for updating its bundled Java version usually sit with that vendor. If nobody asks, no update arrives.

What Kamer Bilişim recommends

  • Find out where Java is actually running. List which applications on your servers use Java and which JDK version each one carries. On Windows servers, the java -version command plus the installed programs list is enough to start. You cannot patch a component you cannot see.
  • Put the question to your vendors in writing. Ask the supplier of your ERP, e-invoicing, warehouse or document management software for their release timeline for CVE-2026-114938. On systems where you cannot apply the patch yourself, this is the only real leverage you have.
  • Apply the interim mitigation until the patch lands. For systems that cannot be updated immediately, researchers suggest running Java with the -XX:-UseBASE64Intrinsics flag as a temporary mitigation. It is a stopgap that buys time rather than a fix, so test it before applying it in production. Also make sure the management interfaces of these applications are not exposed directly to the internet.

If you would like help inventorying the Java components on your servers, tracking vendor releases or applying the patches in a planned way, you can reach us through our contact page. We provide on-site support across the Anatolian side of Istanbul and remote support elsewhere.

Source: BleepingComputer, Tenable Research, Oracle November 2026 Critical Patch Update

Source: BleepingComputer

Message us on WhatsApp