Subscribe
0%

Java4Shell (CVE-2026-114938): a Base64 bug in Java 17+ allows remote code execution on AVX-512 servers. What to do

A memory-corruption flaw in OpenJDK's AVX-512 Base64 decoder affects Java 17.0.6 and later, including 21, 25 and 27. Researchers say they got pre-auth code execution on default Jira, Confluence, Jenkins and Keycloak installs. Oracle shipped fixes on November 17, and CISA is urging immediate patching.

Listen to this article0:00 / 8:06

A critical bug in Java's own Base64 decoder, nicknamed Java4Shell and tracked as CVE-2026-114938, can let attackers run code on servers running Java 17.0.6 or later, including the 21, 25 and 27 lines. Oracle shipped fixes on November 17 in its November Critical Security Patch Update, and security firm Calif, which found the flaw, says it achieved unauthenticated remote code execution against default installs of Jira, Confluence, Jenkins, Keycloak, JFrog Artifactory and PingFederate, according to BleepingComputer and Qualys.

Why it matters: Base64 decoding happens everywhere in Java software, from tokens and headers to file uploads, and the bug sits in the runtime rather than in any one app. That means a single JDK update fixes many products at once, but also that vulnerable Java runtimes are hiding inside appliances, containers and vendor bundles you may not think of as "Java." The US Cybersecurity and Infrastructure Security Agency (CISA) urged organisations to patch immediately, People Matters reports, in guidance the Canadian Centre for Cyber Security contributed to.

Update, November 19: exploitation attempts have started

Attackers began probing for Java4Shell within about a day of disclosure, SecurityWeek reports. No one has confirmed a successful break-in yet.

  • GreyNoise saw more than 150 requests shaped like Java4Shell attacks, coming from five IP addresses. None led to an intrusion on its sensors.
  • Previdian counted nine exploitation attempts from six IPs on November 18–19. It can't say whether any target was compromised.
  • watchTowr sees "java4shell-recon" scanning and blind exploit attempts that it describes as not yet "particularly functional."
  • Cloudflare's Cloudforce One saw one IP scan a target with a tool-identifying User-Agent, then return about 17 hours later with the exploit trigger while posing as Chrome. On November 18 it also saw, for the first time, one IP generating both Java4Shell traffic and traffic from ARTEX, an AI-driven security-testing framework the FBI warned about on November 13, Cyber Security News reports. That means blocking on User-Agent strings won't work.

Exploit code: Calif's public proof of concept only triggers the memory corruption. VulnCheck has a full remote-code-execution exploit, but only for paying customers, and Immersive's Kevin Breen says he has built a working exploit too, per SecurityWeek. VulnCheck expects more public proofs of concept that trigger the bug but don't get past ASLR.

Vendor advisories so far (per SecurityWeek):

Vendor Status
Cisco More than a dozen products affected, including Catalyst Center, Secure Network Analytics, Secure Workload, Smart Software Manager On-Prem, Intersight Virtual Appliance and Splunk AppDynamics On-Prem. No fixes or workarounds yet. IOS XE and UCS Central are under investigation
Atlassian Cloud is being handled, so no action is needed. Data Center (Jira, JSM, Confluence, Bitbucket, Bamboo, Crowd): disable AVX-512 until patches arrive
Elastic Elasticsearch 7.17.3 and later is affected. RCE needs read-level credentials, but unauthenticated denial of service is possible. Fixes are planned for self-managed releases
Keycloak Images 26.8.2-1 and -2 bundled a vulnerable JDK. Use 26.8.2-3 (Nov 19)
Jenkins At risk on vulnerable Java 17/21/25 on AVX-512 VBMI CPUs. Update Java and restart
Siemens Three Industrial Edge Management products affected. Take them offline until patched
Red Hat Rated Critical for RHEL 8, 9 and 10 and its OpenJDK 17/21/25 builds. Fixes are being fast-tracked
Amazon, Microsoft, Azul Patched OpenJDK builds released

If you run any of these, follow the vendor's advice. For appliances without a fix (Cisco, Siemens), restrict network access to them now.

What the bug is

Detail What's reported
Component Hardware-accelerated (intrinsic) Base64 decoder in the x86-64 HotSpot JVM
Flaw Memory corruption: a short malformed input makes the AVX-512 assembly write 62 bytes past the end of a buffer before Java rejects it (Qualys)
Affected Java OpenJDK-based builds from 17.0.6 onward, plus 21, 25 and 27; Oracle Java SE 8 Enterprise Performance Pack 8u511b33-perf
Not affected Builds before 17.0.6 (including standard Java 8 and 11), ARM64, and x86-64 CPUs without AVX-512 VBMI
Affected CPUs Intel Xeon from Ice Lake through Granite Rapids; AMD EPYC/Ryzen Zen 4 and newer (Qualys)
Severity 9.2 under CVSS 4.0 (Calif); 8.1 under CVSS 3.1 (Oracle)
Exploited in the wild? Exploitation attempts seen from November 18; no confirmed compromise as of November 19 (see update below)

