JAVA_TOOL_OPTIONS='-XX:-UseBASE64Intrinsics' java -jar your-app.jar
Published by Lenny Primak on the
The OpenJDK team has published a security advisory for CVE-2026-114938, also known as Java4Shell. This is a vulnerability in the OpenJDK HotSpot Base64 decoder, not a vulnerability in Apache Shiro itself. Shiro applications can still be vulnerable because Shiro decodes Base64 data using the JDK.
The vulnerable code is an optimized Base64 decoding path in HotSpot JVM. Exploitation requires a vulnerable Java runtime and an x86-64 processor with AVX-512 VBMI support. This is a CPU capability, not a condition limited to Intel processors; some AMD processors support it as well. ARM64 systems are not known to be affected.
The Java runtime vendor and version matter. OpenJDK and Oracle have published affected-version details, and other Java distributors may publish their own build-specific guidance. Check the advisory for the vendor and runtime you deploy, including JDKs bundled with applications, containers, and appliances.
Shiro’s web CookieRememberMeManager Base64-encodes serialized identity data in the remember-me cookie and decodes that cookie when reading it. Shiro’s Base64 decoder delegates to java.util.Base64, so a request handled through this path may be vulnerable.
This does not mean every Shiro deployment is exploitable. Exposure depends on the Java runtime, CPU capabilities, and whether an application reaches the affected decoder path. Base64 is an encoding, not encryption, and changing Shiro versions alone does not fix a vulnerable JDK.
Upgrade to a fixed Java runtime from your distributor as soon as possible. Inventory all JVMs, including those bundled with services and container images, and follow the affected-version and update guidance from the Java vendor. Prioritize internet-facing systems.
Until you can apply the update, the following JVM option mitigates this issue on runtimes that support it:
JAVA_TOOL_OPTIONS='-XX:-UseBASE64Intrinsics' java -jar your-app.jar
For managed services and containers, configure the option on the actual application JVM and restart the service. Treat this as a temporary mitigation, verify that your runtime accepts the option, and still apply the vendor’s fixed runtime update.