Critical Java Flaw Java4Shell Prompts Oracle Patch

Oracle patched Java4Shell, a critical OpenJDK flaw that can enable unauthenticated remote code execution. Check affected versions and update Java deployments.

Updated November 19, 2026 at 3:04 PM ET

Quick Answer

Oracle has released fixes for the critical Java4Shell vulnerability. CISA says specially crafted Base64 input could crash the Java Virtual Machine and permit unauthenticated remote code execution, so patching internet-facing systems is the immediate priority.

What Happened

BBC News reported that Calif discovered Java4Shell with help from artificial intelligence and named the flaw after finding it in Java memory functions.

The US Cybersecurity and Infrastructure Security Agency describes the flaw as a memory-corruption vulnerability in the Base64 decoder of the x86-64 HotSpot Java Virtual Machine. Its analysis says a malformed Base64 string can make the decoder write beyond an array boundary, corrupting the Java heap and allowing an attacker to crash the server, read secrets from memory or run code.

Are You Affected?

The vulnerability primarily affects unpatched OpenJDK-based runtimes from version 17.0.6 onward, including Java 21, 25 and 27 on x86-64 processors with the AVX-512 VBMI instruction set, according to the Azure Network Security Blog. ARM64 systems and x86-64 processors without AVX-512 VBMI support were not known to be affected.

Exploitation requires attacker-controlled input to reach the vulnerable Base64 decoding function. The Cisco Security Advisory also says the vulnerability affects OpenJDK Java 17.0.6 and later on x86-64 platforms when processing Base64-encoded content.

The OpenJDK Project’s November 17 advisory lists the affected releases as 27.0.1.0.3, 25.0.5.0.3, 21.0.13.0.3, 17.0.21.0.3, 11.0.33, 8u512 and earlier. Business operators should inventory standalone Java installations as well as Java runtimes bundled with third-party applications, container images and appliances, as CISA recommends.

What to Do Now

  1. Identify the Java Development Kits and Java runtimes installed on business systems, including Java components bundled with applications, containers and appliances.
  2. Update affected OpenJDK runtimes to a patched release. The fixed versions include OpenJDK 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1, along with Amazon Corretto 17.0.21.1.2, 21.0.13.1.2, 25.0.5.1.2 and 27.0.1.1.4, according to Chainguard.
  3. Update third-party Java-based applications to versions that include the security fix, and prioritize internet-facing systems.
  4. If immediate patching is not possible, restrict and validate Base64 input at the application boundary, enforce input-size limits and limit unauthenticated access, as CISA advises.
  5. Monitor for rogue runtimes, unexpected Java Virtual Machine crashes and suspicious Java processes.

What We’re Seeing

NewSunSEO’s managed hosting fleet was reported to contain 59 WordPress sites when read on November 19, 2026. Fifty-eight sites ran PHP 8.3, version 8.3.37, while the PHP version on one site was not readable. All 59 sites ran WordPress 7.1.5. These fleet figures describe the WordPress sites managed by NewSunSEO, not Java installations across other businesses.

React Server Components RCE (2025)

The separate React Server Components vulnerability CVE-2025-55182 also permits unauthenticated remote code execution and has a CVSS score of 10.0. It affects versions 19.0, 19.1.0, 19.1.1 and 19.2.0 of the react-server-dom-webpack, react-server-dom-parcel and react-server-dom-turbopack packages.

A transparent computer module receives a red laser beam in a Server rack

React introduced fixes in versions 19.0.1, 19.1.2 and 19.2.1 and recommends upgrading immediately. Applications without server-side React code or support for React Server Components were not affected.

Why a Java Memory Flaw Matters for Websites

Java is used by companies including Apple and Amazon, along with banks, hospitals and governments, BBC News reported. Cyber-security expert Dr Pedram Hayati said the flaw could compromise financial systems and customer or organizational data. Hayati also said almost every bank in Australia uses Java for critical transaction data.

Cracked circuit board suspended in a dark Server room

Computer scientist Professor Toby Walsh told BBC News that Java manages memory to protect systems and described the discovery as serious because the weakness was found in that function. The report quoted Walsh as saying the flaw had been hiding in plain sight for 12 years.

Chainguard’s investigation found that a proposed fix had been public on GitHub for two months before the pull request was automatically closed without merging, leaving the bug in shipped builds. The same report says the flaw was found independently three times within several weeks, including by a Calif researcher on October 30 and by Chainguard on November 13.

What the Evidence Shows

The OpenJDK Project assigned CVE-2026-114938 a CVSS 3.1 score of 8.1 and recommended upgrading as soon as possible. Fortinet’s FortiGuard Labs advisory also records a CVSS 3.1 score of 8.1 and lists the attack type as unauthenticated, while stating that known exploitation had not been recorded at publication.

Chainguard reported the flaw at about 9.2 severity on CVSS 4.0. Its investigation connected the malformed Base64 input to an out-of-bounds write in the Java heap on servers using a common class of x86-64 CPU.

The FortiGuard Labs advisory reported that its investigation of affected Fortinet products was still underway on November 19. Cisco similarly listed several products as affected, some as under investigation, and stated that no workarounds were available in its November 18 advisory.

Key Considerations

  • Affected Java may be embedded inside third-party applications, container images or appliances rather than listed as a separate installation, according to CISA.
  • The vulnerable path requires attacker-controlled input to reach Base64 decoding functionality.
  • Azure Web Application Firewall mitigations can detect and block known HTTP-based exploitation patterns, but Microsoft says they complement rather than replace patching.
  • ARM64 systems and x86-64 processors without AVX-512 VBMI support were not known to be affected.
  • Cisco and Fortinet continued checking their own product lines after the initial disclosures, with affected-product lists still subject to revision.

FAQ

What Is Java4Shell?

Java4Shell is the name Calif gave to CVE-2026-114938, a memory-corruption vulnerability in Java’s Base64 decoder that can cause application crashes, disclose sensitive information or permit remote code execution.

Which Java Versions Are Affected?

The OpenJDK Project lists affected releases as 27.0.1.0.3, 25.0.5.0.3, 21.0.13.0.3, 17.0.21.0.3, 11.0.33, 8u512 and earlier. Microsoft identifies unpatched OpenJDK-based runtimes from 17.0.6 onward on x86-64 processors with AVX-512 VBMI support as the primary risk.

Has Oracle Released a Fix for Java4Shell?

Yes. Oracle released a critical patch update on November 17, 2026, including a fix for CVE-2026-114938. Fixed releases include OpenJDK 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1.

What Should Website Owners Do?

Website owners should inventory Java runtimes, including those bundled with third-party applications, update affected software and prioritize internet-facing systems. Temporary controls include validating Base64 input, limiting input size and restricting unauthenticated access.

How Was Java4Shell Discovered?

BBC News reported that Calif discovered the flaw with help from artificial intelligence, while Chainguard said it found the issue independently on November 13 after scanning an open-source project. The discovery was not yet publicly available through OpenAI’s GPT-6 Cyber model at the time of the BBC report.

NewSunSEO

NewSunSEO does the SEO and AI search work for businesses that would rather hand it to someone. Visit NewSunSEO.

This article reports on publicly available information from the sources listed below. We have no reason to believe it is inaccurate, but we have not independently verified every claim, and details may change as the story develops.

Sources


See our editorial disclaimer for how our articles are produced.

🤖
Is your business visible to AI assistants?

Run a free scan to see your AI Visibility Score, SEO rating, and local citation accuracy.

Check Your Score →