Java4Shell flaw in Java 17+ HotSpot could allow code execution on Jira, Jenkins and Keycloak servers
Administrators running Java on AVX-512 VBMI x86-64 chips should patch or restrict Base64 input now, since scanning has already begun.
Security firm Calif disclosed Java4Shell, tracked as CVE-2026-114938, a memory-corruption flaw in the Base64 decoder of OpenJDK's HotSpot JVM on x86-64 chips with AVX-512 VBMI, affecting Java 17.0.6 and later. Malformed Base64 input can write past a buffer before Java rejects it, and Calif says this can be chained into unauthenticated code execution against default setups of Keycloak, Jira, Confluence, Jenkins, JFrog Artifactory and PingFederate, and authenticated execution against several others. Oracle and OpenJDK shipped fixes this week, and Amazon and Microsoft have patched their builds, while Red Hat and Atlassian were still working on theirs. Early scanning has started, with GreyNoise and others logging probes, though no successful intrusions have been confirmed, and CISA has urged immediate patching or compensating controls such as limiting Base64 input and unauthenticated access.
Why it matters
The flaw sits in a core part of the Java runtime rather than a single application, so the exposure depends on the processor a server runs on and on whether the vendor fix has reached that build. Calif says default setups of several widely used enterprise products can be reached without an account, which raises the stakes for internet-facing deployments. Red Hat and Atlassian had not yet shipped fixes at the time of the disclosure, so some operators have to rely on compensating controls for now. Scanning from several IP addresses has been logged, but no successful intrusions have been confirmed, so the window to patch before exploitation is the immediate question.
Matters or hype?
Does this story matter, or is it hype? Vote before you see what everyone else said.