CVE-2026-114938: Java4Shell
Java4Shell (CVE-2026-114938) is a reported memory-corruption vulnerability in OpenJDK's AVX-512-accelerated Base64 decoder. Preliminary technical accounts describe an integer underflow during final padding handling that causes a heap-based buffer overflow. A specially crafted 65-byte input reportedly produces a 62-byte overflow capable of corrupting adjacent Java objects. The reported affected range begins with OpenJDK 17.0.6 and includes subsequent Java 17 updates, but precise version and distribution applicability remain unconfirmed. Applications exposing the affected decoding path to unauthenticated input could potentially permit remote code execution. As of November 17, 2026, vendor confirmation of the CVE-specific technical details and affected range is unavailable.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation could potentially execute attacker-controlled code with the privileges of the affected Java process, compromising application data and functionality. Heap corruption could also crash the JVM and disrupt services. Reliable code execution and exploitation in the wild have not been established.
Mitigation
If you can’t patch tonight, do this now.
Restrict unnecessary network exposure and access to services processing untrusted Base64 input. Potential temporary workarounds include disabling Base64 intrinsics with '-XX:+UnlockDiagnosticVMOptions -XX:-UseBASE64Intrinsics' or limiting AVX use with '-XX:UseAVX=2'. These measures are not confirmed workarounds and require vendor guidance and staging validation for applicability, effectiveness, and performance impact. Upstream rejection of malformed or oversized input may reduce exposure, but application-level validation must not be assumed to prevent vulnerable runtime processing.
Remediation
Patch, then assume compromise.
Install a runtime update explicitly confirmed by the relevant JDK vendor to address CVE-2026-114938. Update application-bundled runtimes and container base images, restart or redeploy affected services, and verify the builds used by running JVMs. No CVE-specific fixed build is confirmed; do not assume Oracle's November 2026 updates address this vulnerability without an explicit advisory mapping. Application dependency or logging configuration changes do not repair the reported runtime flaw.
Exploits
No validated public exploits yet. Hidden: 2 not yet analyzed, such as Exploit-DB entries.
References
Frequently asked questions
- Is CVE-2026-114938 exploited in the wild?
- As of Nov 17, 2026, Mallory has no reports of CVE-2026-114938 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-114938?
- As of Nov 17, 2026, Mallory has not confirmed a public exploit for CVE-2026-114938. 2 candidate exploit records are not yet analyzed.
- Is there a patch for CVE-2026-114938?
- Install a runtime update explicitly confirmed by the relevant JDK vendor to address CVE-2026-114938. Update application-bundled runtimes and container base images, restart or redeploy affected services, and verify the builds used by running JVMs.
Recent activity
102 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.