News

A Flaw in Java's Base64 Decoder Writes Past the Buffer, and CISA Wants It Patched Now

CISA urged immediate patching of CVE-2026-114938 on November 17. The flaw corrupts the Java heap when a malformed Base64 value reaches the accelerated decoder.

CISA told organizations on November 17 to patch a memory corruption flaw in Oracle Java before an attacker reaches the Base64 decoder first. The bug, CVE-2026-114938 and nicknamed Java4Shell, sits in the standard library that ships with every JDK rather than in a single application.

On x86-64 processors with AVX-512 VBMI support, HotSpot swaps in a hardware accelerated Base64 decoder. When an input ends in a short padded tail of fewer than four bytes, the routine works out a negative output length, turns it into a store mask and lets 64 bytes land past the end of the destination array. Java then rejects the input. The heap is already corrupted. The OpenJDK fix sends control back to Java before the masked store whenever fewer than four bytes remain.

The input arrives before the login

Base64 is how HTTP Basic credentials, SAML assertions, CSRF tokens and MIME encoded words travel, and applications decode them before authentication finishes. Red Hat rates the flaw critical and says pre-authentication remote code execution has been demonstrated against widely deployed Java applications running default configurations. Earlier reporting put Keycloak, Atlassian Jira and Confluence, JFrog Artifactory, Jenkins and PingFederate in reach without an account, and Kafka, Solr, Elasticsearch, Gerrit and Spinnaker in reach with one.

Blackpoint Cyber reproduced it on an Intel Xeon system: about 28,000 unauthenticated requests carrying a malformed Base64 value ended a local Spring Boot JVM after roughly 20 seconds, and testing showed corruption of nearby Java objects without an immediate crash.

Oracle lists Java SE 8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3 and 27.0.1.0.3, plus GraalVM for JDK 17.0.21.0.3 and 21.0.13.0.3 and GraalVM Enterprise Edition 21.3.20.0.3. Its advisory scores the flaw 8.1, with high attack complexity, no privileges and no user interaction.

Turn the optimisation off until the runtime is replaced

The accelerated path is selected from the processor and the state of the just in time compiler, so an affected build does not take it in every environment. ARM64 systems and x86-64 chips without AVX-512 VBMI never reach that code. Red Hat recommends starting affected JVMs with -XX:-UseBASE64Intrinsics, which removes the vulnerable decoder and leaves other AVX-512 code in place. The broader -XX:UseAVX=2 works only on x86-64, because ARM64 JVMs refuse to start with it.

Finding the exposed runtimes is the harder half. A JDK bundled in a container image or an appliance often has no line of its own in a software inventory, which is the gap patch management software for smaller teams is meant to close.

Neither Oracle nor CISA has reported an attack using the flaw. Patches from Oracle and OpenJDK are available.

Some offers on this page may be paid placements or contain affiliate links.

Cyberpresso: daily cyber & AI brief

Free daily newsletter, read in 5 minutes.

Subscribe free