News
Java4Shell (CVE-2026-114938) risks pre-auth code execution on major Java apps.
A Base64 decoder bug in modern Java builds can let unauthenticated attackers reach remote code execution on apps like Jira, Jenkins, and Keycloak.

Impact
- What was impacted
- Java’s accelerated Base64 decoder on x86-64 CPUs with AVX-512 VBMI (Java 17.0.6+, and lines 21/25/27). Unauthenticated paths that decode Base64 before login can corrupt memory; researchers claim RCE on several products.
- Who was impacted
- Operators of Jira, Confluence, Keycloak, Jenkins, Artifactory, PingFederate, and other Java services on Ice Lake / Zen 4-class hardware — plus anyone shipping those JDKs in containers or product bundles.
- What you need to do
- Install this week’s fixed JDK builds (Oracle, Corretto, Azul, and peers as available), restart services and rebuild images, or temporarily start the JVM with -XX:-UseBASE64Intrinsics until you can patch. Prioritize internet-facing login and token endpoints.
Calif disclosed Java4Shell, tracked as CVE-2026-114938. A faster Base64 path used after JIT compilation writes past its output buffer when handed a malformed string ending in an extra “=”. Java later rejects the string, but the overflow already happened.
Because many servers decode Basic auth headers, SAML artifacts, or CSRF tokens before authentication, the bug can be hit without a login. Calif reported pre-auth impact under default settings for Keycloak, Jira, Confluence, Artifactory, Jenkins, and PingFederate, with additional authenticated cases elsewhere.
Other labs have reproduced crashes and memory leaks more readily than full remote code execution. Oracle rates the issue 8.1 (CVSS 3.1); Red Hat’s preliminary score is higher. Canada’s Cyber Centre warned of remote unauthenticated exploitation. Active exploitation was not listed in CISA KEV at the time of reporting.
The vulnerable intrinsic only runs on x86-64 chips with AVX-512 VBMI, so the same image may be safe on one host and exposed on another. ARM64 is not affected by that path. Patch the JDK, restart, and drop the temporary JVM flags once fixed builds are live — Red Hat’s OpenJDK packages were still catching up when the story landed.
For your AI agent
Agent instructions — copy paste to Claude
You are helping me respond to Java4Shell (CVE-2026-114938): a Base64 decoder overflow in modern Java builds that can be hit before authentication on some apps (Jira, Confluence, Keycloak, Jenkins, Artifactory, PingFederate, and others). The vulnerable intrinsic runs on x86-64 CPUs with AVX-512 VBMI (Java 17.0.6+ and lines 21/25/27). Context: - What was impacted: accelerated Base64 decoding paths that run before auth checks. - Who should care: operators of the listed Java apps / any service bundling affected JDKs on Ice Lake / Zen 4-class hardware. - Fix: install vendor fixed JDK builds, restart, rebuild images. Temporary mitigation: -XX:-UseBASE64Intrinsics (or -XX:UseAVX=2 on x86-64 only). Do this in order. Ask before changing production JVMs. Prefer inventory first. 1. Inventory - Find running Java processes and container images: version, vendor (Oracle, Corretto, Temurin, Azul, Red Hat, etc.), and host CPU flags (avx512vbmi). - Flag internet-facing services that decode Basic auth / SAML / tokens before login. 2. Prioritize - Rank exposed apps (Jira, Confluence, Keycloak, Jenkins, Artifactory, PingFederate, etc.) by exposure and blast radius. 3. Patch or mitigate - Plan upgrade to fixed JDK builds; restart services; rebuild/redeploy images so the running process picks up the new JDK. - If patching is delayed, propose adding -XX:-UseBASE64Intrinsics and document rollback once patched. Do not use -XX:UseAVX=2 on ARM64. 4. Verify - Confirm post-change java -version / image digests and that the mitigation flag is present only where needed. 5. Report back - Inventory table, changes applied, systems still waiting on vendor fixes (e.g. Red Hat if still pending), and residual risk. Do not attempt exploit PoCs against production. Do not invent CVE details beyond what I provided.