What Happened
Oracle released fixes on November 17, 2026 for CVE-2026-114938, the Java4Shell OpenJDK Base64 vulnerability, a heap-based buffer overflow in the Base64 decoder of OpenJDK that could let an unauthenticated remote attacker execute code. CISA published an alert the same day, Critical Java Vulnerability Requires Immediate Patching, and said it strongly urges organizations to immediately patch the vulnerability. Cisco said Oracle announced the availability of fixes on November 17, 2026 for a vulnerability in OpenJDK that could lead to remote code execution.
Severity ratings moved as vendors updated their advisories. Sophos first published its advisory on November 18, 2026 at severity Informational and by November 20, 2026 carried severity High. Fortinet lists a CVSSv3 score of 8.1 and calls the flaw difficult to exploit. Cisco rates the security impact High, and Palo Alto Networks published portfolio status for its products at severity CRITICAL.
No exploitation in the wild is reported in the sources for this story. That is a window, not a reason to wait. CISA urges organizations to apply patches as soon as they are available, prioritizing internet facing systems.
Timeline
- November 17, 2026: Oracle announced the availability of fixes for a vulnerability in OpenJDK identified by CVE-2026-114938, according to Cisco. CISA published its alert and Google Cloud published bulletin GCP-2026-082.
- November 18, 2026: Sophos first published its advisory at 09:40 GMT. Fortinet published its advisory with a CVSSv3 score of 8.1. Cisco published its advisory with a security impact rating of High. AWS published bulletin 2026-189-AWS and said a fix is available in the November 2026 OpenJDK updates. Ubuntu published notices for OpenJDK 17, 21, 25 and 27.
- November 19, 2026: Fortinet and Sophos both revised their advisories. Palo Alto Networks published portfolio status on the impact of the vulnerability on its products.
- November 20, 2026: Sophos updated its advisory to severity High. Ubuntu published notices for CRaC JDK 17, 21 and 25.
Who Is Affected
Any client environment running an affected Java build is in scope, and the affected code is often invisible. CISA urges organizations to review software inventories for JDKs and Java runtimes, including those bundled with third party applications or included in container images and appliances, and notes that these may not appear as separate entries.
Platform vendors published their own coverage. Google Cloud said workloads running unpatched OpenJDK 17.0.6 or later may be affected, whether self managed in VMs and containers or running on managed services such as Google Kubernetes Engine, Cloud Run, App Engine, Dataproc or Dataflow. AWS said it is working to deploy the fix to affected AWS services. Cisco and Palo Alto Networks published advisories on the impact on their products. Ubuntu published notices covering its OpenJDK and CRaC JDK packages.
Google Cloud said OpenJDK 8, 11 and 17.0.0 through 17.0.5 are not affected, and that Google Cloud hypervisors and hardware isolation boundaries between customer VMs and containers are not affected.
Technical Details
CVE-2026-114938, known as Java4Shell. Fortinet lists the affected products as Oracle Java SE, Oracle GraalVM for JDK and Oracle GraalVM Enterprise Edition, in the component Compiler. CISA describes a critical memory corruption vulnerability in the Base64 decoder of the x86-64 HotSpot Java Virtual Machine, which is part of the Java Development Kit. AWS describes a memory issue in the Base64 decoder intrinsic of OpenJDK 17.0.6 and later on x86-64 processors that support AVX-512 VBMI.
Attack vector, as the sources state it: Fortinet describes a difficult to exploit vulnerability that allows an unauthenticated attacker with network access via multiple protocols to compromise the affected products, and says successful attacks can result in takeover. Fortinet's note adds that it 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. CISA says specially crafted Base64 input could crash the JVM and allow for unauthenticated remote code execution. Ubuntu's notices say a remote attacker could possibly use the issue to cause a denial of service or execute arbitrary code.
Affected versions as the sources list them:
- OpenJDK Java 17.0.6 and later on x86-64 platforms
- 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
- OpenJDK 17, 21, 25 and 27 (Ubuntu)
- CRaC JDK 17, 21 and 25 (Ubuntu)
Why the Java4Shell OpenJDK Base64 Vulnerability Is Hard to See
In general, Java does not sit on a machine as its own line item. It arrives inside an application, a container image or an appliance, which is why CISA urges organizations to look for JDKs and Java runtimes bundled with third party applications or included in container images and appliances rather than trusting a software list. AWS notes the issue applies on x86-64 processors that support AVX-512 VBMI, so hardware matters alongside version when you scope the work.
The consequence for an MSP is the same as with any code execution flaw. In general, unauthenticated code execution on an internet facing service is the first step of a wider attack, and the cleanup lands on whoever holds the client relationship. Hours and trust are what you spend, and verified backups plus a recovery path you have tested are what shorten both.
What MSPs Should Do
CISA urges organizations to identify affected Java installations and to patch, and the steps below follow that guidance and the vendor notes in the sources.
- Identify affected Java installations, including JDKs and Java runtimes bundled with third party applications or included in container images and appliances. They may not show up as separate inventory entries.
- Apply relevant Java and vendor patches as soon as they are available, prioritizing internet facing systems.
- If immediate patching is not feasible, apply the interim flag: set JDK_JAVA_OPTIONS to -XX:+IgnoreUnrecognizedVMOptions -XX:UseAVX=2, then restart or redeploy. Upgrade to patched packages afterwards and remove the flag.
- Where patching is not possible yet, use temporary compensating controls: restrict and validate Base64 input at the application boundary, enforce input size limits and limit unauthenticated access.
- Review Oracle's security advisory for patching guidance and for the affected products and versions.
- Check the platform advisories from Google Cloud, AWS, Cisco, Palo Alto Networks and Ubuntu for the services and products you manage.
- Monitor for indicators of suspicious activity, including rogue runtimes, unexpected JVM crashes and suspicious Java processes.
- Confirm backups of affected systems are complete and that a restore works before you start patching.
How EnterProtect Helps
Patching every Java build across a client base takes time you may not have, and some of it has to wait for vendor releases. EnterProtect backup keeps clean, restorable copies of client systems and data, so a failed upgrade, a bad patch or a compromise does not mean starting from nothing.
EnterProtect recovery gets a client running again when a system has to be rebuilt. EnterProtect vulnerability scanning surfaces exposed software versions across an estate as a standing practice rather than an emergency.
That covers the two things every advisory of this kind exposes: what you can bring back, and what you still have exposed.
Frequently Asked Questions
What Is Java4Shell?
Java4Shell is the name given to CVE-2026-114938, a critical flaw in the Base64 decoder of OpenJDK. CISA describes it as a memory corruption vulnerability in the Base64 decoder of the x86-64 HotSpot JVM, which is part of the Java Development Kit. Specially crafted Base64 input could crash the JVM and allow for unauthenticated remote code execution. Oracle released fixes on November 17, 2026.
Which Java Versions Are Affected by CVE-2026-114938?
OpenJDK Java 17.0.6 and later on x86-64 platforms is the core of it. Vendors also list Oracle Java SE 8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3 and 27.0.1.0.3, Oracle GraalVM for JDK 17.0.21.0.3 and 21.0.13.0.3, and Oracle GraalVM Enterprise Edition 21.3.20.0.3. Ubuntu adds OpenJDK 17, 21, 25 and 27 and CRaC JDK 17, 21 and 25. Google Cloud says OpenJDK 8, 11 and 17.0.0 through 17.0.5 are not affected, while Oracle Java SE 8u511b33-perf still appears in the affected list, so check the exact build you run.
Is CVE-2026-114938 Being Exploited in the Wild?
The sources for this story do not report exploitation in the wild. That does not make patching optional. CISA urges organizations to apply patches as soon as they are available and to prioritize internet facing systems, and an exposed Java service is exactly the kind of target attackers look for.
Can I Mitigate the Flaw Without Patching Right Away?
There is a temporary route. Guidance published for this issue is to set or append the environment variable JDK_JAVA_OPTIONS to -XX:+IgnoreUnrecognizedVMOptions -XX:UseAVX=2, then restart or redeploy. Upgrade to patched packages, JDK releases or container images as they become available, then remove the flag.
How Do I Find Affected Java Installations?
Review your software inventory for JDKs and Java runtimes, including those bundled with third party applications or included in container images and appliances, as CISA urges. They often do not appear as separate entries, so check applications that accept Base64 input and any internet facing service first. If you manage cloud workloads, read your provider's advisory as well.
Sources
- Critical Java Vulnerability Requires Immediate Patching (CISA alerts)
- Advisory: OpenJDK Base64 Vulnerability - Java4Shell (CVE-2026-114938) (Sophos Psirt Feed)
- Java4Shell Vulnerability - CVE-2026-114938 (Fortinet Psirt)
- Vulnerability in Oracle OpenJDK (Java4Shell) Affecting Cisco Products: November 2026 (Cisco Psirt)
- USN-9155-1: OpenJDK 17 vulnerabilities (Ubuntu Security)
- USN-9156-1: OpenJDK 21 vulnerabilities (Ubuntu Security)
- USN-9157-1: OpenJDK 25 vulnerabilities (Ubuntu Security)
- USN-9158-1: OpenJDK 27 vulnerabilities (Ubuntu Security)
- CVE-2026-114938 - OpenJDK Base64 Decoder Intrinsic Out-of-Bounds Write Issue (Aws Bulletins)
- CVE-2026-114938 Portfolio Status: Impact of Java Vulnerability (CVE-2026-114938) on Palo Alto Networks Products (Severity: CRITICAL) (Paloalto Psirt)
- USN-9180-1: CRaC JDK 25 vulnerabilities (Ubuntu Security)
- USN-9178-1: CRaC JDK 17 vulnerabilities (Ubuntu Security)
- USN-9179-1: CRaC JDK 21 vulnerabilities (Ubuntu Security)
- GCP-2026-082 (Google Cloud Security Corrected)