Flash

Flash·Safety & Risk·2026-11-18 07:02

Java4Shell Exposed: AI Found a 9.2-Severity OpenJDK Flaw in an Hour; Jira and More Remotely Exploitable by Default

Security firm Calif disclosed Java4Shell (CVE-2026-114938) on Nov 17: a memory-corruption flaw in OpenJDK's Base64 decoder, rated 9.2 under CVSS 4.0 and remotely exploitable without authentication against default configs of Jira and other apps; Oracle shipped patches the same day.

A bright sunlit data center corridor with Java code on a foreground monitor
AI-generated illustration

What happened

Security firm Calif published a technical write-up of Java4Shell on Nov 17. Tracked as CVE-2026-114938, the flaw sits in OpenJDK HotSpot's Base64 decoder: a malformed input of 64 letter A's followed by a single '=' triggers it, making the decoder write 62 bytes past the end of its output buffer. Calif rates it 9.2 (Critical) under CVSS 4.0; Oracle's advisory scores it 8.1 under CVSS 3.1.

Calif says it demonstrated remote code execution without authentication against the default configurations of Keycloak, Atlassian Jira and Confluence, JFrog Artifactory, Jenkins and PingFederate, and after authentication against Apache Kafka, Solr, Elasticsearch, Gerrit and Spinnaker. It also showed a client-side attack in which a Java program that opens a TLS connection to a malicious server can be compromised, and noted that everyday features such as login and file upload can feed attacker-controlled Base64 to the decoder.

AI led the discovery: Calif researcher Quang Luong directed the AI coding agent Codex to audit the JIT compiler, intrinsics and cryptography-related code, found the flaw in about an hour and had a first working exploit two hours later, for less than $200 in AI usage. Calif said it went public because details of the flaw had leaked; it is withholding product-specific exploits for now and published only a proof of concept that reproduces the memory overwrite. No exploitation in the wild has been reported.

Key facts

  1. Flaw: Hand-written AVX-512 VBMI assembly in OpenJDK HotSpot's Base64 decoder: a malformed input with '=' padding makes the output length compute as negative, so a full 64-byte mask is written
  2. Scope: Calif says every build from OpenJDK 17.0.6 onward is affected, covering distributions including Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK and Azul Zulu; the OpenJDK advisory lists Java 17, 21, 25 and 27 as affected
  3. Hardware: Only x86-64 processors with AVX-512 VBMI are affected, including Intel Xeon Ice Lake, Sapphire Rapids, Emerald Rapids and Granite Rapids, and AMD EPYC and Ryzen from Zen 4 on; ARM64 is not affected
  4. Fix: Oracle's November Critical Security Patch Update, released Nov 17, includes 11 Java SE patches, with fixed builds including JDK 17.0.21.1; OpenJDK recommends upgrading as soon as possible; workarounds are the -XX:-UseBASE64Intrinsics or -XX:UseAVX=2 startup flags
  5. Status: As of 21:38 UTC on Nov 17, Red Hat, Ubuntu, Debian, SUSE and Alpine had not yet published a fixed package for the CVE; there is no universal exploit, as each application needs its own chain

Why it matters

A memory-corruption flaw in the Java runtime itself, reachable through everyday features such as login and file upload. An AI coding agent found it in about an hour, sharply shrinking the window between a patch release and its exploitation.
Useful Tap if this story helped you
Send to a friendMakes a share image for X, WeChat, Telegram and more

SourcesCalif (Nov 17, 2026); Oracle (Nov 17, 2026). This article is compiled from public information and does not constitute investment advice.

From HIMIAO Horizon · himiao.ai

Grab todayOpenAI Codex for Students: $100 in Free CreditsHIMIAO Picks →

Follow HIMIAO Horizon

No sign-up · Unsubscribe any time

Email

Notifications

A ping on your phone or computer when the brief is out. No email needed.

HIMIAO PicksWeekly freebies: one email every Friday, a 5-minute read

Comments

  1. Loading comments…
Ask the cat