Java4Shell (CVE-2026-114938)
A heap out-of-bounds write in OpenJDK's x86-64 Base64 decoder that Calif says it found and weaponized with OpenAI's Codex in hours, disclosed Nov 17 2026 with claimed pre-auth RCE against Jira, Jenkins, Keycloak and more.
What happened
On Nov 17 2026, after Oracle shipped fixes that afternoon, security firm Calif disclosed CVE-2026-114938, which it named Java4Shell. The bug is in the HotSpot JVM’s x86-64 intrinsic for java.util.Base64 decoding: on CPUs with AVX-512 VBMI (Intel Ice Lake and Sapphire Rapids servers, AMD Zen 4 and Zen 5), a short malformed Base64 string makes the decoder write past the end of a heap buffer. Calif and Red Hat say OpenJDK 17.0.6 and later are affected, across the 17, 21, 25 and 27 lines and the common distributions (Corretto, Temurin, Zulu, Red Hat and others); Red Hat says OpenJDK 8 and 11 are not, and ARM machines are not known to be affected.
Because Base64 decoding of untrusted input is everywhere in Java services, Calif says it demonstrated pre-authentication remote code execution in its own tests against default installs of Keycloak, Atlassian Jira and Confluence, JFrog Artifactory, Jenkins and PingFederate, and post-authentication RCE against Kafka, Solr, Elasticsearch and others. It is withholding the product-specific exploit chains for now. Red Hat rates the flaw Critical and says it is expediting fixes; the GitHub advisory scores it High (CVSS 3.1 8.1). Mitigations are to disable the intrinsic (-XX:-UseBASE64Intrinsics) or cap AVX at level 2.
VulnCheck reproduced the bug and says denial of service is trivial but RCE needs non-trivial heap grooming plus a target-specific memory leak; it said the flaw was not known to be exploited in the wild on Nov 17 and made a full RCE exploit available to its paying intelligence customers that evening. It was not in CISA’s KEV catalog as of the Nov 17 feed.
AI involvement
Calif says that, as with the PHP flaws it found earlier, it used AI to find and weaponize Java4Shell: researcher Quang Luong directed OpenAI’s Codex to audit HotSpot, found the bug after about 20 minutes of prompting and an hour overall, and had a first working exploit two hours later, for under $200 in tokens. These are Calif’s own claims. No source gives an age for the flaw beyond the affected range starting at 17.0.6. It is listed on the AI CVE tracker.
Timeline
Every dated event in the wiki that involves Java4Shell (CVE-2026-114938), newest first.
Calif says researcher Quang Luong directed OpenAI's Codex to audit the HotSpot JVM and found a heap out-of-bounds write in the x86-64 AVX-512 Base64 decode intrinsic in about an hour, with a first working exploit two hours later, for under $200 in tokens (company claims). It affects OpenJDK 17.0.6 and later on CPUs with AVX-512 VBMI; Calif reports pre-auth RCE in its own tests against Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate. Red Hat rates it Critical; VulnCheck says denial of service is trivial but RCE needs non-trivial heap grooming, and that it was not known to be exploited in the wild on Nov 17. Oracle shipped fixes the same day.
Connections
Java4Shell (CVE-2026-114938) and everything one link away. Drag to move, scroll to zoom, click a node to open it.Open in the full graph →
What links here
Concept AI and CVEs: latent flaws, now exploitable
Company Calif
Sources
- Calif, “Java4Shell: Write once, RCE everywhere”, Nov 17 2026
- Red Hat, “RHSB-2026-018 Remote Code Execution via memory corruption on x86-64 systems - OpenJDK (CVE-2026-114938)”, Nov 17 2026
- VulnCheck, “Java4Shell CVE-2026-114938: Fine, I Guess We'll Do This Again”, Nov 17 2026
- JFrog Security Research, “Java4Shell: What We Know About the Critical OpenJDK RCE Vulnerability (CVE-2026-114938)”, Nov 17 2026
- GitHub Advisory Database, “GHSA-6g7j-4xh3-xq2q”, Nov 18 2026