Oracle's November 17 Java security update addresses Java4Shell, a remotely exploitable flaw that can let an attacker take control of an affected application. Administrators need to check full runtime builds, hardware and applications, including Java copies bundled with other software.
Tracked as CVE-2026-114938, the flaw affects the Base64 decoder. A vulnerable application can be attacked without a sign-in when it processes specially crafted data. The Canadian Centre for Cyber Security says successful attacks could also expose information or crash a service. Its November 17 advisory says it is not aware of active exploitation.
In the U.S., UC Berkeley's Information Security Office issued a notice to IT administrators and service owners, urging upgrades as soon as possible.
Which systems need checking

Exposure depends on the Java build, processor and application. Canada's advisory identifies x86-64 processors with AVX-512 Vector Byte Manipulation Instructions, or VBMI. Red Hat's bulletin says its affected OpenJDK environments include 17.0.6 and later, including the 21 and 25 lines, on hardware with that instruction support. An attacker must be able to supply data to the vulnerable decoder.
Oracle's CVE-specific risk-matrix row lists these supported Java SE builds as affected:
| Java line | Affected Oracle build listed |
|---|---|
| 8 performance build | 8u511b33-perf |
| 17 | 17.0.21.0.3 |
| 21 | 21.0.13.0.3 |
| 25 | 25.0.5.0.3 |
| 27 | 27.0.1.0.3 |
That row also includes Oracle GraalVM for JDK 17.0.21.0.3 and 21.0.13.0.3, and GraalVM Enterprise Edition 21.3.20.0.3. Oracle rates the flaw 8.1 under CVSS 3.1, with no privileges or user interaction required and high attack complexity.
Red Hat says its OpenJDK 8 and 11 do not contain the vulnerable code path. That statement covers Red Hat's builds; Oracle separately lists the Java 8 performance build above. Oracle's broader November Java update fixes 11 vulnerabilities, so its overall product list covers more than Java4Shell alone.
What administrators should do now
Canada's cyber agency recommends inventorying Java environments, prioritizing internet-facing services and identifying vulnerable components inside third-party products, appliances and containers. Apply the appropriate fixed release from the supplier of each runtime.
Red Hat says it is expediting fixes. Its bulletin also tells customers to rebuild containers when updated base images become available and keep the underlying OpenJDK packages current in products that use them.
For systems that cannot be patched immediately, Canada's advisory recommends considering isolation from public networks. It also identifies the JVM option -XX:UseAVX=2 as a temporary way to disable AVX-512 support. Berkeley warns that this option can slow other work. These measures need the application's responsible IT team to assess their operational effects.
Keep checking the relevant vendor bulletin for updated packages and affected-build information. Canada's advisory also calls for reviewing application, authentication, web-server and endpoint logs for suspicious activity.










