PHP Warns of Critical Security Flaws Affecting All Supported Versions, Fixes Coming November 19 · 5h 10-Year-Old NGINX HTTP/2 Flaw Lets Unauthenticated Attackers Execute Code on Servers · 15h F5 Warns 6 Critical BIG-IP Flaws Can Crash Traffic in Specific Setups, May Allow RCE · 15h CVE-2026-123633 and CVE-2026-123007: Critical NGINX HTTP/2 Vulnerabilities · 16h Critical Apache Roller RCE Flaw Under Active Exploitation, No Authentication Required · 16h Java4Shell Flaw Threatens Global Enterprises, Java Application Ecosystem · 17h How Cloudflare WAF helps protect against Java4Shell (CVE-2026-114938) · 19h Vulnerabilities in LMS software · 21h New Attack Bypasses TPM Lockout to Crack Windows Hello and BitLocker PINs in Days, Not Years · 21h AI Pentesting Checklist for Web Apps: 15 Questions to Ask Before Choosing a Vendor · 21h PHP Warns of Critical Security Flaws Affecting All Supported Versions, Fixes Coming November 19 · 5h 10-Year-Old NGINX HTTP/2 Flaw Lets Unauthenticated Attackers Execute Code on Servers · 15h F5 Warns 6 Critical BIG-IP Flaws Can Crash Traffic in Specific Setups, May Allow RCE · 15h CVE-2026-123633 and CVE-2026-123007: Critical NGINX HTTP/2 Vulnerabilities · 16h Critical Apache Roller RCE Flaw Under Active Exploitation, No Authentication Required · 16h Java4Shell Flaw Threatens Global Enterprises, Java Application Ecosystem · 17h How Cloudflare WAF helps protect against Java4Shell (CVE-2026-114938) · 19h Vulnerabilities in LMS software · 21h New Attack Bypasses TPM Lockout to Crack Windows Hello and BitLocker PINs in Days, Not Years · 21h AI Pentesting Checklist for Web Apps: 15 Questions to Ask Before Choosing a Vendor · 21h
🛡️
ACyber Sentinel Security Assessment Team
← Back to feed
⚡ Intelligence Report

CVE-2026-114938: When the Java Runtime Becomes the Attack Surface

CVE-2026-114938: When the Java Runtime Becomes the Attack Surface


Java has been one of the most trusted foundations of enterprise application development for decades. From identity platforms and application servers to CI/CD pipelines and business-critical applications, Java continues to operate behind services that organisations depend on every day.

That widespread adoption is precisely what makes the newly disclosed Java4Shell vulnerability worth examining.

Reported by security research firm Calif, Java4Shell concerns memory corruption in the OpenJDK Base64 decoder. The vulnerability has been reported as a pre-authentication remote code execution issue, with a CVSS 4.0 score of 9.2.

What makes this particularly interesting is that the reported vulnerability does not originate in an application-specific business function. It sits inside the Java runtime itself.

What is Java4Shell?

Java4Shell is the name given by Calif to CVE-2026-114938.

The reported vulnerability involves an out-of-bounds memory write in the hardware-accelerated Base64 decoding implementation within OpenJDK.

Base64 decoding is an ordinary operation in modern applications. Encoded data can appear in authentication tokens, API requests, SAML messages and other application-level communications.

The security concern is what happens when specially crafted input reaches the vulnerable decoding implementation.

Instead of safely processing the input, the decoder may write beyond its intended memory boundary, potentially corrupting adjacent heap memory.

Calif reports that this can be developed into remote code execution. However, independent researchers have raised questions about whether the demonstrated memory corruption reliably enables arbitrary code execution rather than causing a JVM crash.

That distinction matters. A memory-corruption vulnerability and a reliably exploitable remote code execution vulnerability are not interchangeable claims.

Understanding the technical exposure

The reported issue is associated with the AVX-512 VBMI hardware-accelerated Base64 decoder.

The relevant conditions include:

  • An affected OpenJDK implementation.
  • An x86-64 processor supporting AVX-512 VBMI.
  • Attacker-controlled input reaching the vulnerable Base64 decoding path.

The researcher describes a problem in the decoder’s memory handling when processing specially crafted Base64 input.

The underlying concern is an out-of-bounds write. When a decoder calculates an incorrect output boundary, data can be written beyond the allocated destination buffer.

This creates the possibility of heap corruption.

The important distinction is that the vulnerability is hardware-dependent. Not every Java installation automatically meets the exploitation requirements. ARM64 systems, for example, are not affected by the reported AVX-512-specific implementation.

Which Java distributions are affected?

Calif identifies OpenJDK 17.0.6 and later as affected and lists several distributions built from OpenJDK.

These include Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, BellSoft Liberica, SAP SapMachine, Red Hat OpenJDK, Oracle OpenJDK, Oracle Java SE and Oracle GraalVM for JDK.

The reported hardware requirement and the exact runtime build must both be considered when determining exposure.

Oracle’s November security update also lists affected baseline builds across Java SE 8, 11, 17, 21, 25 and 27. However, that update addresses multiple vulnerabilities; its entire affected-version list should not be interpreted as proof that every listed release is vulnerable to this particular CVE.

