OpenJDK Base64 flaw yields pre-auth RCE on AVX-512 CPUs
CVE-2026-114938 corrupts memory in the decoder on recent Intel and AMD processors and is exploitable before login in default Jenkins, Jira, Keycloak, and other installs.
A memory-corruption bug in OpenJDK's Base64 decoder can leak memory and lead to remote code execution on x86-64 machines whose processors implement AVX-512 VBMI, and several widely deployed Java applications are exposed before authentication in their default configuration.
The flaw, CVE-2026-114938, affects OpenJDK from 17.0.6 onward, according to an advisory from Calif.io, which branded the issue Java4Shell. Jan Schaumann summarized the disclosure on the oss-security list. Calif.io wrote that after its earlier PHP2Shell report, "we realized many people didn't know what PHP was. So we decided to go after something a little more familiar: Java."
The corruption sits in the decoder path taken when the CPU supports the relevant AVX-512 features. Calif.io says affected processors include Intel Xeon generations from Ice Lake through Granite Rapids, and AMD EPYC and Ryzen chips from Zen 4 onward. A machine is in scope only if all of the AVX-512 and BMI2 feature flags the advisory lists are present.
Calif.io says it confirmed pre-authentication remote code execution, in default configurations, against Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins, and PingFederate. The write-up includes a self-contained proof of concept. The same advisory lists vulnerable builds from Amazon Corretto, Eclipse Temurin, Microsoft, Azul Zulu, BellSoft Liberica, SAP SapMachine, Red Hat, Oracle OpenJDK, Oracle Java SE, and Oracle GraalVM for JDK, plus specific Oracle Java SE update levels.
OpenJDK's advisory dated 17 November 2026 does not include technical detail. Oracle has published JDK release notes covering the update. Schaumann noted he had not yet seen a link to the source fixes. Upgrading to a vendor build that includes the fix is the remediation described so far.