Java4Shell CVE-2026-114938 needs an Oracle Java and GraalVM runtime decision now. Oracle’s November 17, 2026 security update identifies affected supported builds across three product families. Inventory the runtime inside each application and container, then obtain the matching vendor fix and redeploy the workload.
The Canadian Cyber Centre says the vulnerable path requires an x86-64 processor with AVX-512 VBMI and data reaching the Java Base64 decoder. Prioritize reachable services on matching hardware; for wider CVE triage, see the vulnerability intelligence platform. Keep other embedded Java runtimes in the inventory until their own distributor confirms applicability.
Which Java4Shell CVE-2026-114938 Builds Does Oracle List?
Oracle’s risk matrix marks the following supported builds as affected. These are affected build identifiers, not a table of fixed releases. Check the full runtime build and distributor before approving a replacement.
| Oracle product | Affected supported builds in Oracle’s matrix |
|---|---|
| Java SE | 8u511b33-perf; 17.0.21.0.3; 21.0.13.0.3; 25.0.5.0.3; 27.0.1.0.3 |
| GraalVM for JDK | 17.0.21.0.3; 21.0.13.0.3 |
| GraalVM Enterprise Edition | 21.3.20.0.3 |
Oracle assigns CVSS 3.1 score 8.1 and high attack complexity to this Compiler flaw. Its record says an unauthenticated network attacker can compromise a vulnerable runtime when data reaches the affected component. The researcher separately rates the issue 9.2 under CVSS 4.0; the Oracle and NVD records provide no CVSS 4.0 score.
Why Does a Java Service Face This Risk?
Calif’s research locates the memory corruption in an optimized Base64 decoding path of OpenJDK HotSpot. On supported processors, mishandling the end of encoded data can write beyond a heap buffer. An exposed application feature can pass external data into that library even when the application itself contains no custom decoder.
Calif reports laboratory remote code execution in several server applications and sample frameworks. Those demonstrations show plausible reachability, but they do not establish exploitation in a customer’s environment. The Canadian Cyber Centre said on November 17 that it was not aware of active exploitation at that time.
Brandefense Blackhole recorded 14 dark-chat posts mentioning this CVE from August 20 through November 18, 2026. The count measures discussion, not distinct incidents or confirmed exploitation. A separate GitHub search found eight public repositories named for this CVE on November 17, 2026; repository count also cannot confirm attacks.
What Should Java Owners Do Today?
- Inventory deployed runtimesRecord vendor, complete build, processor capability, and the workload that starts each Java process.
- Find bundled copiesInspect application images, containers, appliances, and third-party distributions; ask suppliers for a CVE-specific fix statement.
- Prioritize reachable workloadsStart with internet-facing Java services on x86-64 hardware with AVX-512 VBMI.
- Apply and verify the fixInstall the distributor’s supported update, rebuild or redeploy bundled images, and confirm the runtime build after restart.
- Handle delayed fixesRestrict exposure, test any temporary JVM mitigation, and set a dated patch exception.
The Canadian Cyber Centre suggests disabling JVM AVX-512 support with -XX:UseAVX=2 when immediate patching is impossible. Treat that as a temporary, tested workaround because it changes runtime behavior and does not repair the code. Oracle likewise says network restrictions may reduce risk but are not a long-term substitute for security updates.
Use a patch management process to track rollout and exceptions. A vulnerability management workflow helps reconcile host inventory with bundled Java copies. If telemetry suggests compromise, preserve relevant records under the incident response plan.
Frequently Asked Questions
Does Java4Shell require an internet-facing Java server?
No. Calif also describes a laboratory client-side scenario, while Oracle's record allows network access through multiple protocols. Prioritize reachable workloads without excluding other affected runtimes.
Can disabling AVX-512 replace the Java update?
The Canadian Cyber Centre offers disabling JVM AVX-512 support as a temporary mitigation when patching is delayed. Test it and install a supported distributor fix.
