Vulnerability alert · 18 Nov 2026
-XX:-UseBASE64Intrinsics.You are exposed if a Java 17, 21, 25 or 27 application runs on an x86-64 server whose CPU supports AVX-512 VBMI and decodes Base64 from requests, which login flows, tokens and file uploads routinely do. Cloud VMs on recent Intel Xeon (Ice Lake, Sapphire Rapids and newer) or AMD Zen 4 count. ARM servers (Graviton, Ampere) and standard Java 8 and 11 are not affected. Oracle released fixed builds on 17 November 2026. Other OpenJDK vendors (Temurin, Corretto, Zulu, Microsoft, Red Hat) are still rolling theirs out, so the JVM flag below is the fastest protection today.
For speed, HotSpot's JIT compiler replaces java.util.Base64 decoding with a hand-written AVX-512 routine once the code runs often. When that routine handles the last partial block of input, a crafted combination of trailing padding produces a negative length. The routine then writes 62 or 63 bytes past the end of the destination array on the Java heap (Horizon3.ai). Memory corruption inside the JVM is how a "safe" language ends up with remote code execution.
Oracle scores it 8.1 (CVSS 3.1) with high attack complexity; the finders at Calif score it 9.2 under CVSS 4.0. The higher number is the better guide to urgency. The bug sits in a library call that thousands of applications make on untrusted input, and a failed exploit attempt usually just crashes the service, so attackers can retry (Tenable FAQ).
You need all three conditions:
Check the CPU on a Linux host; all four flags must print for it to be vulnerable (Cycode):
grep -m1 '^flags' /proc/cpuinfo | tr ' ' '\n' | grep -E '^(avx512f|avx512bw|avx512vbmi|bmi2)$'
Remember that a cloud instance family can move to newer CPUs when it is resized or restarted. "Not vulnerable today" on one host does not cover the fleet.
This isn't only about the big products. The vulnerable call is java.util.Base64, and the most common place it meets attacker input is the Authorization: Basic header, which is decoded before the password is checked. HeroDevs found that path in Spring Security HTTP Basic, Jetty's BasicAuthenticator and Tomcat's BasicAuthenticator (9.0.89+ and 10.1.23+). JWT handling depends on the library: Auth0 java-jwt uses Base64.getUrlDecoder() (HeroDevs). Calif also demonstrated code execution against a sample Spring Boot app. No framework update fixes this; only the JDK does.
Wiz says its own AI research harness produced a working proof of concept within two hours, before full disclosure (Wiz). Assume attackers can build exploits quickly too.
Calif says the list is not exhaustive and that each application needs its own exploit. It has published a safe reproducer that tests a JVM and CPU, but is withholding the product exploits for now. At least one other researcher says he has built a working application exploit and not released it (Tenable). Identity providers (Keycloak, PingFederate) and CI servers (Jenkins) deserve the first look: compromise there hands over every system behind them.
Exploitation status: none reported, and not yet in CISA's KEV catalog. CISA's 17 November alert urges organisations to patch immediately. The details leaked before the fix, so the usual gap between disclosure and exploitation is shorter than normal. Our CVE lookup will show the moment it lands in KEV.
-XX:-UseBASE64Intrinsics to the JVM options (JAVA_TOOL_OPTIONS, setenv.sh, the service unit or the container entrypoint) and restart. It turns off the vulnerable fast path and costs some Base64 performance. Don't use the alternative -XX:UseAVX=2 on mixed fleets: a JVM on ARM won't start with it. Neither flag is an Oracle-supported fix (Horizon3.ai).jcmd <PID> VM.flags -all | grep UseBASE64Intrinsics should show false.docker run --rm --entrypoint java <image> -version.hs_err_pid*.log files on internet-facing Java services, and on unusual Base64 payloads in authentication headers if your WAF can see them.Keycloak, Jira, Confluence and Jenkins sit in the middle of most fintech and SaaS estates, often reachable from the internet for SSO or partner access. For PCI DSS and NIS2 this is a textbook critical vulnerability with a vendor fix: patch it in your critical window, document the interim mitigation, and keep evidence of which hosts were checked. Our stack check sends an email the moment a product you run appears in CISA's exploited list. The radar shows which new CVEs are climbing in exploitation likelihood before that.
Possibly, even without Jira or Jenkins. Spring Security, Tomcat and Jetty decode HTTP Basic auth headers with java.util.Base64 before checking the password. Any app using them on an affected JDK and AVX-512 CPU is reachable without login, and only a JDK update or the JVM flag protects it.
No. The vulnerable code is an AVX-512 routine that only runs on x86-64 processors with AVX-512 VBMI support. ARM64 servers such as AWS Graviton and Ampere are not affected.
Researchers report that starting the JVM with -XX:-UseBASE64Intrinsics disables the vulnerable code path, at some cost to Base64 performance. It is not an Oracle-supported fix, so install your vendor's patched Java build as soon as it is available.
We inventory Java runtimes across hosts, containers and appliances, roll out the interim flag safely, and track vendor patches through to closure, with the evidence your PCI DSS or NIS2 auditor will ask for.
Request a quote →