TL;DR: What is Java4Shell?
Java4Shell (CVE-2026-114938) is a memory-corruption bug in the Base64 decoder of OpenJDK, the code under almost every Java runtime. Security firm Calif disclosed it on 17 November 2026, the same day Oracle shipped fixed builds. A short malformed Base64 string makes Java write 62 bytes past a memory buffer, and Calif showed it can lead to takeover before login on default installs of Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate. Only Java 17.0.6 and newer on Intel and AMD servers with AVX-512 VBMI run the vulnerable code; ARM is not affected. Calif found it with OpenAI's Codex in about an hour. Patch, restart, and check the Java that ships inside your products.
Developing story. Last updated 19 Nov 2026, 10:30 CET. We'll update this article as Oracle, OpenJDK and software vendors publish more.
Update 19 Nov, 10:30 CET: Probing has started: GreyNoise counted 187 Java4Shell-shaped requests from 5 IP addresses, with no successful intrusion reported, and the bug is still off CISA's exploited list. Red Hat, Ubuntu, Microsoft, Azul and Eclipse Temurin (Linux) have shipped fixed builds, while Debian stable, Temurin for Windows and macOS, the official Temurin Docker images and Oracle GraalVM were still waiting. Java 8 and 11 are confirmed not affected. Jenkins and Keycloak published fixes, and Atlassian says its Cloud customers need to do nothing.
Are you getting customers from ChatGPT yet?
More and more traffic is coming from Perplexity, ChatGPT, Grok and other AI tools.
👉 Rank on ChatGPT