Back to blog

Seguir y suscribirse

Fastly’s Virtual Patch for Java4Shell (CVE-2026-114938)

Learn about Fastly’s virtual patch for the critical Java4Shell vulnerability (CVE-2026-114938).

Simran Khalsa
Simran KhalsaInvestigador de seguridad de personal
Equipo de investigación de seguridad de Fastly
Equipo de investigación de seguridad de FastlyEquipo de investigación de seguridad de Fastly, Fastly

This week, a critical RCE vulnerability was disclosed in OpenJDK, an open-source implementation of Java. The following provides all the details you need to ensure you’re covered and information about Fastly’s virtual patch that helps protect Next-Gen WAF customers from Java4Shell.  

What is Java4Shell, CVE-2026-114938? 

  • Java4Shell (assigned CVE-2026-114938) is a critical remote code execution (RCE) vulnerability discovered in OpenJDK - an open-source implementation of Java. 

  • Left unpatched, this vulnerability may allow for attackers to deploy remote code execution attacks on applications like Confluence, Atlassian Jira, Jenkins, and more.

Java4Shell Details

The following provides key details about Java4Shell: 

  • Java4Shell is the informal name for CVE-2026-114938, a critical OpenJDK remote code execution flaw disclosed on November 17, 2026.

  • It is a critical vulnerability, given a preliminary CVSS v4.0 score of 9.2, and OpenJDK scores it 8.1 under CVSS 3.1.

  • The flaw affects Java versions 17 (from 17.0.6), 21, 25 and 27.

  • It is a memory-corruption bug in the x86-64 intrinsic implementation of OpenJDK’s Base64 decoder. A stray padding character causes an out-of-bounds heap write. Only x86_64 CPUs with AVX-512 VBMI are affected. ARM64, Java 8 (apart from Oracle’s 8u511b33-perf build) and Java 11 are not affected.

  • Oracle’s fixed builds are 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1, other distributions ship their own fixed builds. Vendor coverage is uneven, so those with Java4Shell in their ecosystem should work to ensure a patch. 

  • As of November 19, there was no public RCE exploit and no confirmed exploitation in the wild. A trigger for the bug is public.

What Fastly is Doing to Help Customers Protect Against Java4Shell

Fastly has created a virtual patch for Java4Shell, CVE-2026-114938 that is available to Next-Gen WAF customers. Fastly’s virtual patch helps protect customers from Java4Shell while underlying systems are patched. It detects the known trigger in the Authorization and Cookie request headers and may not cover every attack path, so patching is still required. Customers should check their account settings:

  • The virtual patch is already active for organizations utilizing the Automatic CVE Virtual Patching feature.

  • For customers without this setting turned on, the fix is as simple as enabling the patch within the Fastly dashboard. You can find full instructions here.

What are the Potential Impacts of Java4Shell if Left Unpatched?

  • Remote code execution without credentials: An attacker may be able to run code inside a vulnerable Java application without logging in, which puts internet-facing services most at risk.

  • Exposure of sensitive data: Before any code execution, the bug can be used to read heap memory, which may contain credentials, tokens and customer data.

  • Service disruption: A failed or deliberate attempt can crash the JVM and take the application down.

  • Widely deployed products affected: Researchers report successful attacks against Jira, Confluence, Jenkins, Keycloak, Artifactory and PingFederate in their default configurations.

How to Secure Against Java4Shell with Help from Fastly

As always, Fastly is here to support customers and non-customers alike, in securing against vulnerabilities like CVE-2026-114938 and beyond. Our teams are here for you as you navigate ongoing mitigation - whether you’re a longstanding Fastly platform customer or in need of immediate protection. Visit our documentation page on Virtual patches for CVEs for more information. And reach out anytime if you need additional help.

Sources: 

  1. RHSB-2026-018 Remote Code Execution via memory corruption on x86-64 systems - OpenJDK (CVE-2026-114938) - "java4shell"

  2. OpenJDK Base64 Decoder – Critical Memory Corruption Vulnerability (CVE-2026-114938)

¿Estás listo para empezar?

Ponte en contacto con nosotros hoy