IT teams can use this Java4Shell bundled JVMs checklist to find every runtime that executes, including copies inside products and containers, and confirm the running process picked up the fix. CISA’s 17 November alert urges immediate patching of CVE-2026-114938, a memory-corruption flaw in OpenJDK’s hardware-accelerated Base64 decoder. Calif has shown pre-authentication code execution on default installs of Keycloak, self-managed Jira and Confluence, Artifactory, Jenkins and PingFederate.
Updated November 18, 2026
Key Takeaways
- Java 17.0.6–17.0.21, 21, 25 and 27 are affected on AVX-512 VBMI.
- Bundled and container JVMs miss OS patches and may not appear in inventories.
- Oracle fixed builds end in .1; some vendors were unreleased on 18 Nov.
- Confirm the live process with jcmd after restart, not the disk package.
What should you inventory before you patch?
CISA warns that JDKs and Java runtimes may not appear as separate inventory entries. Bundled copies do not get operating-system updates.
- Search appliances, installers and container images for private JDKs, not only standalone Java packages.
- Start with Keycloak and PingFederate, then self-managed Jira and Confluence Data Center, Jenkins and Artifactory.
- Add Spring Boot services on an affected runtime and every Tomcat server. No advisory ties Tomcat to this CVE.
- Include Java clients that open outbound TLS. Calif reported a client-side exploit via a malicious TLS server.
Reuse the image-level inventory used for Alpine container edges instead of the host package list.
Which Java lines and CPUs are in scope?
Upwind’s 17 November account lists Java 17.0.6 to 17.0.21, Java 21 up to 21.0.13, Java 25 up to 25.0.5 and Java 27 up to 27.0.1. Standard Java 8, Java 11 and Java 17.0.0 to 17.0.5 are not affected. Oracle lists Performance Pack build 8u511b33-perf as affected.
On Linux, prioritize hosts whose /proc/cpuinfo flags include avx512f, avx512bw, avx512vbmi and bmi2. Upwind names Intel Xeon Ice Lake, Sapphire Rapids, Emerald Rapids and Granite Rapids, and AMD Zen 4 or newer. ARM is not affected. A cloud resize can move a workload onto an affected processor, so use a clean CPU check only to prioritize.
Which vendor builds close Java4Shell bundled JVMs?
Oracle’s 17 November builds are fixed only when the version ends in .1. As of 18 November, Check Point listed Corretto and Zulu as shipped, Red Hat and Temurin as not yet released, and Microsoft Build of OpenJDK and Liberica as unconfirmed.
Adoptium’s 18 November note says November 2026 Temurin releases contain the fix. Docker Hub images follow only after every binary for that JDK version is published. Upwind reproduced the bug on unfixed Temurin 21.0.13. Product bundles need the product vendor’s update.
| Vendor | 17–18 Nov status | Fixed build |
|---|---|---|
| Oracle JDK | Fixed 17 Nov 2026 | Ends in .1 |
| Amazon Corretto | Shipped 18 Nov | Vendor fixed release |
| Azul Zulu | Shipped 18 Nov | Vendor fixed release |
| Eclipse Temurin | Adoptium: Nov 2026 fix; Check Point 18 Nov: not yet | 17.0.21.1+2, 21.0.13.1+2, 25.0.5.1+2, 27.0.1.1+4 |
| Red Hat OpenJDK | Not yet released 18 Nov | Check vendor |
| Microsoft OpenJDK | Unconfirmed 18 Nov | Check vendor |
| BellSoft Liberica | Unconfirmed 18 Nov | Check vendor |
| Product-bundled JVM | Product vendor update | Not an OS package |
How do you verify the running process?
The fix or the flag takes effect only after Java restarts. Rebuild images and recreate containers before you check the process serving traffic.
- Patch Keycloak and PingFederate first, then Jira, Confluence, Jenkins and Artifactory. For self-managed Jira and Confluence, apply Atlassian’s update or the startup flag, then other exposed services, internal systems and Java clients.
- If no fixed build is available, add -XX:-UseBASE64Intrinsics and restart. It works on any architecture. Heavy Base64 decoding may slow down, so test first.
- Do not set -XX:DisableIntrinsic=_base64_decodeBlock alone; Java may fail to start. Use -XX:UseAVX=2 only on x86-64, and remove either option after you patch.
- For Elasticsearch, apply Elastic’s update or add the flag in a new .options file under config/jvm.options.d/ (or /etc/elasticsearch/jvm.options.d/ on DEB and RPM). Do not edit the root jvm.options file.
- On the live PID, run jcmd PID VM.version and jcmd PID VM.flags. Oracle fixed builds end in .1, such as 17.0.21.1.
CISA’s temporary controls are not a complete fix: restrict and validate Base64, enforce input-size limits, and limit unauthenticated access. Watch crashes, hs_err_pid logs, rogue runtimes and suspicious Java processes.
Upwind’s 17 November post said the issue was not in the CISA KEV catalog. As of 18 November, Check Point was not aware of confirmed exploitation. A triggering input has been visible since 9 September 2026. Apply the same urgency you would to confirmed PHP2Shell exploitation.
Frequently asked questions
Which Java versions are affected by Java4Shell?
Affected lines are Java 17.0.6 to 17.0.21, Java 21 up to 21.0.13, Java 25 up to 25.0.5 and Java 27 up to 27.0.1. Standard Java 8 and Java 11 are not affected, though Oracle lists Performance Pack build 8u511b33-perf as affected.
Are ARM hosts vulnerable?
No. Only x86-64 CPUs with AVX-512 VBMI run the vulnerable decoder, and ARM is not affected.
How do you confirm the running JVM picked up the fix?
After Java restarts, jcmd VM.version on the live PID should show a fixed build, such as an Oracle version ending in .1. If you set the mitigation flag, VM.flags should list -XX:-UseBASE64Intrinsics.
Is Java4Shell in the CISA KEV catalog?
Upwind’s 17 November post said it was not in the CISA KEV catalog. As of 18 November, Check Point was not aware of confirmed exploitation, and CISA still urges immediate patching.