Skip to content
securitytabs

LiveUpdated

Java4Shell: critical remote code execution flaw reported in OpenJDK's Base64 decoder

A newly disclosed flaw in the Java runtime that powers many business applications could let an attacker run code on a server by sending specially crafted data. US authorities urge organizations to find their Java installations and patch quickly.

Remote code execution flaw in OpenJDK Base64 decoder
Remote code execution flaw in OpenJDK Base64 decoder

What's new

TimelineWhat should my organization do?

Vulnerabilities

What happened

Security researchers at Calif disclosed a memory-corruption flaw nicknamed Java4Shell, tracked as CVE-2026-114938, on 17 November 2026, according to SentinelOne. It sits in OpenJDK's Base64 decoder, and malformed Base64 input can trigger remote code execution. [1][2]

Datadog Security Labs says the bug corrupts memory in the decoder's AVX-512 code path, and SentinelOne says it enables code execution on AVX-512 CPUs. CISA describes it as affecting the Base64 decoder of the x86-64 HotSpot Java Virtual Machine and says crafted input could crash the JVM and allow unauthenticated remote code execution. [2][1][3]

Severity and scoring

NVD rates the flaw 8.1 on the CVSS 3.1 scale. SentinelOne and Wiz cite a CVSS 4.0 score of 9.2, which they call critical. Rapid7 says details were preliminary at the time of writing, pending confirmation in Oracle or OpenJDK advisories. CISA's Known Exploited Vulnerabilities catalogue does not list the flaw. [1][4][5]

Oracle patches and official guidance

Oracle was due to release fixes for 11 Java SE vulnerabilities on 17 November, all remotely exploitable without authentication, with a top CVSS 3.1 score of 8.1, according to its advance notice. The Hacker News reported that separate reports on the OpenJDK flaw emerged the same day. [6]

CISA strongly urges organizations to patch immediately and to review their software inventory for JDKs and Java runtimes. Canada's Cyber Centre issued an alert the same day. None of the cited sources report attacks using the flaw so far. [3][7]

Timeline

  1. CISA urged organizations to patch the Java flaw immediately. [3]

  2. Oracle was due to release patches for 11 Java SE vulnerabilities. [6]

  3. Researchers at Calif disclosed Java4Shell in OpenJDK. [1]

Explained

The technology and terms in this story. Learn more

Business ActionWhat this means inside your organization, and what to do about it, by company size.

Small business

No dedicated security staff; relies on providers

What to know

Java often runs inside business software that a vendor or IT provider manages. CISA urges immediate patching. [3]

What to do

  1. Ask your IT provider and software vendors whether they use Java and have applied Oracle's November update. [3][6]
  2. Install Java updates on any computers or servers you manage yourself. [3]

Mid-size company

A small IT or security team

What to know

CISA asks organizations to identify affected Java installations through their software inventory. [3]

What to do

  1. Review your software inventory for JDKs and Java runtimes and identify affected installations. [3]
  2. Apply the vendor updates and watch Oracle and OpenJDK advisories for confirmed details. [5][6]

Large enterprise

A security operations team

What to know

Datadog and Wiz publish guidance on which deployments are affected and how to detect and mitigate the flaw; Rapid7 says details remain preliminary. [2][4][5]

What to do

  1. Inventory JDKs and Java runtimes, including those bundled with applications, and prioritise internet-facing services that decode Base64 input. [3][2]
  2. Follow the detection and mitigation steps in the Datadog, Wiz and SentinelOne write-ups while patches roll out. [2][4][1]

Sources

  1. [1]SentinelOne Blog · Nov 17, 22:19 UTC
    Defending Against Java4Shell: Vulnerability in OpenJDK Enables RCE on AVX-512 CPUscontext
  2. [2]Datadog Security Labs · Nov 17, 00:00 UTC
    Java4Shell: Remote Code Execution in OpenJDK (CVE-2026-114938)context
  3. [3]CISA Advisories · Nov 17, 12:00 UTC
    Critical Java Vulnerability Requires Immediate Patchingcontext
  4. [4]Wiz Blog · Nov 17, 22:29 UTC
    CVE-2026-114938 RCE in OpenJDK: Everything You Need to Knowcontext
  5. [5]Rapid7 Blog · Nov 17, 18:26 UTC
    CVE-2026-114938: Reported Critical Pre-authentication Remote Code Execution in Java 17context
  6. [6]The Hacker News · Nov 17, 15:17 UTC
    Oracle to Patch 11 Java Flaws Today as Critical OpenJDK RCE (CVE-2026-114938) Report Emergescontext
  7. [7]Canadian Centre for Cyber Security · Nov 17, 23:30 UTC
    AL26-029 - Critical vulnerability impacting Oracle Java - CVE-2026-114938context