Enterprise applications that deserve attention

The implications extend beyond organisations that directly manage Java runtimes.

Several widely deployed enterprise products have been identified in research demonstrations and security advisories as potentially exposed when running affected Java environments.

These include Keycloak, Atlassian Jira, Atlassian Confluence, Jenkins, JFrog Artifactory and PingFederate.

These platforms often sit within critical enterprise workflows. Identity management, software delivery, authentication and collaboration services can become attractive targets if their underlying runtime is vulnerable.

Organisations should not assume that a product is protected simply because its application version is current. The Java runtime bundled with that product must also be examined.

Why should security teams care?

Consider an enterprise environment running multiple Java-based applications.

An organisation may have a well-established vulnerability management programme, regular application security testing and a patch management process. However, Java runtimes may exist in application bundles, containers, middleware installations and vendor-managed appliances outside the primary infrastructure inventory.

This creates an additional challenge.

A vulnerable runtime can remain in production even when the application itself appears fully updated.

If an attacker can reach the vulnerable decoding path, the potential consequences include application process compromise, exposure of sensitive information, service disruption through JVM crashes and potentially remote code execution if the reported exploit conditions are successfully achieved.

Further compromise of connected systems may also be possible, depending on the privileges and network access of the application process.

For security leaders, this is not just another Java patching exercise. It is a reminder that the runtime and its underlying dependencies are part of the enterprise attack surface.

Detection and mitigation

The immediate priority should be identifying Java installations that meet the reported exposure conditions.

Check CPU capabilities on Linux

Calif has published the following command to identify the relevant processor flags:grep -m1 '^flags' /proc/cpuinfo | tr ' ' '\n' | grep -E '^(avx512f|avx512bw|avx512vbmi|bmi2)$'

The presence of all four flags indicates that the processor meets the hardware capability requirements described in the disclosure. It does not, by itself, establish that the installed Java runtime is vulnerable.

Identify Java runtimesjava -version

Do not limit this check to the system-wide Java installation. Examine application-bundled JREs and JDKs, container images, Kubernetes workloads, application servers, CI/CD runners, vendor appliances and packaged enterprise products.

Apply security updates

Oracle published its November 17, 2026 security updates covering multiple Java vulnerabilities.

The relevant replacement builds include Java 8u513, Java 11.0.33.1, Java 17.0.21.1, Java 21.0.13.1, Java 25.0.5.1 and Java 27.0.1.1.

Organisations should validate the applicable vendor advisory before deployment, particularly when using third-party OpenJDK distributions or applications with bundled runtimes.

Temporary mitigation

Calif identifies two JVM options that can be considered as interim workarounds.

The first option disables the hardware-accelerated Base64 implementation:-XX:-UseBASE64Intrinsics

The second option restricts AVX execution to version 2:-XX:UseAVX=2

These are temporary workarounds, not substitutes for vendor security updates. Test their compatibility and performance impact before applying them to production workloads. In particular, the second option can affect other workloads using AVX-512.

What should vulnerability management teams prioritise?

This disclosure deserves a coordinated response across infrastructure, application security and vulnerability management teams.

  • Asset discovery: Identify every Java runtime, including those embedded within third-party applications.
  • Exposure assessment: Correlate runtime versions with processor architecture and AVX-512 VBMI capability.
  • Business criticality: Prioritise internet-facing identity platforms, CI/CD infrastructure and business-critical applications.
  • Remediation: Coordinate patch deployment with application owners and product vendors.
  • Validation: Confirm the actual running JVM version after updates and application restarts.
  • Monitoring: Investigate unexpected JVM crashes, suspicious application requests and anomalous process execution.

The New Zealand National Cyber Security Centre has also issued an alert advising organisations to identify affected Java runtimes, including those embedded in containers and vendor appliances, and update impacted systems.

The bigger picture

Java4Shell raises an important question about how organisations manage the security of software dependencies.

We often concentrate on vulnerabilities in applications, operating systems, databases and network appliances. But the runtime executing the application deserves the same level of scrutiny.

A vulnerability in a widely deployed runtime can create a common exposure across otherwise unrelated enterprise products.

The lesson is straightforward: application security does not end with securing the application code. It extends to the runtime, libraries, dependencies, processor-specific implementations and everything required to execute the application.

The application may be secure. The platform hosting it may be secure. But if the runtime connecting the two is vulnerable, the enterprise still has a problem.

Referenced Vulnerabilities

CVE-2026-114938 CVSS 8.1 HIGH Received
CVE-2026-114938 - Vulnerability in the Oracle Java SE, Oracle GraalV
Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: Compiler). Supported versions that are affected are Oracle Java SE: 8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3, 27.0.1.0.3; Oracle GraalVM for JDK: 17.0.21.0.3 and 21.0.13.0.3; Oracle GraalVM Enterprise Edition: 21.3.20.0.3. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in takeover of Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Note: This vulnerability can only be exploited by supplying data to APIs in the specified Component without using Untrusted Java Web Start applications or Untrusted Java applets, such as through a web service. CVSS 3.1 Base Score 8.1 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H).