News Vulnerabilities & Zero-Days
Java4Shell: OpenJDK Base64 Flaw Opens Pre-Auth RCE in Java Apps
CVE-2026-114938 is a memory-corruption bug in the hardware-accelerated Base64 decoder inside OpenJDK's HotSpot JVM. Calif.io says it reached unauthenticated code execution on default installs of Keycloak, Jira, Jenkins and other products, and CISA is urging immediate patching.

Key takeaways
- CVE-2026-114938 sits in the HotSpot JVM's AVX-512 VBMI Base64 decoder, so it reaches any Java app that decodes Base64 before authentication.
- Calif.io reports pre-auth code execution on default installs of Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate, based on its own testing.
- Exposure depends on CPU: Calif says x86-64 with AVX-512 VBMI is affected and ARM64 is not.
- CISA recommends inventorying JDKs bundled in third-party apps, container images and appliances, starting with internet-facing systems.
- CISA has not reported exploitation in the wild, and the JVM flag -XX:-UseBASE64Intrinsics is a documented workaround where patching lags.
Calif.io has disclosed CVE-2026-114938, a memory-corruption flaw in the AVX-512 VBMI Base64 decoder path of OpenJDK's HotSpot JVM. Oracle shipped fixes in its latest Critical Security Patch Update, OpenJDK published a matching advisory the same day, and CISA issued a standalone alert titled "Critical Java Vulnerability Requires Immediate Patching".
Why this one is different #
The bug is in the runtime, not in an application or library. Any Java service that decodes Base64 before it authenticates the caller is a candidate. The Hacker News cites HTTP Basic login headers and SAML artifacts as examples of input that takes that path. CISA's alert says specially crafted Base64 input could crash the JVM and allow unauthenticated remote code execution.
Calif reports pre-auth code execution under default configurations against Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins and PingFederate. It reports post-auth code execution against Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit and Spinnaker. These results come from Calif's own testing, and Calif says the lists are not exhaustive. The firm is withholding product-specific exploit chains until users have had a chance to upgrade.
Scoping exposure #
There is a hardware precondition, which makes triage faster than usual:
- Calif says the flaw only triggers on x86-64 CPUs with AVX-512 VBMI, meaning Intel Ice Lake and later and AMD Zen 4 and later.
- Calif says ARM64 is not affected.
- The OpenJDK advisory places the bug in the hotspot/compiler component and lists the affected release lines. It does not mark the oldest long-term-support lines as affected, but Oracle's advisory additionally lists a performance build on its oldest supported Java SE line as affected, so Oracle customers on that line must check Oracle's notice. Check the advisory and your vendor's notice for exact builds.
The harder part is finding every JDK. CISA specifically recommends inventorying JDKs bundled inside third-party applications, container images and appliances, and prioritising internet-facing systems.
Severity, stated carefully #
Oracle, as the CVE numbering authority, rates the flaw High and describes it as difficult to exploit, with an unauthenticated network attacker able to achieve takeover. Calif scores it Critical under the newer CVSS standard. Those are two different assessments from two different parties.
CISA's alert does not say the flaw is being exploited in the wild, and the CVE is not in the Known Exploited Vulnerabilities catalog.
Workarounds #
Where patches lag, Calif documents two JVM launch options:
-XX:-UseBASE64Intrinsics, which disables the vulnerable intrinsic.-XX:UseAVX=2, which Calif notes breaks OpenJDK startup on ARM, so do not apply it fleet-wide without checking architecture.
The AI angle #
Calif states it used an AI coding agent to find and weaponize the bug, and claims roughly one hour to find it and two more hours to a first working exploit. That is the researchers' own account, but it is a useful data point on how cheap deep runtime bugs are becoming to find.
Sources
- Java4Shell: Write once, RCE everywhere, Calif.io
- Critical Java Vulnerability Requires Immediate Patching, CISA
- Oracle Critical Security Patch Update Advisory - November 2026, Oracle
- OpenJDK Vulnerability Advisory: 2026/11/17, OpenJDK
- CVE-2026-114938, CVE Program
- Java4Shell Flaw (CVE-2026-114938) Enables Pre-Auth RCE in Jira, Jenkins, Keycloak and More, The Hacker News
Questions this raises
- Is CVE-2026-114938 being exploited in the wild?
- CISA's alert does not say so, and the CVE is not in the Known Exploited Vulnerabilities catalog. Calif.io says it is withholding product-specific exploit chains until users have had a chance to upgrade.
- How do I tell whether my Java services are exposed?
- Check three things: whether the JDK is on an affected release line per the OpenJDK advisory or your vendor's notice, whether the host CPU is x86-64 with AVX-512 VBMI, and whether the application decodes Base64 from untrusted input. Remember JDKs bundled inside containers, appliances and third-party products.
- What can I do if I cannot patch yet?
- Calif.io documents launching the JVM with -XX:-UseBASE64Intrinsics, or with -XX:UseAVX=2. Calif notes the second option breaks OpenJDK startup on ARM.