On 17 November 2026, security firm Calif disclosed a memory flaw in OpenJDK's Base64 decoder, found with the help of an AI model. It was named Java4Shell and assigned CVE-2026-114938. Oracle patched it the same day. No confirmed exploitation had been reported as of 17 November, and CISA urged organizations to patch immediately.
What happened
Calif found the flaw in the decoder that turns Base64 text back into data, a routine used throughout Java applications. Oracle's November Critical Patch Update scores it 8.1 on CVSS 3.1. Calif scores the same flaw 9.2 on CVSS 4.0. Where the two differ, Oracle's own advisory is the one to follow for your risk rating.
Who is affected
The flaw sits in OpenJDK versions 17.0.6 and later, across the 17, 21, 25 and 27 release lines, in any build that has not yet received the fix. That includes builds from every OpenJDK vendor: Oracle, Microsoft's Build of OpenJDK, Amazon Corretto, Eclipse Temurin, Azul Zulu, Red Hat and others. It only affects x86-64 processors with the AVX-512 VBMI instruction set.
Releases before 17.0.6, including standard Java 8 and 11, are not affected. Neither is ARM64. Calif's write-up names Jira, Confluence, Jenkins and Keycloak among the applications it found reachable without a login, as examples of where the decoder sits exposed.
How to check
Start by listing every Java runtime in your environment, not just the ones that show up in an ordinary software inventory. Java is routinely bundled inside applications, containers and appliances, and those copies will not appear on a standard list. Once you have the full list, compare each running version against the vendor's own advisory for the product it belongs to.
How to fix
The fix is the vendor's patched build. Oracle's fixed builds are 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1. After installing a patched build, restart every Java process it affects: the patch only takes effect on restart, so an unpatched process can keep running even after the files on disk are updated. Confirm the running version afterward, rather than assuming the restart picked it up.
Patch internet-facing sign-in systems and build systems first, since those are the most exposed. For any product that bundles its own Java runtime, follow that product's own advisory rather than patching the Java installation yourself. Oracle's and OpenJDK's advisories are also where to check for any temporary measures they list while a patched build is being rolled out.
Checking what Java is actually running, everywhere it is running, is the step most teams underestimate. That inventory, not the patch itself, is usually where the work is.