HomeTech NewsCybersecurityCISA and Canada Urge Immediate Patches for Java4Shell Flaw

CISA and Canada Urge Immediate Patches for Java4Shell Flaw

CISA and the Canadian Centre for Cyber Security have called for immediate patching of a critical Oracle Java flaw, CVE-2026-114938, known as Java4Shell. The Cyber Centre said it is not aware of active exploitation at this time.

In an alert published on 17 November 2026, CISA described a “critical memory-corruption vulnerability” in “the Base64 decoder of the x86-64 HotSpot Java Virtual Machine (JVM), which is part of the Java Development Kit (JDK).” “Specially crafted Base64 input could crash the JVM and allow for unauthenticated remote code execution.” CISA said the Canadian Centre for Cyber Security contributed to the alert.

The Cyber Centre’s own alert, AL26-029, also dated 17 November, classifies the issue as a heap-based buffer overflow (CWE-122) in the Base64 standard Java library. It said the flaw could be exploited remotely without authentication “by sending specially crafted base64 data to Java processes running on x86-64 processors that contain AVX-512 Vector Byte Manipulation Instructions (VBMI) hardware.” Successful exploitation, it said, could result in memory corruption, disclosure of sensitive information, process crashes or arbitrary code execution. “The Cyber Centre is not aware of active exploitation at this time, but that can change quickly.”

The vendor fix is in Oracle’s Critical Security Patch Update for November 2026, issued as Rev 1 on 17 November. In the Java risk matrix, Oracle lists CVE-2026-114938 against the Compiler component of Oracle Java SE, Oracle GraalVM for JDK and Oracle GraalVM Enterprise Edition, with a CVSS 3.1 base score of 8.1 and high attack complexity. The “supported versions affected” match the Cyber Centre’s table: 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; GraalVM for JDK 17.0.21.0.3 and 21.0.13.0.3; and GraalVM Enterprise Edition 21.3.20.0.3. Oracle’s first Java note on the row says the vulnerability “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.” Customers should take fixed-release numbers from that advisory, not from third-party write-ups.

CISA’s recommended actions are to inventory JDKs and Java runtimes, including those bundled in third-party applications, container images and appliances, and to apply vendor patches as soon as they are available, starting with internet-facing systems. If immediate patching is not feasible, it said, organisations should restrict and validate Base64 input at the application boundary, enforce input-size limits, and limit unauthenticated access, and should watch for unexpected JVM crashes and suspicious Java processes. The Cyber Centre added that, where a fix cannot be applied at once, organisations should consider isolating internet-facing applications and “consider disabling JVM support for AVX-512 by using JVM flag -XX:UseAVX=2 if you cannot patch.”

Datadog Security Labs, in its own research rather than an official advisory, said “reliable remote code execution requires additional exploitation work tailored to the application and Java Virtual Machine (JVM) environment.” It also said that, on affected x86-64 deployments, starting the JVM with -XX:UseAVX=2 “prevented out-of-bounds writes in our tests,” and that the flag should be scoped to x86 systems, because native ARM64 JVMs will not recognise it and will fail to start if it is passed.

The alert sits in a line of recent TSN patch-and-decoder stories, including Oracle’s October Critical Patch Update, CISA’s later listing of a Brotli decoder flaw, and early exploit attempts against an Oracle E-Business Suite flaw after its patch. Unlike that EBS case, there is no official confirmation here that Java4Shell is being used in the wild.

The Cyber Centre has not confirmed any active use of the flaw

CISA’s “critical” wording and Oracle’s 8.1 score are not the same kind of statement. CISA is urging immediate patching of a memory-corruption bug it says can crash the JVM and allow unauthenticated remote code execution. Oracle, in the November CSPU, gives the same CVE a CVSS 3.1 base score of 8.1 with high attack complexity. Both can be true at once. Neither figure is a count of compromised servers, and the Cyber Centre has said plainly that it is not aware of active exploitation, with the rider that this can change quickly.

The hardware condition is part of that picture. The Cyber Centre ties exploitation to x86-64 processors that include AVX-512 VBMI. Datadog Security Labs, in its own tests, reached the same hardware limit and said reliable code execution would take extra, environment-specific work. That is Datadog’s research, not a CISA or Oracle finding, and it is not a reason to delay the patches those agencies have asked for. It is a reason not to treat every Java install, on every processor, as equally exposed. The practical list stays the official one: find bundled as well as stand-alone runtimes, apply the November 2026 CSPU to the affected Oracle and GraalVM builds, and, where a patch has to wait, use the high-level compensating controls CISA and the Cyber Centre have already set out, including the AVX-512 flag, with Datadog’s caution that the flag is an x86 measure.

Sources

Related stories

Oracle October CPU Ships 1,295 Patches, Led by Fusion is the closest recent TSN account of an Oracle patch release, and is the next read.

Follow @tsnmediahub on X for breaking AI news as it happens.

Follow on X

Share this story

Latest stories

More in this category

Latest stories

Explore the TSN Atlas: Every topic we cover, mapped. Click a bubble to dive in.