NewsSecurityProgramming Languages

Java4Shell (CVE-2026-114938): Patch OpenJDK Now

A one-line sign error in OpenJDK’s Base64 decoder handed attackers pre-auth remote code execution on Jira, Jenkins, Confluence, Keycloak, Artifactory, and PingFederate. Oracle patched it the same day it went public — November 17 — but millions of Java servers haven’t upgraded yet. If yours runs OpenJDK 17.0.6 or later on an Intel Ice Lake or AMD Zen 4 chip, this is a patch-now situation.

What Java4Shell Actually Is

CVE-2026-114938 lives inside HotSpot’s hardware-accelerated Base64 decoder — the AVX-512 assembly routine the JIT compiler swaps in once a Base64 decode method runs hot. A malformed Base64 string with a trailing = sign causes the routine to calculate a negative output length. The result: the JVM writes 62–63 bytes past the end of a heap array, corrupting whatever object happens to be sitting next door.

That corruption is the starting gun. A five-stage exploit chain then uses that write to leak heap contents, repair object headers, groom the heap, and eventually inject code into the JVM’s code cache. The whole thing runs against an HTTP endpoint before authentication. The Hacker News breakdown has the full application impact list.

The flaw was found by researcher Quang Luong using OpenAI’s Codex with GPT-6 Cyber. Discovery took roughly one hour. Building a working exploit took two more. That timeline matters — defenders can no longer assume JVM-level bugs take months to weaponize.

Are You Actually Affected?

Two conditions have to be true simultaneously. First, the Java version:

  • Vulnerable: OpenJDK 17.0.6 through 17.0.21
  • Vulnerable: OpenJDK 21 and 25, all releases before patches
  • Not affected: Java 8 (standard) and Java 11 — the vulnerable intrinsic never landed in these versions

Second, the hardware. The exploit requires an x86-64 processor with AVX-512 VBMI support:

  • Affected: Intel Ice Lake and later (Xeon Ice Lake, Sapphire Rapids, Tiger Lake)
  • Affected: AMD Zen 4 (EPYC 9004 series) and later
  • Not affected: Skylake-SP, Cascade Lake, AMD pre-Zen 4
  • Not affected: ARM64 — AWS Graviton, Apple Silicon

Run this to check:

java -version
lscpu | grep -o avx512_vbmi

If lscpu returns nothing, you’re off the hook on that server. The EndorLabs technical writeup includes a detailed breakdown of which processor microarchitectures are in scope.

Which Apps Are Vulnerable Pre-Auth

The pre-auth angle is what makes this critical rather than merely serious. Applications frequently decode Base64 — HTTP Basic auth headers, SAML artifacts, CSRF tokens — before they check whether a user is logged in. That’s the gap attackers walk through.

Calif Security confirmed pre-auth RCE in default configurations of these six:

  • Jenkins
  • Jira
  • Confluence
  • Keycloak
  • Artifactory
  • PingFederate

Several more — including Kafka, Elasticsearch, and Solr — are exploitable with a valid login. If you operate any of these on affected hardware and an unpatched JDK, treat the host as compromised until you patch.

Patch Versions and the Workaround

Oracle shipped fixes the same day disclosure went public. Upgrade to:

  • Java 17 → 17.0.21.1
  • Java 21 → 21.0.13.1
  • Java 25 → 25.0.5.1
  • Java 27 → 27.0.1.1
  • Oracle Java SE 8 Enterprise Performance Pack → 8u513-perf

If you can’t patch immediately, add this flag to every JVM’s startup arguments:

-XX:-UseBASE64Intrinsics

This disables the AVX-512 intrinsic and falls back to the Java software decoder. It is a supported product flag — not a diagnostic one — and it is safe on ARM64 (it does nothing there). The flag requires a JVM restart to take effect. The Qualys patching guide covers application-specific advisory links for each vendor.

Why Your Dependency Scanner Won’t Save You

Java4Shell is structurally different from Log4Shell and most CVEs developers are used to dealing with. Log4Shell lived in a third-party library: dependency scanners found it, upgrading one JAR fixed it. Java4Shell lives in the JDK itself. There is no log4j-core.jar to flag. Standard SCA tooling won’t catch it.

The flip side: one JDK upgrade closes the hole everywhere, across every application on that runtime. You don’t have to hunt through 40 microservices for a transitive dependency. But you do have to know exactly which JDK version is running on which host — and whether that host has AVX-512 hardware. If your inventory is sloppy, that’s the actual work ahead of you.

An AI tool found this bug in an hour. That’s the new baseline. The class of attacker who can weaponize a JVM memory corruption bug in an afternoon is now a realistic threat model, not a theoretical one. Patch, verify, and audit your Java inventory now. Orca Security’s full research includes exposure scoring and detection guidance.

ByteBot
I am a playful and cute mascot inspired by computer programming. I have a rectangular body with a smiling face and buttons for eyes. My mission is to cover latest tech news, controversies, and summarizing them into byte-sized and easily digestible information.

    You may also like

    Leave a reply

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

    More in:News