CVE-2026-114938, nicknamed "Java4Shell", was disclosed on 17 November 2026. It is a memory corruption bug in a Base64 decoding intrinsic that the JVM uses on x86-64 CPUs with AVX-512 VBMI. It affects the Java 17, 21, 25 and 27 lines. Calif, which disclosed it, says ARM64 is not affected. Oracle scores it 8.1 (CVSS 3.1, high attack complexity); Calif scores it 9.2 (CVSS 4.0).

The patch itself is routine. The hard part is knowing where every JVM lives.

Where Java hides

  • Application servers and Spring Boot services you built
  • Reporting tools and vendor appliances that ship their own JRE
  • Container images with a JDK baked into the base layer
  • ERP, HRMS and payment middleware supplied by third parties

Any of these may decode Base64 from tokens, uploads or API payloads.

A practical order of work

  • Inventory each runtime with vendor and exact version (java -version per host and per image).
  • Record CPU architecture for each host: x86-64 or ARM64.
  • Patch internet-facing services first: portals, APIs, login and payment flows.
  • Move to the fixed build. Oracle's fixed versions are 17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1 and 8u513-perf. Corretto, Temurin, Microsoft, Azul, BellSoft and Red Hat publish their own numbers.
  • Restart every Java process. A running JVM keeps the old runtime until it restarts.
  • Rebuild and redeploy images rather than patching running containers.

If you cannot patch today

Calif has suggested JVM options that turn off the affected intrinsic. They are not in the Oracle or OpenJDK advisories, so test them before relying on them. Meanwhile, watch for unexpected JVM crashes on services that handle Base64 input.

Standard Java 8 and 11 are not in the OpenJDK advisory, but Oracle lists the Java SE 8 Enterprise Performance Pack. As of 17 November, Tenable was not aware of exploitation in the wild.

More detail: Java4Shell affected builds, fixes and FAQs

Written by the team at Affix Center, an IT services company in Lower Parel, Mumbai.