NEWS

Follow-Up: Java4Shell Details Published, Patches Out and Jenkins, Jira, Keycloak Shown Exploitable

New: Calif published Java4Shell (CVE-2026-114938) details. Fixes shipped Nov 17; apps like Jenkins, Jira and Keycloak were exploited in tests on AVX-512 CPUs.

Dylan H.

News Desk

November 17, 2026
3 min read
Follow-Up: Java4Shell Details Published, Patches Out and Jenkins, Jira, Keycloak Shown Exploitable

This is a follow-up to our earlier report, Oracle Patches 11 Java Flaws as Reported OpenJDK RCE 'Java4Shell' Emerges. That article said the fix status was unconfirmed. Researchers at Calif have since published their writeup, and Oracle and OpenJDK shipped fixes on November 17.

What is new

  • Fixes are available. Oracle's November 2026 Critical Patch Update carries the fix. The upstream change is tracked as JDK-8393212 and was committed under embargo on October 14 as "Base64 optimization improvements". Endor Labs notes the CVE-to-JDK mapping is not formally confirmed, though the mechanism matches Calif's writeup.
  • Root cause is public. CVE-2026-114938 is a heap out-of-bounds write in HotSpot's AVX-512 Base64 decode intrinsic. A malformed, padded input tail makes the JIT-compiled decoder write past its output array before the input is rejected. Datadog describes a 62-byte write beyond a 98-byte destination array.
  • Real applications were exploited in testing. Calif reports unauthenticated RCE against Keycloak, Atlassian Jira and Confluence, JFrog Artifactory, Jenkins and PingFederate. Authenticated RCE was shown against Apache Kafka, Solr, Elasticsearch, Gerrit and Spinnaker. Sample Struts and Spring Boot apps also fell.
  • AI-assisted discovery. Calif says researcher Quang Luong found the flaw with OpenAI's Codex and built an initial exploit for under $200 in usage costs.
  • Severity. CVSS 4.0 is 9.2 (Calif). Oracle rates it 8.1 under CVSS 3.1.

Who is affected

ConditionDetail
JDKUnpatched OpenJDK 17.0.6 and later, from any vendor (Oracle, Corretto, Temurin, Zulu, Microsoft, Red Hat)
CPUx86-64 with AVX-512 VBMI (Ice Lake and later Xeons, AMD Zen 4 and later)
Not affectedJava 8 and 11 standard builds, ARM64, CPUs without VBMI
DecodersBasic and URL decoders; the MIME decoder is not affected

Attackers still need an application-specific path that feeds untrusted Base64 to the decoder. Calif has published a proof of concept for the memory corruption but withheld its weaponized chains. No in-the-wild exploitation had been confirmed as of November 17, though the researchers say details leaked before the patch.

  1. Install your JDK vendor's November 2026 build that includes JDK-8393212, then restart the services.
  2. Prioritize internet-facing Jenkins, Jira, Confluence, Keycloak, Artifactory and PingFederate on AVX-512 hardware.
  3. If you cannot patch yet, add -XX:-UseBASE64Intrinsics to disable the accelerated decoder, or -XX:UseAVX=2 to disable AVX-512. Do not use the latter on ARM64, where the JVM fails to start.
  4. Treat workarounds as temporary and watch for exploitation reports.

Sources