Cybersecurity Research

Java4Shell: Oracle Patches High-Severity Java Flaw That Could Allow Remote Code Execution

Sophos · 17 Nov 2026
Key Takeaway Find out where Java runs in your business, including inside third-party software, and apply the November 2026 Oracle updates, starting with internet-facing systems.

On 17 November 2026, Oracle released updates for multiple vulnerabilities in Java SE. One of them, CVE-2026-114938, has been nicknamed "Java4Shell" and rated high severity with a CVSS score of 8.1.

The flaw is a memory corruption issue in the Base64 decoder of the x86-64 HotSpot JVM, which is part of the Java Development Kit (JDK). According to Sophos, an attacker who sends specially crafted Base64 input could crash the JVM or, in the worse case, achieve remote code execution without needing to log in.

The U.S. Cybersecurity and Infrastructure Security Agency (CISA) issued an alert on the same day, urging organisations to patch immediately. As of Sophos's publication, no active exploitation has been reported.

Sophos advises organisations to find their vulnerable Java runtimes and apply the November 2026 Oracle Java SE updates. Internet-facing x86-64 services that decode untrusted Base64 input should be handled first, since they are the most exposed.

Where patching cannot happen straight away, Oracle's general workaround for this update is to block the network protocols an attack needs. For this vulnerability Oracle lists the protocol as "Multiple" and warns that blocking may break application functionality, so it is a stopgap rather than a fix.

SophosLabs is still investigating whether existing countermeasures apply and whether additional detections can be built. Activity is being reviewed across customer environments and will be escalated where it is found.

Why it matters

Base64 decoding is routine in web applications, so any internet-facing Java service on x86-64 that accepts outside input may be exposed without anyone having thought of it as risky. Because the flaw needs no authentication, a login screen or access control will not protect an unpatched service. Oracle's network-blocking workaround lists the protocol as "Multiple" and may break applications, so patching is the realistic path, and it forces teams to inventory Java runtimes first.

What to do

  • Identify all Java runtimes in your environment, especially on x86-64 servers.
  • Apply the November 2026 Oracle Java SE updates, starting with internet-facing services.
  • Prioritise services that decode untrusted Base64 input.
  • Test Oracle's protocol-blocking workaround for application breakage before relying on it as a temporary measure.
Java CVE-2026-114938 Oracle Remote Code Execution Patch Management

Summarised by CISO AI from Sophos, written with Claude Sonnet 5.5. We link back to every original so you can read it yourself.