Java4Shell, tracked as CVE-2026-114938, is a memory-corruption flaw in the Base64 decoder of OpenJDK, and the fixes shipped the same day Calif published it, on November 17. What decides whether a given server is exposed is its processor, because the vulnerable code runs only where the CPU supports AVX-512 VBMI.

What was disclosed

Research firm Calif disclosed the flaw as a bug in hand-written machine code that OpenJDK uses to decode Base64 faster on x86-64 chips. Calif says malformed input can overwrite neighboring heap memory, which can leak data in the manner of Heartbleed or lead to remote code execution. It scores the flaw 9.2 out of 10 under CVSS 4.0. The OpenJDK advisory lists the same flaw at 8.1 under CVSS 3.1, with attack complexity rated high.

Calif says it found the bug with AI assistance. In its words, “It took our own Quang Luong an hour to discover the vulnerability, and two more hours to develop the first working exploit.” The firm puts the total token cost under $200. It also says there is “no universal exploit”, because the steps depend on how an application uses Base64.

Advertisement

CyberTech Your brand belongs here. Reach the decision-makers who read CyberTech every day. Premium placements across the site and newsletter. Advertise with us

Who is exposed

Red Hat’s security bulletin says the flaw affects OpenJDK 17.0.6 and later on x86-64 systems whose CPU supports the AVX-512 VBMI instruction set. Red Hat says ARM64 systems and x86-64 chips older than Intel Ice Lake or AMD Zen 4 are not known to be affected, and that OpenJDK 8 and 11 do not contain the vulnerable code path. The Canadian Centre for Cyber Security’s alert AL26-029 lists Oracle Java SE 8 build 8u511b33-perf among the affected products, so the two vendors do not agree on Java 8, and teams running it should read Oracle’s advisory for their exact build.

Calif reports unauthenticated remote code execution in default configurations of Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins and PingFederate. It reports code execution after login in Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit and Spinnaker. Calif calls the list non-exhaustive and says ordinary features such as authentication and file uploads can reach the decoder in other applications built on Struts or Spring Boot. Red Hat adds that any product supported on Red Hat Enterprise Linux, including container images built on its base images, is potentially affected until those images are rebuilt.

VulnCheck, citing Calif’s write-up, lists the builds that carry the same code as Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, BellSoft Liberica, SAP SapMachine, Red Hat OpenJDK, Oracle OpenJDK, Oracle Java SE and Oracle GraalVM for JDK. A team that picked its Java from any of those vendors needs that vendor’s notice before it can say its own servers are clear.

How hard exploitation is

VulnCheck reproduced the flaw on Ice Lake hardware and found that crashing an affected JVM is trivial for a request that reaches a Base64 decoding path, because a burst of requests reliably took a service down in its testing. Code execution is a different matter. “Remote code execution, by contrast, has a substantially higher bar,” wrote Caitlin Condon, VP of Security Research at VulnCheck, who said it needs heap grooming plus a target-specific memory disclosure to get past address randomization.

Both VulnCheck and the Cyber Centre say they know of no exploitation in the wild at the time of their writing. The Cyber Centre adds that this “can change quickly.”

What it means for the security leader

The patch list for this flaw cannot be built from a software inventory alone. A Java 17 service running on an ARM instance and the same service on an Ice Lake or Zen 4 host share a version number and differ in exposure. In our reading, the useful inventory column here is the processor, and teams that already track instance types will finish triage first.

Newsletter

Get the week's best tech coverage.

Free. Read by thousands of HR, tech, and business leaders.

The second difficulty is that the runtime sits inside other products. Jenkins, Keycloak and Confluence ship or depend on a JVM, so the fix may arrive through a vendor release or a rebuilt container image instead of an operating system update. We covered the same pattern in the exploited Apache Axis flaw in Confluence and N-central, where the vulnerable library lived inside two products.

The third is speed. Google’s threat intelligence group described a framework that turns published patches into exploits, and Calif’s own timeline of about three hours from discovery to a first working exploit shows the same compression from the finder’s side. We made a related point about network rules as a stopgap for PHP2Shell: they buy time and do not replace the update.

What defenders should do

The Cyber Centre recommends inventorying Java runtimes by vendor and full build version, updating to a fixed supported release, and putting internet-facing systems first. It also tells teams to identify third-party products, appliances and containers that bundle Java and to watch their vendors for updates.

For systems that cannot be patched yet, the Cyber Centre suggests the JVM flag -XX:UseAVX=2, which turns off AVX-512 use, and says lscpu | grep avx512 shows whether a Linux host’s processor supports it. VulnCheck tested disabling the Base64 intrinsic with -XX:+UnlockDiagnosticVMOptions -XX:-UseBASE64Intrinsics and verified that it stopped the overflow on OpenJDK 17, 21 and 25. The Cyber Centre also advises isolating internet-facing applications from public networks until a fix is applied, and reviewing web server, application and authentication logs for suspicious activity.

Check each distribution’s own advisory for the fixed build number, because Amazon, Red Hat and other vendors publish their own bulletins and some were still updating them when this was written. Then rebuild container images on updated base images, since a patched host does not change what runs inside an old image.

Source: OpenJDK Vulnerability Advisory, November 17, 2026