Overview
- Researchers at Calif used AI tools to find a memory‑safety bug in OpenJDK and disclosed it on Tuesday, November 17, 2026.
- Oracle and the OpenJDK project issued fixes the same day and security agencies are urging immediate patching with JVM restarts required.
- The flaw affects OpenJDK builds starting with 17.0.6 and downstream distributions only when running on x86‑64 CPUs that support AVX‑512 VBMI; ARM64 systems are not affected.
- Calif demonstrated pre‑authentication remote code execution against products such as Keycloak, Jira, Confluence, JFrog Artifactory, Jenkins, and PingFederate but researchers are withholding product‑specific exploit chains and there are no confirmed in‑the‑wild attacks yet.
- Temporary mitigations include starting the JVM with -XX:-UseBASE64Intrinsics or -XX:UseAVX=2 and teams should inventory bundled runtimes and prioritize internet‑facing identity and build systems for patching or isolation.