No GraalVM Community release has the Java4Shell fix yet. Run as a JVM, it's exposed through both of its compilers. As Native Image, the build target decides, not the JDK on the host.
If you run GraalVM Community, patching Java didn't fix Java4Shell for you: no GraalVM Community release contains the fix today. The newest, 25.5.5.0.3 (released 3 November), is built on JDK 25.0.5.0.3, before the patch, and carries a second, unpatched copy of the vulnerable decoder inside the Graal compiler.
Java4Shell (CVE-2026-114938) is a heap write past the end of an array in the AVX-512 VBMI Base64 decoder that HotSpot uses for java.util.Base64, disclosed on 17 November. GraalVM ported that decoder into its own compiler in March 2026, bug included, and shipped it in every release from 25.1 on.
The public guidance so far says the GraalVM problem is Native Image binaries built with 25.1 or later, and that GraalVM running as a normal JVM is covered by Oracle's November update. We tested both on real hardware. The JVM case is worse than that, and the Native Image case is narrower.
-XX:-UseBASE64Intrinsics. No Community release is patched, and on an AVX-512 VBMI CPU both of its compilers reach the bug. The flag stopped Graal's path in our tests, and it is the standard workaround for C2's. It is case-sensitive: -XX:-UseBase64Intrinsics is an unknown option and the JVM won't start.-march=native on such a machine) carry the bug. Binaries built with the default target don't include the vulnerable code path. JVM flags don't exist in a Native Image binary, so only a rebuild changes it.-march=native leaves the vulnerable path out. Then rebuild again on 25.6.The full conditions, fixed builds by distribution and check commands for every JVM are on our Java4Shell page. This post is about GraalVM.
Java4Shell lives in the tail of a hand-written decoder. After decoding 64-byte blocks, 1 to 3 bytes can be left over. The decoder computes the output size for them as zero, takes one off for each trailing =, and ends up with a negative number. The instruction that builds the write mask reads only the low byte of that number, so the mask comes out all ones and the decoder writes a full 64 bytes past the end of the output. Java throws an exception afterwards, but the write has already happened. OpenJDK's fix adds four lines that send short tails to the plain code path.
GraalVM has its own copy. In March 2026 GraalVM's compiler ported HotSpot's Base64 fast paths as AMD64Base64DecodeOp (oracle/graal ec076abb, GR-65455), including this tail logic. Graal uses that op in two places:
GraalVM's fix for its copy is dated 14 September (13a4853144b8, "Avoid AVX-512 Base64 tail overwrite"), was merged on 11 November (oracle/graal pull request 15006), and has shipped in no release. Every release from 25.1.3 to 25.5.5.0.3 has the unguarded tail; 25.0 releases don't have the port at all.
We ran each build on two AWS machines: an m7i.large (Intel Xeon 8488C, Sapphire Rapids, with AVX-512 VBMI) and an m5.large (Intel Xeon 8175M, Skylake, with AVX-512 but no VBMI). Each test decodes crafted Base64 into an array larger than the output, pre-filled with marker bytes; a changed marker past the decoded length is a write the decoder must never make. No exploit was run.
| Build, on the VBMI machine | Out-of-range write |
|---|---|
| GraalVM Community 25.5.5.0.3, Graal as the JIT | 62 bytes past a 50-byte output, from a 65-byte input |
| The same, with HotSpot's C2 as the JIT | The same: its JDK 25.0.5.0.3 predates OpenJDK's fix |
The same, Graal as the JIT with -XX:-UseBASE64Intrinsics |
None |
Native Image binary, built with -march=native |
62 bytes past the output from a 65-byte input, basic and URL decoders |
Native Image binary, default target (x86-64-v3) |
None of this kind: the AVX-512 path isn't compiled in |
Three things follow.
avx512vbmi.-XX:-UseBASE64Intrinsics, -XX:UseAVX=2 and C1-only (-XX:TieredStopAtLevel=1) each stopped the write on Java 17 and 21. We prefer the first: -XX:UseAVX=2 turns off AVX-512 for all compiled code, not just Base64.ec076abb).13a4853144b8), not labelled as a security fix.| What you run (x86-64 with AVX-512 VBMI) | Status as of 20 November 2026 |
|---|---|
| GraalVM Community 25.1 to 25.5 as a JVM | Exposed through Graal and through C2. Use -XX:-UseBASE64Intrinsics |
| GraalVM Community 25.0.x as a JVM | No Graal copy, but its JDK (25.0.2 and earlier) predates OpenJDK's fix: with C2 it reaches HotSpot's unpatched decoder. With Graal, its default JIT, not established. Use the flag |
Native Image binary built with 25.1 to 25.5 for a VBMI target (such as -march=native on a VBMI machine) |
Exposed, on any host with VBMI, whatever JDK is installed. Rebuild |
| Native Image binary built with 25.1 to 25.5, default target | No Java4Shell write in our test: the AVX-512 path isn't in the binary |
| Native Image binary built with 25.0 or earlier | No Graal copy of the decoder |
| Mandrel or Quarkus native executables | Quarkus and Red Hat say not affected. That holds for builds made with GraalVM before 25.1; we didn't check Mandrel's own releases |
| Oracle GraalVM for JDK 17.0.21.1 | Not confirmed fixed: Oracle's notes say it is built on 17.0.20.1+4, which may be a typo for the patched 17.0.21.1+4 |
Check your own:
# 1. Does the CPU have what the bug needs? (all four must appear)
grep -o -w -E 'avx512f|avx512bw|avx512vbmi|bmi2' /proc/cpuinfo | sort -u
# 2. Which GraalVM is this, and is the flag on? (JVM mode; replace PID)
java -version
jcmd PID VM.flags -all | grep -E ' (UseAVX|UseBASE64Intrinsics) '
# 3. Native Image: which GraalVM built it, and for which target?
native-image --version
grep -rn -- '-march' pom.xml build.gradle* src/main/resources/application.properties 2>/dev/null
For Native Image, step 3 runs where the binary is built: the GraalVM version and any -march option in your build configuration or CI, including the Maven and Gradle native plugins and Quarkus's quarkus.native.additional-build-args. A binary has no JVM flags to read at runtime.
-XX:-UseBASE64Intrinsics works for GraalVM as a JVM, not for Native Image.These reduce risk while you wait for a fixed release; only the fixed release removes the bug.
hs_err_pid*.log) or Native Image process crashes that follow requests carrying long Base64 values, such as Authorization: Basic headers or tokens ending in =.Calif (Quang Luong) for finding and disclosing Java4Shell, and Albert Yang, credited by Oracle; the OpenJDK Vulnerability Group and Oracle for the fix; the GraalVM team for fixing its copy; Precursor Security for reporting GraalVM's statement.