Blog / Front Line — part 24 of 25

Java4Shell: the OpenJDK Base64 flaw behind Jira, Jenkins and Keycloak

· urgentic · 5 min read

Short read

This post covers Java4Shell (CVE-2026-114938), a flaw in the way modern Java decodes Base64 data. On recent Intel and AMD server processors it can let an attacker run code on applications such as Keycloak, Jira, Confluence and Jenkins without logging in. Oracle shipped fixed builds on 17 November and exploitation attempts have already been seen.

You'll learn who is exposed, how to check, the interim fix if you can't patch today, and what to watch for while you work through it.

Most Java bugs live in one library or one product. Java4Shell lives in Java itself. On 17 November, security firm Calif disclosed CVE-2026-114938, a memory corruption flaw in OpenJDK's Base64 decoder, after details leaked ahead of a fix. Oracle released patched builds in its November Critical Security Patch Update the same day, and CISA and the Canadian Centre for Cyber Security both issued alerts.

Base64 is everywhere. Login headers, JSON Web Tokens, SAML artefacts and file uploads all use it, and many applications decode it before a user has authenticated. That is what makes this one worth acting on quickly.

What the flaw is

Java normally decodes Base64 in ordinary Java code. But on x86-64 processors that support a feature called AVX-512 VBMI, the JVM swaps in a hand-written, hardware-accelerated routine once the decoder gets busy. According to Red Hat's bulletin, specially malformed input sent through that fast path corrupts memory, and an attacker who controls the input can use it to run code in the Java process or crash the service.

Calif says the bug can be used in two ways: to read the application's memory, which may hold keys and tokens, and to execute code on the server. It also says it found the bug with an AI coding agent in about an hour and had a first working exploit two hours later, for under $200 in AI costs, according to Qualys.

Oracle scores it 8.1 under CVSS 3.1 with high attack complexity; Calif rates it 9.2 under CVSS 4.0.

Who is exposed

All of these have to be true, per Red Hat and Tenable:

  • Java version: OpenJDK 17.0.6 or later, including the 21, 25 and 27 lines. Standard Java 8 and 11 don't contain the vulnerable code (Oracle's Java 8 Enterprise Performance Pack is the exception).
  • Processor: x86-64 with AVX-512 VBMI, which covers Intel Xeon Ice Lake, Sapphire Rapids, Emerald Rapids and Granite Rapids, and AMD Zen 4 or newer. On Linux, look for the avx512f, avx512bw, avx512vbmi and bmi2 CPU flags. ARM64 systems are not affected.
  • Application: it decodes attacker-controlled Base64 with the standard Java decoder.

That last condition sounds narrow, but it isn't. Calif reports pre-login code execution against default configurations of Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins and PingFederate, and post-login execution against Apache Kafka, Apache Solr, Elasticsearch, Gerrit and Spinnaker. It also demonstrated code execution on sample apps built with Spring Boot and Apache Struts, and a client-side variant where a Java program is compromised simply by connecting over TLS to a malicious server.

It affects builds from most vendors, not just Oracle: Calif names Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, BellSoft Liberica, SAP SapMachine and Red Hat OpenJDK among them. Note that many of the applications above ship their own bundled Java, so checking the server's system Java isn't enough.

Is it being exploited?

As of 18 November, Tenable reports that GreyNoise has seen exploitation attempts, though no confirmed successful compromise against its sensors, along with scanning from a public tool that checks for vulnerable Java versions. VulnCheck says it has a working code-execution exploit for customers, and Immersive's Kevin Breen says he has built one too. The flaw is not yet in CISA's Known Exploited Vulnerabilities catalog.

There's a useful reality check from Palo Alto Networks: despite the name, this is not another Log4Shell. Each product needs its own exploit chain, specific hardware is required and exploitation is sensitive to timing. That slows mass exploitation. It doesn't protect a specific, high-value target, and an internet-facing identity provider or Jira server is exactly that.

What to do now

  1. Find your Java. Inventory every JVM on x86-64 servers, including Java bundled inside products and container images, and note which hosts have AVX-512 VBMI CPUs. Prioritise anything internet-facing, plus identity, CI/CD and collaboration systems.
  2. Patch. Oracle's and Eclipse Temurin's fixed builds are 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1. Amazon Corretto and Azul Zulu have also released fixes; other distributions use their own version numbers, and Tenable notes that as of 18 November Red Hat and Ubuntu had not yet shipped fixes. Check each vendor's advisory, and each product vendor's guidance for bundled runtimes.
  3. Mitigate where you can't patch yet. Start affected JVMs with -XX:-UseBASE64Intrinsics, which turns off the vulnerable fast path. Red Hat calls this the preferred interim option, and the Keycloak project has recommended it for its server. The alternative, -XX:UseAVX=2, disables AVX-512 entirely, but only use it on x86-64: Java on ARM64 won't start with it.
  4. Restart and verify. A new JDK or startup flag does nothing until the process restarts. Confirm the running version and flags afterwards.

What to watch for while you patch

Patching takes time, especially with bundled runtimes and vendors still releasing fixes. In the meantime, watch the systems you've identified:

  • repeated crashes or restarts of a Java service, since failed exploit attempts can crash the application
  • unusual or malformed Basic authentication headers, tokens or SAML requests in web and proxy logs
  • a Java process spawning shells or unexpected child processes
  • new outbound connections from servers such as Jenkins, Keycloak or Jira
  • unexpected sign-ins or token use after a crash, given the flaw can leak secrets from memory

If a vulnerable, exposed system has been running since the leak, it's worth reviewing these logs from 17 November onwards rather than only from the day you patched.

The bottom line

Java4Shell is a hardware-dependent, harder-to-exploit flaw, but it sits in the platform under some of the most important systems in a business: single sign-on, build pipelines and the tools teams work in every day. Find where Java runs on modern x86-64 servers, patch or apply the startup flag, restart, and keep a close eye on those hosts until the job is done.

  • Java4Shell
  • CVE-2026-114938
  • OpenJDK
  • Java
  • Keycloak
  • Jira
  • Jenkins
  • patch management
  • vulnerability