Java4Shell: an out-of-bounds write in OpenJDK's Base64 decoder
On 17 November 2026, Java4Shell was disclosed (CVE-2026-114938). It is an out-of-bounds write in OpenJDK’s Base64 decode function.
It is rated 9.2 out of 10 (CVSS 4.0) and affects vulnerable OpenJDK versions starting from 17.0.6 on x86-64 CPUs that support AVX-512 VBMI.
Security researchers showed that an unauthenticated remote attacker could exploit this flaw to corrupt heap memory and execute malicious code. This was demonstrated on default installs of Jira, Confluence and Jenkins.
An out-of-bounds write happens when a program writes data beyond the memory space reserved for it. This can corrupt other data or cause a crash.
We made a challenge, Out Of Bounds Write.c, which explores the same type of vulnerability. It is a small program that greets you by name. It copies the name you provide into a fixed-size memory buffer, with the greeting message stored immediately beside it.
We made our challenge in C because Java checks memory bounds, but the vulnerable code underneath it does not, just like C.
What happens if your name is longer than the space available?
Think you can fix the security bug? Try it now.
Out Of Bounds Write.c on SecDim Play: Play - SecDim
