What the bug is. Base64 is the everyday way software turns binary data into text, and it shows up in logins, file uploads and network messages. To decode it faster, OpenJDK uses special AVX-512 VBMI instructions on some x86-64 chips. Calif found a flaw in that hand-written fast path: malformed input overwrites nearby memory. The trigger is just 64 A characters followed by = (128 on older OpenJDK 17 builds). Calif says this can leak memory the way Heartbleed did, or lead to remote code execution.
Who is exposed. OpenJDK 17.0.6 and later and the builds made from it, including Oracle Java SE, Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu and Red Hat OpenJDK. The OpenJDK advisory lists Java 17, 21, 25 and 27 as affected; 8 and 11 are not. It only bites on x86-64 CPUs with AVX-512 VBMI, which covers many modern server processors. Calif showed pre-auth RCE on Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate, and post-auth RCE on Kafka, Solr, Elasticsearch, Gerrit and Spinnaker. It also showed client-side compromise of a Java program that connects over TLS to a malicious server.
How bad is it right now. Calif published a proof of concept for the memory corruption but not its weaponized app exploits, and there is no single exploit that works everywhere: an attacker has to find a way to feed bad Base64 to each app. Calif says researcher Quang Luong found the bug with OpenAI's Codex in about an hour and had a first working exploit about two hours later, for under $200 in AI cost. That speed is the warning. Expect the gap between patch and attack to be short.
Defender move. Patch the Java runtime itself, not just the app on top of it. The fixed Oracle builds are 17.0.21.1, 21.0.13.1 and 25.0.5.1 (per Datadog Security Labs and HeroDevs). Pull the matching update from your Corretto, Temurin, Zulu, Microsoft or Red Hat vendor, and remember that bundled JREs inside appliances and containers count too. Start with internet-facing Jenkins, Jira, Confluence, Keycloak and PingFederate. If you can't patch today, Calif's stopgap is starting Java with -XX:-UseBASE64Intrinsics, which turns off the buggy fast path, or -XX:UseAVX=2.
