Aikido Says Deep Review Found Java4Shell in Original OpenJDK Pull Request

Summary
Aikido says its Deep Review tool identified Java4Shell in a reconstructed 2021 OpenJDK pull request, explaining an AVX-512 Base64 decoder underflow that can corrupt heap memory and suggesting the upstream mitigation.
Key points
- Aikido reports that Deep Review identified Java4Shell (CVE-2026-114938) in a reconstruction of the 2021 OpenJDK pull request that introduced the vulnerable code.
- The article says the memory-corruption flaw affects the hardware-accelerated Base64 decoder on x86-64 CPUs with AVX-512 VBMI; ARM systems are not affected.
- A non-MIME input ending in invalid padding can trigger an integer underflow, produce an incorrect output mask, and cause a write beyond the allocated destination buffer.
- Aikido says Deep Review recommended checking for fewer than four remaining input bytes and falling back to the safer decoder, matching the upstream fix in effect.
- The tool also reportedly identified an oversized vectorized write and incomplete invalid-character validation; the article says both defects were later corrected upstream.
- The article lists Oracle fixed releases as 17.0.21.1, 21.0.13.1, 25.0.5.1, and 27.0.1.1, and says Aikido offers patched Temurin 17 and 21 images.
Article Details
- Attack Vectors
- A non-MIME Base64 input ending in invalid padding can trigger integer underflow in OpenJDK's AVX-512 decoding path, causing an out-of-bounds write and Java heap memory corruption. The vulnerable path requires an x86-64 CPU supporting AVX-512 VBMI; the article says ARM systems are unaffected.
- The original implementation also had an oversized vectorized write that could exceed a destination region intended for 48 decoded bytes, and an incomplete invalid-character check that could allow certain invalid characters to pass validation.
- Defensive Notes
- Upgrade to a fixed Java release: Oracle lists 17.0.21.1, 21.0.13.1, 25.0.5.1, and 27.0.1.1.
- If an upgrade is not yet possible, the article says Aikido offers patched Java images for Temurin 17 and 21 in JDK and JRE variants.
- Check for potentially affected runtimes through the Aikido dashboard's “Am I affected?” check or Attack Surface.
- For the decoder edge case, the suggested mitigation is to check whether the remaining input is shorter than four bytes and fall back to the safer decoding implementation.
CVE
Vendors
AikidoIf you can’t upgrade yet, Aikido has patched Java images for Temurin 17 and 21, in both JDK and JRE variants. To check your exposure, click “Am I affected?” on the Aikido dashboard, or onboard to Attack Surface to findOracleIf you're affected, upgrade to a patched Java version. Oracle's fixed releases are 17.0.21.1, 21.0.13.1, 25.0.5.1, and 27.0.1.1.
Products
Eclipse TemurinIf you can’t upgrade yet, Aikido has patched Java images for Temurin 17 and 21, in both JDK and JRE variants. To check your exposure, click “Am I affected?” on the Aikido dashboard, or onboard to Attack Surface to findJavaIf you're affected, upgrade to a patched Java version. Oracle's fixed releases are 17.0.21.1, 21.0.13.1, 25.0.5.1, and 27.0.1.1.OpenJDKJava4Shell (CVE-2026-114938) is a critical memory corruption vulnerability in OpenJDK's Base64 decoder that can lead to remote code execution. The vulnerable code only runs on x86-64 CPUs that support AVX-512 VBMI, so
Tools
AI Code AnalysisFor code that merged years ago, like the 2021 change behind Java4Shell, AI Code Analysis reasons across your whole codebase to find vulnerabilities in what you’ve already shipped. Deep Review then checks each new changeAikido MCP serverasking for a fix, Aikido opens a new pull request with that fix built on top of yours. With the Aikido MCP server, your coding agent can also run Deep Review on your local branch before you open a pull request.Deep ReviewThen we ran Aikido Deep Review against the reconstructed pull request, which you can explore on GitHub along with Deep Review’s findings. We replaced the original authors’ and reviewers’ names with placeholders, and the
