Java4Shell (CVE-2026-114938): Heap Overflow in HotSpot's AVX-512 Base64 Decoder
OpenJDK and Oracle disclosed CVE-2026-114938, nicknamed Java4Shell, on November 17. The bug is in HotSpot's hand-written AVX-512 VBMI Base64 decoding intrinsic. On malformed standard or URL-safe Base64 input with unexpected padding, an integer underflow makes the routine miscalculate a length and write up to 62 bytes past a buffer on the Java heap. The bug triggers only when the JVM runs with UseAVX=3 on an x86-64 CPU that supports AVX-512 VBMI (Intel Ice Lake and later, AMD Zen 4 and later) and C2 has compiled the decode path. ARM64 is not affected. OpenJDK 17.0.6 and later are affected, including 21, 25, 26 and 27, from every vendor. According to Docker's write-up, Java 8 and 11 are not affected. Oracle rates the flaw CVSS 3.1 8.1 (High). The researchers at Calif rate it CVSS 4.0 9.2 (Critical).
Calif reports turning the bug into heap disclosure and remote code execution. They demonstrated pre-authentication RCE against default installs of Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate, and post-authentication RCE against Kafka, Solr, Elasticsearch, Gerrit and Spinnaker. The exploits have not been published. Reports on exploitation in the wild disagree. Docker and OX Security reported no confirmed exploitation as of November 18, while Sophos reports a public proof-of-concept that triggers the crash and scanning activity seen by researchers.
Fixed builds are 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1. Java 26 left support in September and lines 18–20, 22–24 and 26 will get no fix, so applications on those versions must move to a supported LTS or to 27. Corretto, Azul Zulu and SapMachine have shipped fixed builds. As of November 18, Adoptium had published only 27.0.1.1+4 for x86-64 Linux, and its other Temurin lines were still pending. The same OpenJDK update fixes nine other CVEs, two of which are rated 7.4 and affect Java 8 through 27.
If you can't patch right away, start the JVM with -XX:-UseBASE64Intrinsics. Docker recommends this over the other published workaround, -XX:UseAVX=2, because UseAVX does not exist on ARM64 and a JVM started with it there will fail to start. Base64-heavy code may run slower with the intrinsic disabled. If you set the flag through JAVA_TOOL_OPTIONS, it reaches child JVMs too, but it replaces any value already set rather than adding to it. Confirm the flag took effect with jcmd <pid> VM.flags. Applications that bundle their own JDK, such as Elasticsearch, Jira and Jenkins distributions, need a fix from their vendor.
Read more — Docker Blog
JEP 547 Lazy Constants (Fourth Preview) Targeted to JDK 28
On November 20, JEP 547, Lazy Constants (Fourth Preview), moved to Targeted for JDK 28. It had been Proposed to Target, with a review that ended on November 18. The API was previously called Stable Values and then Computed Constants. It lets a field be initialized lazily, at most once, while the JIT still treats it as a constant. That gives static final-style performance without eager initialization or double-checked locking.
This fourth preview makes no API changes from the third. Only the release target moves, and the feature stays behind --enable-preview. JEP 547 joins JEP 543 (Structured Concurrency, final) and JEP 544 (Ahead-of-Time Code Compilation) in JDK 28's targeted set. JDK 28 Early-Access Build 24 is available for testing.
Read more — OpenJDK
Valhalla: What It Took to Land Value Objects as a JDK 28 Preview
Inside Java published David Simms's Devoxx Belgium 2026 talk, Why It Takes 3000 Commits to Bring Valhalla's Value Objects to the JDK, on November 16. The talk covers JEP 401 (Value Objects), which arrives in OpenJDK as a preview feature. Value objects give Java a new type model that needs few changes to existing code: a class declared as a value class has no identity, so the JVM can flatten it and lay it out like a primitive.
Simms explains the JVM benefits of value classes, the decade-long history of Project Valhalla, and the implementation work in the VM. He also outlines the path toward bridging objects and primitives, including future generic specialization such as a List of a primitive type. The talk is useful background for teams that want to try value classes on data-heavy code with the JDK 28 early-access builds.
Read more — Inside Java
Java Roundup: Hibernate ORM 8.0 CR1, TomEE 11 M2 Fixes 38 CVEs, TornadoVM jitLLM 3.0
InfoQ's roundup for the week of November 9 shows the Jakarta EE 12 stack moving toward release candidates:
- Hibernate ORM 8.0.0.CR1 implements Jakarta Persistence 4.0.0-M7 and Jakarta Data 1.1.0-M4. Hibernate Reactive 5.1.0.CR1 and 5.0.0.CR1 are compatible with it.
- GlassFish 9.0.0-M4 ships Jakarta Persistence 4.0.0-M7 on EclipseLink 6.0.0-M1, plus Eclipse JNoSQL 1.2.0-M2 and 2.0.0-M1.
- Apache TomEE 11.0.0-M2 resolves 38 CVEs, adds Jakarta Authorization 3.0, and ships the EclipseLink JPA artifact in TomEE Plume.
- TornadoVM jitLLM 3.0 starts 1.43x faster when built with GraalVM Native Image and runs prefill up to 9.3x faster for GPU-accelerated LLM inference in Java.
Smaller releases include JobRunr 9.0.4, which adds hardened Docker images, and the JReleaser 2.0.0 snapshots, which remove the -a and -d short CLI flags. That removal will break build scripts that use the short forms.
Read more — InfoQ
Links & Sources
- Docker patches Java4Shell and the NGINX HTTP/2 with Docker Hardened Images
- Advisory: OpenJDK Base64 Vulnerability - Java4Shell (CVE-2026-114938)
- Google Cloud Dataflow security bulletins (GCP-2026-082)
- JEP 547: Lazy Constants (Fourth Preview)
- Why It Takes 3000 Commits to Bring Valhalla's Value Objects to the JDK
- Java News Roundup: Lazy Constants, Spring for Apache Pulsar, GlassFish, Hibernate, TomEE, Seed4J