Java4Shell (CVE-2026-114938): quick cheat sheet on who’s actually affected and what to do today
retained text
Java4Shell is a heap overflow in OpenJDK’s optimized Base64 decoder. Malformed Base64 input can write past the end of a buffer. Calif disclosed it on Nov 17 and demonstrated RCE against: * Keycloak, Jira, Confluence, Artifactory, Jenkins, and PingFederate without authentication * Kafka, Solr, and Elasticsearch with authentication **You’re only affected if all three of these are true** 1. You run OpenJDK 17.0.6 or later. Standard 8 and 11 aren’t affected, except Oracle’s Java 8 Enterprise Performance Pack. 2. The CPU is x86-64 with AVX-512 VBMI. ARM64 isn’t affected. 3. Attacker-controlled Base64 reaches the decoder. Think Basic auth headers, JWTs, SAML, and API bodies. **What to do** * **Patch the runtime.** Oracle’s fixed builds are 17.0.21.1, 21.0.13.1, and 25.0.5.1. Corretto and Zulu have fixes out too. Check your own vendor’s advisory, because Oracle’s build numbers don’t carry over to Temurin, Corretto, and the rest. * **Can’t patch yet?** Add `-XX:-UseBASE64Intrinsics`, test it, and restart the JVM. * **Don’t trust** `java -version` **on the host.** Containers and apps often bundle their own JRE. * **Hunt for signs of exploitation:** * long runs of `A...=` in Authorization: Basic headers * new `hs_err_pid` crash files * Java processes spawning `sh`, `curl`, or `wget` As I am CloudSEK employee, posting as our threat intel team wrote up Java4Shell, and I’ve boiled it down to the parts you can act on today. Thankyou
document fetched 2026-11-20 00:24 · canonical https://reddit.com/r/cybersecurity/comments/1y0dpru/java4shell_cve2026114938_quick_cheat_sheet_on