All postsSHORT3 min read
Java4Shell: Calif Says an Expert With Codex Found It in 1 Hour
Calif reports expert-led Codex research behind Java4Shell. Check the affected Java versions, CPU requirements and vendor fixes.
Is your Jira patched? Calif says an expert with Codex found Java4Shell in about 1 hour. The firm reports under $200 in total tokens for discovery plus the first working exploit. The patch sweep starts with checking which Java runtimes you actually run.
What Java4Shell is
Calif disclosed Java4Shell, CVE-2026-114938, on November 17, 2026. It's a memory-corruption bug in OpenJDK's Base64 decoder. Calif says a remote attacker without credentials can overwrite heap memory, read it and reach remote code execution.
Base64 represents binary data as text. It's used in authentication protocols, file uploads and network messages. OpenJDK uses specialized AVX-512 VBMI instructions to speed up decoding on supported x86-64 processors. The vulnerable code is specific to that hardware.
How Calif says Codex helped find it
Calif says its researcher Quang Luong found the bug with Codex in about 1 hour, then built the first working exploit in 2 more hours. Calif reports under $200 in total token costs across discovery and that first exploit. That figure is a token cost.
Luong directed the AI. In his write-up, he says most early results Codex brought back were slop, including unreachable findings or findings with unrealistic exploitation requirements. He supplied context and rejected those results.
Who is affected
Calif identifies OpenJDK 17.0.6 and newer, plus the distributions built from it, with a specific CPU condition. OpenJDK's advisory lists JDK 17, 21, 25 and 27 for this CVE. Oracle's advisory also lists Oracle Java SE 8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3 and 27.0.1.0.3; Oracle GraalVM for JDK 17.0.21.0.3 and 21.0.13.0.3; and Oracle GraalVM Enterprise Edition 21.3.20.0.3. Inventory every Java runtime and check its vendor and full build against the advisory.
Calif lists these distributions built from OpenJDK as vulnerable, subject to the hardware condition:
- Amazon Corretto
- Eclipse Temurin
- Microsoft Build of OpenJDK
- Azul Zulu
- BellSoft Liberica
- SAP SapMachine
- Red Hat OpenJDK
- Oracle OpenJDK
- Oracle Java SE
- Oracle GraalVM for JDK
The CPU must be x86-64 with AVX-512 VBMI support. ARM64 CPUs aren't affected. Calif lists Intel Xeon Ice Lake, Sapphire Rapids, Emerald Rapids and Granite Rapids, plus AMD EPYC and Ryzen Zen 4 or newer, as CPU families meeting the hardware requirements.
Calif's Linux check:
grep -m1 '^flags' /proc/cpuinfo | tr ' ' '\n' | grep -E '^(avx512f|avx512bw|avx512vbmi|bmi2)$'
Calif says the output must include all 4 flags: avx512f, avx512bw, avx512vbmi and bmi2. Check each runtime's vendor and full build against the advisory as well as checking the CPU. Include runtimes bundled inside your tools in the inventory.
What Calif's tests showed
Calif reports remote code execution without a login on these applications in their default configurations:
- Keycloak
- Atlassian Jira
- Atlassian Confluence
- JFrog Artifactory
- Jenkins
- PingFederate
Calif also reports remote code execution after authentication on:
- Apache Kafka Broker
- Apache Solr
- Elasticsearch
- Gerrit
- Spinnaker
Calif says these lists are non-exhaustive. These are the firm's reported testing results.
The severity scores
Calif rates Java4Shell 9.2 out of 10 under CVSS 4.0, which it labels critical.
OpenJDK and Oracle score it 8.1 under CVSS 3.1. Keep the scorer and CVSS version with each number.
The fix and the stopgap flags
OpenJDK published its advisory and Oracle released its patch on November 17, 2026. Update each affected runtime to its vendor's fixed build.
If an update has to wait, Calif lists either of these startup flags for OpenJDK:
-XX:-UseBASE64Intrinsics
That disables hardware-accelerated Base64 encoding and decoding.
-XX:UseAVX=2
That disables AVX-512. Calif says to apply -XX:UseAVX=2 only on x86-64 hosts. OpenJDK on ARM doesn't recognize it and will fail to start.
The catch
An expert steered the AI, reviewed its output and supplied the research context. Calif's reported discovery time and token cost describe that expert-led work.
Calif says there is no universal exploit. Each target needs its own profile. The firm is withholding application-specific exploits until people have had a chance to upgrade.
Here's how you get paid
My take: sell small teams a Java patch sweep. No income guaranteed.
Find every Java runtime they run, including the ones bundled inside tools such as Jira, Confluence, Jenkins and Keycloak, and check each one's vendor and full build against the advisory. Those applications appear on Calif's reported test list. Update each affected runtime to its vendor's fixed build. Where an update has to wait, use one of Calif's stopgap flags.
Hand over a one-page report listing what you found and what you fixed. That's the service I'd offer: a runtime inventory, the updates and a report the team can keep.
Daily email
Get each breakdown in your inbox.
One email each evening, right after the Short goes live: the AI tool it covers, the full write-up with sources, and how to get paid for it. Free, and you can unsubscribe anytime.