Calif says Java4Shell achieves unauthenticated remote code execution against Keycloak, Jira and Jenkins in default configs.
The issue is tracked as CVE-2026-114938 and scores 9.2 under CVSS 4.0, according to Calif.
Aikido reports the bug affects Java 17, 21, 25 and 27 releases before patched builds.
Base64 is a text encoding that carries binary data through login tokens, uploads and network messages.
Java promises memory safety where the runtime manages memory and blocks classic corruption bugs.
It breaks that promise here.
An intrinsic is a JIT shortcut that replaces Java code with hand tuned CPU vector instructions for speed.
Calif says the vulnerable AVX-512 path mishandles the final characters and computes a negative output length.
The trigger is 64 A characters plus a single equals sign, which allocates a 50 byte buffer then writes 64 bytes, according to Calif.
That stray padding turns the write mask to all ones so 62 bytes spill past the array into neighboring objects, Calif reports.
Quang Luong found the bug in an hour and built the first exploit in two more for under 200 dollars in tokens, according to Calif.
Ordinary login and file upload paths expose the decoder to remote input, according to Calif.
Researcher samczsun showed a malicious TLS server can also compromise a Java client that connects out, according to Calif.
Calif also reports post-auth execution in Kafka, Solr and Elasticsearch plus Struts and Spring Boot samples.
The fixed overwrite becomes a writer that corrupts a buffer length, then a reader that leaks heap memory like Heartbleed, according to Calif.
A TLAB is a private Eden slice that gives each thread its own cursor, and grooming forces large arrays outside it to order victims, according to Calif.
There is no universal exploit because each app needs different grooming and repair steps, according to Calif.
Patch to fixed builds now and you can also watch for needless native optimizations that widen attack surface.





