Oracle patches Java4Shell, an OpenJDK flaw a researcher found with Codex in about an hour
Oracle patched CVE-2026-114938, nicknamed Java4Shell, on 17 November 2026. Calif says its researcher found the Base64 flaw with OpenAI's Codex in about an hour.
By Emre A.Published
Tech AI LatestOracle fixed CVE-2026-114938, a memory corruption flaw in Java's Base64 decoder nicknamed Java4Shell, in its 17 November 2026 security update and credited Quang Luong of Calif. Calif says Luong found it with OpenAI's Codex in about an hour. Oracle scores it 8.1; it hits Java 17.0.6 and later on x86-64 processors with AVX-512 VBMI. CISA urged immediate patching. No exploitation in the wild had been confirmed as of 17 November.
Key facts
- Disclosed: 17 November 2026 in Oracle's Critical Security Patch Update, which contains 655 new patches
- Flaw: CVE-2026-114938, out-of-bounds write in OpenJDK's optimized Base64 decoder; Oracle CVSS 3.1 score 8.1, Calif CVSS 4.0 score 9.2
- Affected: OpenJDK 17.0.6 and later on x86-64 CPUs with AVX-512 VBMI; native ARM64 runtimes are not affected
- Fixed builds: 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1
- Found by: Quang Luong of Calif, who the firm says used OpenAI's Codex
- Exploitation: none confirmed in the wild as of 17 November; not in CISA's Known Exploited Vulnerabilities catalog
What Oracle fixed
Oracle released its November Critical Security Patch Update on 17 November 2026 with 655 new security patches. Eleven of them are for Java SE, and Oracle says all eleven can be exploited over a network without credentials. The most serious is CVE-2026-114938, which researchers have nicknamed Java4Shell. Oracle lists it for Java SE, GraalVM for JDK and GraalVM Enterprise Edition, gives it a CVSS 3.1 base score of 8.1 with high attack complexity, and credits Quang Luong of Calif.io and Albert Yang for reporting it.
Datadog Security Labs, in its technical analysis, describes the bug as an out-of-bounds write in OpenJDK's optimized Base64 decoder. When the JVM's C2 compiler replaces the decoder with its AVX-512 native routine, malformed padding produces a negative output length, and the routine writes past the end of the destination array. In Datadog's example, the store wrote 62 bytes beyond a 98-byte array. Calif rates the flaw 9.2, Critical, under CVSS 4.0.
Who is exposed
Three conditions have to line up, according to Datadog. The runtime must be OpenJDK 17.0.6 or later, it must run on an x86-64 processor that supports AVX-512 VBMI instructions, and the application must pass attacker-controlled data to the basic or URL Base64 decoder. The MIME decoder takes a different path. Native ARM64 Java runtimes are not affected. Oracle's own list for this CVE names Java 17, 21, 25 and 27 builds and the Java 8 Enterprise Performance Pack, not standard Java 8 or 11. The fixed releases are 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1.
Datadog says denial of service is the more readily achievable impact and that remote code execution would need exploitation work tailored to each application and JVM. There is no single exploit that works against all Java applications. The US Cybersecurity and Infrastructure Security Agency still urged immediate patching and asked organizations to inventory Java runtimes bundled in third-party applications, container images and appliances, starting with internet-facing systems.
How AI found it
Calif, a security firm that publishes research on AI-assisted bug hunting, says Luong found the flaw in about an hour using OpenAI's Codex coding agent and built a first working exploit about two hours later, as reported by Quartz and BleepingComputer. The same Oracle advisory credits Nicholas Carlini of Anthropic for CVE-2026-114940, a Java TLS flaw scored 7.4. Two of the Java fixes in one quarterly update therefore trace back to researchers working at or with frontier AI labs.
This fits a pattern our cybersecurity coverage has followed all autumn. Anthropic said in October that Claude found exploit chains in major browsers and operating systems, OpenAI released GPT-6 Cyber for vetted defenders in November, and Google Project Zero said it will shorten its disclosure deadline to 30 days because AI speeds up both discovery and exploitation.
What to do now
The practical lesson is that the time between discovery and a working exploit has shrunk to hours for a skilled researcher with an AI agent, while enterprise Java patch cycles are still measured in weeks. Teams should update every runtime, including those bundled inside vendor products and container base images, then rebuild images and restart Java processes so the new runtime is loaded.
Where an update cannot ship at once, Datadog's tests found two startup flags that blocked the out-of-bounds write: -XX:-UseBASE64Intrinsics, the narrower option, or -XX:UseAVX=2 on x86-64 hosts only, since ARM64 JVMs refuse to start with that flag. Datadog also suggests checking the CPU for avx512vbmi support to prioritize hosts. The open question is how quickly attackers find application paths that feed untrusted Base64 into the vulnerable decoder; CISA's Known Exploited Vulnerabilities catalog did not list the flaw as of 17 November.
What changed
| Before | OpenJDK 17.0.6 and later on AVX-512 VBMI x86-64 CPUs carried an unknown out-of-bounds write in the Base64 decoder |
|---|---|
| After | Oracle and OpenJDK builds 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1 fix CVE-2026-114938; CISA urges immediate patching |
| Who it affects | Java applications that decode untrusted Base64 input on x86-64 servers with AVX-512 VBMI, including runtimes bundled in vendor products and containers |
Questions people ask
- What is Java4Shell?
- It is the nickname for CVE-2026-114938, an out-of-bounds write in OpenJDK's optimized Base64 decoder that Oracle patched on 17 November 2026 and scores 8.1 under CVSS 3.1.
- Which Java versions are affected by Java4Shell?
- OpenJDK 17.0.6 and later on x86-64 processors with AVX-512 VBMI. Fixed builds are 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1. Native ARM64 runtimes are not affected.
- Was Java4Shell found by AI?
- Calif says its researcher Quang Luong found it in about an hour with OpenAI's Codex and built a working exploit about two hours later. Oracle credits Luong and Albert Yang.
- Is Java4Shell being exploited?
- No exploitation in the wild had been confirmed as of 17 November 2026, and the flaw was not in CISA's Known Exploited Vulnerabilities catalog.
Sources
- Oracle Critical Security Patch Update Advisory - November 2026 (Oracle, 17 Nov 2026)
- Java4Shell: Remote Code Execution in OpenJDK (CVE-2026-114938) (Datadog Security Labs, 17 Nov 2026)
- Critical Java Vulnerability Requires Immediate Patching (CISA, 17 Nov 2026)
- Java4Shell: AI found a critical Java flaw, and Oracle patched it (Quartz, 18 Nov 2026)
- Critical Java4Shell flaw allows RCE attacks on major Java applications (BleepingComputer, 17 Nov 2026)
- A vulnpocalypse bug worthy of attention: Researchers disclose critical flaw in Java with help of AI (CyberScoop, 17 Nov 2026)
Reference pages
Spotted an error? See the corrections policy and tell the editor. Facts in this story come from the sources listed above; vendor claims are attributed.
Comments
Loading comments.





