✉ The Friday AI Brief: the week's 5 best AI stories, tools & comparisons — in your inbox every Friday morning.

Oracle logo

Java4Shell: GPT-6 Cyber Found a Critical Flaw in Java Itself — Oracle Patched It the Same Day

An AI model found a critical remote-code flaw in Java itself — and Oracle patched it the same day it was disclosed. The bug, dubbed Java4Shell (CVE-2026-114938), sits in OpenJDK’s hardware-accelerated Base64 decoder, and security firm Calif says it achieved unauthenticated remote code execution against default installations of Jenkins, Jira, Confluence, Keycloak, JFrog Artifactory and PingFederate. Why it matters: Java runs inside a huge share of enterprise software, and this flaw lives in the runtime itself — patching the JDK, not just your apps, is the fix.

November 17, 2026

What happened

Calif disclosed Java4Shell on Tuesday, November 17, the same day Oracle and the OpenJDK project shipped fixes. The flaw is an out-of-bounds memory write in the hand-written x86-64 assembly HotSpot uses to speed up Base64 decoding on processors with AVX-512 VBMI instructions. Malformed Base64 padding produces an incorrect write mask, so the decoder writes past its buffer and corrupts heap memory — before Java rejects the input. Calif rates the flaw 9.2 under CVSS 4.0; Oracle’s record scores it 8.1 under CVSS 3.1 and calls it remotely exploitable without authentication, albeit with high attack complexity. CISA has urged organizations to review their software inventory for JDKs and Java runtimes, including copies bundled inside third-party applications, container images and appliances.

How AI found it

Calif researcher Quang Luong used OpenAI’s Codex to audit the JVM’s compiler, optimized routines and cryptography code. The New York Times reported the work used GPT-6 Cyber, OpenAI’s specialized cybersecurity model available through Codex, and said it independently verified the vulnerability from Calif’s proof-of-concept details. Calif says Luong found the flaw in about an hour and built the first working exploit in roughly two more hours, then used heap grooming to turn memory corruption into remote code execution. Wiz says its Atlas AI research system also produced a proof-of-concept within about two hours. Calif is clear about the limits: there is no universal exploit, each target application needs a tailored chain, and no in-the-wild attacks have been reported.

Who is affected, and what to do

The bug affects unpatched OpenJDK builds starting with 17.0.6, including affected releases of Java 21, 25 and 27, on x86-64 systems whose CPUs support AVX-512 VBMI; ARM64 systems are not affected. Oracle and Amazon have shipped fixed builds, while other distributions were still publishing theirs at disclosure time. If you cannot patch immediately, Red Hat recommends starting affected JVMs with -XX:-UseBASE64Intrinsics, which disables the vulnerable hardware-accelerated decoder. Updating application dependencies alone does not fix this — the runtime itself has to be updated, including JVMs bundled inside products and containers.

Why it matters

This is the clearest public example yet of the new shape of vulnerability research: a frontier cyber model, a researcher steering it, and a critical flaw in foundational software found and weaponized in an afternoon for a token bill Calif puts under $200. That cuts both ways — defenders like Calif and Wiz get there faster, but so will attackers once a disclosure is public. For anyone running Java in production, the practical takeaway is boring and urgent: inventory every runtime you ship, patch it, and do not assume a bundled JDK updates itself. Everything AI, tested — and this week, that includes the plumbing underneath the AI itself.

Frequently asked questions

What is Java4Shell?

Java4Shell is CVE-2026-114938, a memory-corruption flaw in OpenJDK’s AVX-512 Base64 decoder that can let an unauthenticated attacker crash a Java application or, with a tailored exploit chain, run code remotely.

Which Java versions are affected?

Unpatched OpenJDK 17.0.6 and later, including affected Java 21, 25 and 27 releases, on x86-64 hardware with AVX-512 VBMI support. ARM64 is not affected.

How do I fix Java4Shell?

Update the JDK/JRE itself to a patched build from your distribution. As a stopgap, launch the JVM with -XX:-UseBASE64Intrinsics to disable the vulnerable decoder path.

Sources: Gizmodo, DevOps.com, CyberKendra, New York Times (via Gizmodo), CISA

Leave a Comment

Your email address will not be published. Required fields are marked *

Get the 5 best AI tools every week

Top AI news, tools, and prompts — one short email. Free, unsubscribe anytime.

Run a newsletter of your own? Monetize and grow it with SparkLoop →

Scroll to Top