AIToday
AI Coding AssistantsAI Safety & AlignmentGIGAZINE AIPublished: Nov 18, 2026, 16:00 JST

Quang Luong uses OpenAI's Codex to find Java4Shell in one hour

Send on LINE
Quang Luong uses OpenAI's Codex to find Java4Shell in one hour

3 Key Points

  1. What happened

    Calif's Quang Luong had OpenAI's Codex scan complex JVM code and it found a memory-corruption bug in OpenJDK's AVX-512 VBMI Base64 decoding, named Java4Shell, in about one hour, with a first exploit in two more.

  2. Why it matters

    The finding suggests AI assistance can compress vulnerability discovery and exploit development into hours at token costs under $200, shifting how quickly a single researcher can move from a hint to a working attack.

WHO IT HITSSecurity teams running OpenJDK-based Java stacks on AVX-512 VBMI-capable x86-64 processors face an urgent patching task, and vulnerability researchers gain a concrete example of AI-assisted exploit development.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, every morning.

Context & Analysis

Java is often described as memory-safe because it manages memory automatically, but its runtime is built in C, C++, and assembly, leaving room for memory-corruption flaws. OpenJDK uses the AVX-512 VBMI instruction set on supported x86-64 processors to speed up Base64 decoding, and Calif found that this acceleration path writes beyond allocated memory when handling malicious Base64 data. The impact spans both server and client Java applications, since a Java program making a TLS connection to a malicious server can be attacked as well. Calif demonstrated remote code execution without authentication against default configurations of Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins and PingFederate, and after authentication against Apache Kafka, Apache Solr, Elasticsearch, Gerrit and Netflix Spinnaker. The flaw is rated 9.2 out of 10 on CVSS 4.0, classified Critical, and affects unpatched OpenJDK 17.0.6 and later plus downstream builds such as Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK and Oracle Java SE. Calif says the vulnerable code was added to speed up some applications but brings serious risk to many that barely need that speed. The firm also frames the work as a "centaur hacker" model, where AI supplies processing power and human researchers supply expertise and judgment, and it proposes "Vibe Uncoding" to reduce software complexity by identifying and removing unnecessary features and code.

FAQ
Which Java versions and processors are affected by Java4Shell?
Unpatched OpenJDK 17.0.6 and later are affected, including Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK and Oracle Java SE. Only environments on AVX-512 VBMI x86-64 processors, such as some Intel Ice Lake Xeon and AMD Zen 4 EPYC and Ryzen chips, are vulnerable; ARM64 is not affected.
How much did the AI cost to find the vulnerability?
The token cost for using AI was under $200 in total.
Is there a fix or workaround for Java4Shell?
Oracle released a patch on November 17, 2026, and Calif advises users to apply updates promptly. As an interim measure, disabling the CPU-extension acceleration in Base64 decoding is also suggested.
Send on LINE

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleNVIDIA quarterly revenue doubles to $115.8 billion