The vulnerable path is limited to x86-64 processors with the AVX-512 VBMI instruction set, which in practice covers most modern cloud and data-centre servers. Distributions built from OpenJDK are affected too: Oracle Java SE, Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, Red Hat's OpenJDK and others, per BleepingComputer and Qualys.

How bad is it in practice

There is no universal exploit. An attacker needs an app-specific way to get crafted Base64 data into the decoder, which slows mass exploitation, Qualys and BleepingComputer note. But Calif's list of working targets is long. Beyond the six pre-auth targets above, it reports code execution for authenticated users on Apache Kafka brokers, Apache Solr, Elasticsearch, Gerrit and Spinnaker, plus sample apps built on Apache Struts and Spring Boot. Qualys adds that heap memory can be read, potentially exposing keys and tokens. It also says a client-side variant can compromise Java programs that connect over TLS to a malicious server.

Calif published a proof of concept showing the memory corruption but is holding back its product-specific exploits. It also says details leaked before coordinated disclosure, according to Endor Labs. The researchers report finding the bug with AI help in about an hour, using OpenAI's Codex, and building a first working exploit about two hours later for under $200 in AI costs, per BleepingComputer. That is a reminder of how quickly others could rebuild an exploit now that the root cause is public.

Fixed versions

Line Oracle fixed build Amazon Corretto
17 17.0.21.1 17.0.21.1.2
21 21.0.13.1 21.0.13.1.2
25 25.0.5.1 25.0.5.1.2
27 27.0.1.1 27.0.1.1.4
8 Perf Pack 8u513-perf —

Sources: Qualys and Aikido. Other vendors (Temurin, Zulu, Microsoft, Red Hat, Linux distributions) ship on their own schedules and may use different build numbers. VulnCheck lists Oracle's fixed builds as 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3 and 27.0.1.0.3, which differ from the numbers above, so confirm against your vendor's own advisory. As of Aikido's November 18 update, it had no confirmed Temurin fix. Early write-ups from November 17, including watchTowr's FAQ and Endor Labs' post, said no fix or workaround existed yet. Those were published before Oracle's release and the technical details came out.

What to do

  1. Find every JVM, not just the ones you installed. CISA warns that Java may not show up as its own entry in software inventories. Check vendor appliances, container base images and apps that bundle their own runtime.
  2. Check the version and the CPU. Anything on 17.0.6 or later, running on x86-64 with AVX-512 VBMI, is in scope until it's on a fixed build.
  3. Patch internet-facing Java services first: identity providers (Keycloak, PingFederate), Jira, Confluence, Jenkins and Artifactory. Then update to your vendor's fixed build and restart every Java process. Qualys stresses checking the running JVM, not just the installed package.
  4. If you can't patch today, use a temporary workaround (also requires a restart):
    • Preferred: turn off the vulnerable fast decoder. VulnCheck's tested form is -XX:+UnlockDiagnosticVMOptions -XX:-UseBASE64Intrinsics, so include the unlock flag. Base64-heavy workloads may slow down.
    • Alternative: -XX:UseAVX=2, which disables AVX-512 more broadly. It's x86-only, and ARM JVMs won't start with it.
  5. Don't rely on a WAF or reverse proxy. Qualys says that isn't a reliable control. CISA's interim advice is to validate Base64 input at app boundaries, cap input sizes and limit unauthenticated access.
  6. Watch for crashes. Unusual JVM crashes, odd Java process behaviour and unexpected runtime installs are worth investigating, per CISA's guidance.

Vulnerability scanners are already adding checks. Qualys lists QIDs 389494 (OpenJDK), 389610 (Oracle Java SE November CPU) and 389608 (Corretto). Also watch for advisories from vendors whose products bundle their own Java runtime. Until a vendor ships an updated bundle, the JDK update and the workaround flags are the fixes that count.

Sources

  1. BleepingComputer — Critical Java4Shell flaw allows RCE attacks on major Java applications bleepingcomputer.com
  2. Qualys — How to Find, Mitigate, and Patch the Critical Java4Shell Flaw (CVE-2026-114938) Now blog.qualys.com
  3. People Matters — US cybersecurity agency urges immediate patching of critical Oracle Java vulnerability me.peoplemattersglobal.com
  4. Aikido — Java4Shell Java RCE: Fix & Versions (CVE-2026-114938) aikido.dev
  5. Endor Labs — Java4Shell (CVE-2026-114938): Pre-Auth Heap Overflow in OpenJDK endorlabs.com
  6. watchTowr — Java4Shell (Java CVE-2026-114938) FAQ watchtowr.com
  7. SecurityWeek — Java4Shell exploitation attempts begin as vendors rush out advisories securityweek.com
  8. VulnCheck — Java4Shell CVE-2026-114938: Fine, I Guess We'll Do This Again vulncheck.com
  9. Cyber Security News — Hackers exploiting Java4Shell RCE flaw using ARTEX disguise themselves as Chrome cybersecuritynews.com

#Java#OpenJDK#Oracle#Java4Shell#CVE-2026-114938#vulnerability#patch now#Jenkins#Keycloak#Atlassian