AIThis post was created with the assistance of artificial intelligence (AI).

TL;DR

CISA urged organizations on November 17, 2026, to patch CVE-2026-114938, a memory-corruption flaw in an optimized Java Base64 decoder. The documented exposure is limited to certain Java releases running on x86-64 processors with AVX-512 VBMI, when outside data reaches the decoder; CISA’s record listed no exploitation at that time.

The U.S. Cybersecurity and Infrastructure Security Agency urged organizations on November 17, 2026, to patch CVE-2026-114938, a memory-corruption flaw in an optimized Base64 decoder in the Java virtual machine. CISA says specially crafted input could crash the JVM and permit unauthenticated remote code execution. Exposure depends on the Java runtime, processor features and whether a program passes outside data to the decoder.

Before you orderOffer from Amazon

Get the latest gadgets delivered free with Prime

  • Fast, free delivery on millions of items
  • Prime Video, Amazon Music and more included
  • Member-only deals all year
Start your free Prime trial Free trial for eligible customers · Cancel anytime
As an affiliate, we earn on qualifying purchases.

The vulnerability, called Java4Shell by its finders, affects the Base64 decoder in the x86-64 HotSpot JVM. CISA described it as a critical flaw and urged immediate patching. Oracle and the OpenJDK project published advisories on November 17, and Oracle included a fix in its November 2026 security update.

The listed affected Java versions are 17, 21, 25 and 27. Red Hat says the vulnerable code entered OpenJDK in version 17.0.6; it says OpenJDK 8 and 11 do not contain the code. The source material also identifies Oracle GraalVM and a specific Oracle Java 8 build, 8u511b33-perf, as affected. Organizations should check their vendor’s advisory for the exact builds and update available for each product.

A vulnerable runtime alone does not establish exposure. The processor must be x86-64 and support AVX-512 VBMI, and external data must reach the relevant Base64 decoder. Red Hat says ARM64 systems and x86-64 systems without that instruction-set feature are not affected. Oracle describes a possible route through APIs used by a web service; the advisory excludes untrusted Java Web Start applications and applets from that described route.

At a glance
updateWhen: CISA alert issued November 17, 2026; ex…
The developmentCISA issued an urgent alert urging organizations to patch the Java Base64 decoder vulnerability CVE-2026-114938, also called Java4Shell.
Table titled Which Java versions are affected, and the fixed builds. Java 8: not affected in OpenJDK, with one exception, Oracle's 8u511b33-perf build. Java 11: not affected. Java 17: affected from 17.0.6 on, per Red Hat; fixed Ubuntu build 17.0.21.1. Java 21: affected; fixed build 21.0.13.1. Java 25: affected; fixed build 25.0.5.1. Java 27: affected; fixed build 27.0.1.1, Amazon Corretto 27.0.1.1.4. Highlighted: only on certain chips, x86-64 with AVX-512 VBMI; ARM64 systems are not affected. Also affected: Oracle GraalVM
Affected Java lines and fixed builds. Sources: OpenJDK Vulnerability Advisory, November 17, 2026; Oracle Critical Security Patch Update Advisory, November 2026; Red Hat; Ubuntu, November 18, 2026; Amazon Corretto 27 change log. Chart: Thorsten Meyer AI.

Which Java Systems Face Risk

The alert matters most to operators of internet-facing Java services that run an affected build on a compatible processor and process data supplied by users or other external systems. CISA’s warning describes a possible path from specially crafted input to remote code execution without authentication. That makes identifying exposed runtimes and applying the vendor patch a priority for organizations that meet those conditions.

Inventory can be harder than checking the Java installation an administrator knowingly deployed. Java may be bundled with business applications, appliances or container images, and those copies may be maintained by a software vendor rather than by the host’s operating-system package manager. Teams should check product and image advisories, then update or follow the supplier’s remediation instructions. The source material recommends starting with internet-facing systems.

The name Java4Shell echoes Log4Shell, but the name does not establish that the flaws have the same reach or severity. The documented processor and runtime limits narrow the set of potentially exposed systems. Administrators still need to verify those limits against their own deployments rather than assume every Java server is affected or that a system is safe based on its top-level Java version alone.

Products Worth Considering

Logitech MX Mechanical Wireless Illuminated Keyboard, Tactile Quiet, Graphite

Logitech MX Mechanical Wireless Illuminated Keyboard, Tactile Quiet, Graphite

Bose QuietComfort Wireless Noise Cancelling Headphones - Twilight Blue Limited Edition

Bose QuietComfort Wireless Noise Cancelling Headphones – Twilight Blue Limited Edition

As an affiliate, we earn on qualifying purchases.

How Vendors Describe Java4Shell

