Is your Java app still running on a vulnerable runtime?
On 17 November a flaw in OpenJDK went public. CVE-2026-114938, called Java4Shell by the firm that found it. It is a memory bug in the Base64 decoder built into the JVM itself, in the AVX-512 accelerated decode path reac
On 17 November a flaw in OpenJDK went public. CVE-2026-114938, called Java4Shell by the firm that found it.
It is a memory bug in the Base64 decoder built into the JVM itself, in the AVX-512 accelerated decode path reached through java.util.Base64. That detail is the whole story. It is not a flaw in a library or a framework, so a dependency scan will not flag it. The fix is not a library update. It is a new Java runtime, plus a restart of every JVM.
The firm that found it showed unauthenticated remote code execution against default installs of Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate. Oracle scores it 8.1. CISA put out an alert the same day urging teams to patch at once. No exploitation in the wild had been reported as of 18 November.
For the full root cause breakdown, this is the best write up I have read.
Are you affected?
All three of these have to hold:
- Your runtime is OpenJDK 17.0.6 or later without the fix. The maintained lines 17, 21, 25 and 27 are all affected.
- Your CPU is x86-64 with AVX-512 VBMI support, Intel Ice Lake and later server parts, AMD Zen 4 and later. ARM64 is not affected.
- Attacker controlled data reaches the Base64 decoder.
Standard Java 8 and Java 11 builds do not contain the vulnerable code.
How to check in one minute
Run java -version wherever your app runs. A patched Corretto 21 runtime prints this:
openjdk version "21.0.13.1" 2026-11-17 LTS
OpenJDK Runtime Environment Corretto-21.0.13.1.2 (build 21.0.13.1+2-LTS)
OpenJDK 64-Bit Server VM Corretto-21.0.13.1.2 (build 21.0.13.1+2-LTS, mixed mode, sharing)
Look for 21.0.13.1 or later in the first line. Anything at 21.0.13 exactly, or 21.0.12 and below, is unpatched.
If your vendor has no fixed build yet, there is a stopgap. Start the JVM with this flag to turn off the accelerated Base64 path:
-XX:-UseBASE64Intrinsics
Base64 work falls back to plain Java, slower but correct. Treat it as a stopgap, not a fix. Upgrade to a patched build as soon as your vendor ships one, then remove the flag.
What I built
I checked what most Java starters actually ship. Almost every Docker Java image builds on Temurin. When I built this, Temurin had no fixed build out, so a starter pinned to it would have shipped the vulnerable runtime by default. Corretto had its fixed builds out on disclosure day, so I built on that.
One honest update since then. Adoptium now says its November 2026 Temurin releases fix this too, with fixed binaries publishing and container images to follow. So the Corretto edge here is timing, not something permanent. The point of the starter is not which vendor you pick. It is that the runtime you pin is a patched one, and you can prove it.
The starter is Spring Boot 4.1.2 on Amazon Corretto 21.0.13.1.2. The Dockerfile pins that exact build by tag and digest in both stages, so the build cannot drift to a different image under the same tag. I verified it locally before publishing. Maven build passes, tests pass, the app boots, health returns UP, and a runtime endpoint at GET /api/runtime reports the JVM actually running, so you can prove the deployed service is on the patched build.
One more honest note. A live Railway deploy is still untested, so the Docker image build gets its first real test on your first deploy. The template page says that plainly.
Repo: https://github.com/AdeelAhmedKhan/spring-boot-corretto-patched
Railway template: https://railway.com/deploy/spring-boot-on-patched-corretto-21
Have you checked which JDK your Java services are running on?
Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes β full credit and traffic to the original publisher.