Java4Shell (CVE-2026-114938): Leaked Java RCE in OpenJDK's Base64 Decoder Is Still RESERVED, With No Official Advisory

Critical · 2026-11-17 · By H.A

Java4Shell (CVE-2026-114938): Leaked Java RCE in OpenJDK's Base64 Decoder Is Still RESERVED, With No Official Advisory

Details of an unauthenticated remote code execution flaw in OpenJDK 17.0.6+ have leaked before disclosure: the CVE is only reserved, NVD has no record and Oracle has named no fix yet.

Overview

A critical Java flaw has gone public before its owners were ready to talk about it. CVE-2026-114938, nicknamed "Java4Shell", is being described as an unauthenticated remote code execution bug in the Java runtime (OpenJDK and Oracle Java SE builds based on it). It is not yet officially disclosed. The researchers who say they found the bug and reported it to Oracle confirmed that the vulnerability had leaked, and promised to publish their technical write-up only after Oracle ships a patch.

At the time of writing, 21:50 Mauritius time (17:50 UTC) on 17 November 2026:

Everything below about how the bug works comes from the leaked and researcher-reported details. It has not been confirmed by Oracle or OpenJDK and may change once the official advisory is out.

The Vulnerability

According to the reported details, the flaw sits in the hardware-accelerated Base64 decoder inside the HotSpot JVM. On x86-64 CPUs with AVX-512, the JVM replaces the normal Java code behind java.util.Base64 decoding with a fast hand-written machine-code routine (an "intrinsic").

Why this matters: Base64 decoding is everywhere in server-side Java. It is used for HTTP Basic authentication headers, JSON Web Tokens, SAML assertions, API payloads, file uploads and message queues. Any service that decodes Base64 from an untrusted user on an affected JVM and CPU could be reachable without logging in.

Affected Versions

Reported (not confirmed by the vendor):

Officially listed by Oracle as affected by some of the 11 Java SE fixes in the November 2026 update (not mapped to individual CVEs):

Timeline

Tradecraft

There are no public reports of attacks yet. Based on the reported mechanics, attackers would most likely:

Failed attempts are likely to crash the JVM, which helps defenders.

IOCs

No indicators of compromise have been published. There are no public exploit samples, payload hashes or attacker infrastructure for this CVE yet.

Detection

Recommended Actions

Analyst Assessment

Java4Shell is a classic leaked-before-disclosure situation. The name, the CVE number and enough detail to start hunting are already public, while the official records are still empty. That gap is the risk: skilled attackers can work from a 65-byte trigger and a known code location, while defenders cannot yet point to a vendor advisory or a fixed version number.

Until Oracle and OpenJDK publish, treat the technical details and the 9.2 score as credible but unconfirmed. What you can do now is make the inventory, check AVX-512 exposure, stage the patch and prepare the JVM option as a fallback. When the advisory lands, the job is simply to roll out the update.

Reef Sentinel will update this item when the CVE record, the NVD entry or the vendor advisories are published. Severity: Critical (reported, pending official scoring).

Sources

REEF SENTINEL