CISA’s November 17 alert links the vulnerability to Oracle’s advisory and lists actions for organizations. The Canadian Centre for Cyber Security contributed to the alert, according to the source material. The OpenJDK project also published an advisory that day, with its risk matrix listing Java 17, 21, 25 and 27 while leaving Java 8 and 11 unmarked.

Oracle’s November Critical Patch Update covered 655 security patches across its products, including 11 for Java SE, according to the supplied source. CVE-2026-114938 received the highest score among those 11 Java SE entries. Oracle describes its November package as complementing its existing quarterly cumulative updates. The timing of the Java4Shell fix therefore coincides with a broader Oracle security release.

Severity scores differ by publisher. Oracle assigns 8.1 out of 10 and calls exploitation difficult; Red Hat rates the flaw critical at 9.8; and the finders give it 9.2 under CVSS 4.0. The National Vulnerability Database had not assigned a score in the supplied material. These ratings use different assessments and should be reported with their sources, rather than treated as a single agreed measure.

““strongly urges organizations to immediately patch””

— CISA

What Exploitation Records Show

The supplied source says CISA’s CVE record listed “Exploitation: none” on November 17, and that the flaw was absent from CISA’s Known Exploited Vulnerabilities catalogue version dated November 18. Those entries describe the records at those dates; they do not prove that exploitation could not occur or establish the status after those snapshots.

The source material does not provide a confirmed account of attacks in the wild, affected victim counts or evidence that a particular product has been compromised. The researchers said they were holding back product-specific attack chains “until everyone has had a chance to upgrade.” The exact set of downstream products containing affected Java builds is also not enumerated in the supplied material.

Severity assessments vary, and the National Vulnerability Database had not scored the CVE in the source material. The underlying advisories give more technical details, but the available text does not establish how many deployments meet all exposure conditions. Organizations need to check their own runtime versions, processor capabilities and data flows.

Patch, Then Check Bundled Runtimes

Organizations should identify Java runtimes in the affected version range and apply the November vendor update or the vendor’s specified fix. Prioritize internet-facing Java services that run on x86-64 processors with AVX-512 VBMI and accept outside data that may reach the decoder. Confirm remediation against the relevant Oracle, OpenJDK or distribution advisory.

After updating directly managed runtimes, teams should check container images and software that bundles Java. Where an application vendor controls the runtime, administrators should consult that vendor’s security notice and deploy its patched release or follow its stated mitigation. A general-purpose Java update may not change a copy packaged inside another product.

CISA’s alert and the vendor advisories are the current sources identified here for technical scope and fixes. Organizations should follow those advisories for changes, including any revised affected-version lists or newly reported exploitation. The supplied source does not name a further public disclosure date or a later reporting milestone.

Key Questions

What is Java4Shell?

Java4Shell is the researchers’ name for CVE-2026-114938, a memory-corruption vulnerability in an optimized Base64 decoding routine in the x86-64 HotSpot Java virtual machine. CISA says specially crafted input could crash the JVM and permit unauthenticated remote code execution.

Which Java versions are listed as affected?

The supplied advisories list Java 17, 21, 25 and 27, plus Oracle GraalVM and the specific Oracle Java 8 build 8u511b33-perf. Red Hat says OpenJDK 8 and 11 are not affected. Check the relevant vendor advisory for exact product builds.

Does every server running an affected Java version need a patch?

The source describes exposure when an affected runtime runs on an x86-64 processor with AVX-512 VBMI and outside data reaches the decoder. Red Hat says ARM64 and x86-64 systems without that feature are not affected by this flaw. Organizations should still verify their configurations and vendor guidance.

Has Java4Shell been exploited?

CISA’s record listed “Exploitation: none” on November 17, 2026, and the supplied source says the flaw was not in the November 18 KEV catalogue. These are dated records, not a guarantee about later activity.

What should administrators do first?

Check affected Java runtimes on internet-facing services, then install the vendor’s November fix. Also inspect container images and products that bundle Java, since those copies may require a separate update from the software supplier.

Source: Thorsten Meyer AI

You May Also Like

The OAuth Permission Apocalypse.

A critical security flaw in enterprise OAuth permissions, likened to SQL injection, has led to a series of supply chain breaches in 2026, exposing thousands of organizations.

Exploring ByteDance’s Recent Investment In AI Data & Safety Initiatives

ByteDance reportedly established a new internal department focused on AI data governance and safety, signaling increased organizational attention to AI risk management.

The Defender’s Window Is Closing Faster Than Anyone Is Counting

April 2026 saw rapid advances in AI cybersecurity, with defenders improving their tools while offensive capabilities accelerate, raising urgent policy questions.

What Does The OpenAI And Poland’s NASK Partnership Mean For AI Safety?

OpenAI and Poland’s NASK say they will work on AI safety and security, but have not disclosed projects, funding, a timetable or measures of progress.