Oracle and OpenJDK released fixes on November 17, 2026, for CVE-2026-114938, nicknamed Java4Shell, a memory-corruption flaw in the Java runtime’s hardware-accelerated Base64 decoder that can be reached over the network without logging in.
Oracle and OpenJDK confirm the CVE, the score, and that it is reachable over the network without authentication. The researchers who found it, Calif, report working remote code execution against several widely used enterprise products. Oracle rates the flaw 8.1 (CVSS 3.1); Calif rates it 9.2 (CVSS 4.0).
What’s confirmed
Oracle rates the flaw as difficult to exploit.
Calif and Upwind agree it is an out-of-bounds heap write in the AVX-512 Base64 decoder, reachable through ordinary input paths such as HTTP Basic authentication headers and tokens.
What’s reported but not yet independently verified
Calif says it turned the bug into pre-authentication code execution in default configurations of products including Keycloak, Jira, Confluence, Artifactory, Jenkins, and PingFederate, and that a Java program connecting to a malicious TLS server can also be compromised.
Each attack needs a tailored setup, and Calif is withholding product-specific exploit chains while organizations patch. Some early analyses expected only a crash, but Calif’s write-up reports more.
We have not seen independent reproduction of code execution. Other researchers now say they have working exploits, but none have been published. As of November 18, GreyNoise reports scanning for the flaw with no successful exploitation, and the CVE is not in CISA’s Known Exploited Vulnerabilities catalog.
Why exposure varies
Three factors decide whether a system is at risk.
- The Java build and vendor: OpenJDK 17.0.6 and later, including 21, 25 and 27, are affected. Java 8 and Java 11 are not affected, with one exception: Oracle’s Java 8 Performance Pack. Oracle’s fixes are out. Debian has fixed its unstable branch while stable releases are pending. Other distributions ship on their own schedules. These are the statuses as of November 18, 2026:
- Fixed: Oracle, Azul Zulu, Amazon Corretto, Microsoft Build of OpenJDK
- Not yet fixed: Eclipse Temurin, Red Hat, Ubuntu, Debian stable
- The CPU: Only x86-64 processors with AVX-512 VBMI (Intel Ice Lake or later, AMD Zen 4 or later) run the vulnerable code. ARM64 does not.
- Whether untrusted data can reach Java’s built-in Base64 decoder, including through frameworks and libraries.
Because these facts are hard to establish across a large estate, our advice is to patch every affected Java runtime and use the CPU check to set priority, not to exempt systems.
What to do today
- Inventory every Java runtime, including JDKs bundled inside applications such as Jenkins, Elasticsearch, Kafka, and Keycloak, and those in container images. Running java -version on the host can name the wrong one.
- Apply Oracle’s fixed builds or your vendor’s fix as it ships, restart every JVM and rebuild container images. For commercial products that bundle Java, follow the product vendor’s update process.
- If you cannot patch yet, researchers list two interim options: -XX:-UseBASE64Intrinsics on any architecture, or -XX:UseAVX=2 on x86-64 only, because ARM JVMs will not start with it. Both need a restart.
- Prioritize internet-facing identity, build, and artifact systems. Then internal services, then clients that connect to external servers.
- Review unexplained JVM crashes (hs_err_pid files) and bursts of Base64 decoding errors in application logs. Neither proves compromise and their absence proves nothing.
Be careful with advice going around
One widely shared flag stops the JVM from starting if used alone, and a “fixed in 17.0.11 / 21.0.3” claim refers to an unrelated bug. Fake proofs of concept are likely, and some articles are AI-generated or AI-rewritten, so check claims against Calif, Oracle, and OpenJDK directly.
How Black Duck helps
Because the flaw sits in the Java runtime rather than in an application library, a manifest-based dependency scan can miss it; finding it is an inventory problem.
Black Duck SCA container scanning analyzes each layer of an image using binary analysis and can identify the JDK it contains, including runtimes bundled inside applications. Black Duck Binary Analysis does the same for appliances, vendor software, and other compiled artifacts.
Search your bill of materials for CVE-2026-114938 (BDSA-2026-40579) for a list of every affected project version, and add a policy that flags affected JDK builds. Hardware, JVM flags, and reachable inputs still need checks on the hosts themselves.
We will update this post as vendors ship fixes and more research is published.
For a similar runtime flaw, see how teams used Black Duck SCA to respond to PHP2Shell.