Java4Shell: an AI-assisted researcher found a critical Java flaw in an hour, for under $200
CVE-2026-114938 is a memory bug in OpenJDK's Base64 decoder that can hand an attacker, with no password, control of servers running Jira, Confluence, Jenkins or Keycloak. Oracle and OpenJDK fixed it on 17 November. No attacks are known yet, but you need to update and restart.
Sixty-four letter “A”s and an equals sign. That is all it takes to break Java. On Tuesday the 17th, security firm Calif disclosed Java4Shell, a flaw deep inside OpenJDK (the most widely used Java runtime) that can let an attacker with no password run whatever code they like on a server.
What has the industry talking is how it was found. According to Calif’s own disclosure, researcher Quang Luong needed one hour, working with AI, to spot the bug, and two more to get the first working exploit. The whole thing cost less than $200 in tokens, the unit these models are paid for in.
What is the Java4Shell vulnerability?
It’s a memory-corruption bug in Java’s Base64 decoder. Base64 turns files and binary data into text, and it is everywhere: logins, file uploads, messages between systems. To decode faster, Java uses a piece of hand-written code for x86-64 processors with AVX-512 VBMI instructions. That’s where the bug lives. A malformed input makes the routine write past the space it set aside and corrupt the memory next to it.
Calif scores it 9.2 out of 10 on the CVSS 4.0 severity scale. Oracle, which uses the older scale, gives it 8.1 and calls it “difficult to exploit”. ARM processors aren’t affected.
Which software is exposed to Java4Shell?
Calif took over Keycloak, Jira, Confluence, JFrog Artifactory, Jenkins and PingFederate with no login, in their default setups. With a user account, it also got into Kafka, Solr, Elasticsearch, Gerrit and Spinnaker. The firm stresses the list isn’t complete, since any Java application that decodes Base64 coming from outside could be in the line of fire.
These are back-office tools, but they run inside banks, telecoms, software houses and public services. It lands in a week when systems were already under the microscope, after the White House insisted the run of US outages was not a cyberattack.
Is there a fix for Java4Shell?
Yes. Oracle shipped patched builds the same day in its November security update, and OpenJDK published its own advisory. Distributions built on it, such as Temurin, Corretto and Red Hat’s, are following. At the time of disclosure there were no signs of real-world attacks.
If you run servers, there’s one step people forget: updating the package isn’t enough. Every Java program has to be restarted before the new version is actually in use.
Calif says this is the second serious flaw it has found this way in a few weeks, after PHP2Shell, and calls it the era of the “centaur hacker”, part human, part machine. For defenders the arithmetic is blunt: in this case, finding the hole and having a working attack were three hours apart.
By Oliver Grant
Illustration: Tugadaily · photos: Pixabay, panumas nikhomkhai and Márcio Carvalho / Pexels