Java4Shell (CVE-2026-114938): out-of-bounds write in the OpenJDK Base64 decoder intrinsic
Identifiers: CVE-2026-114938
- Published
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
Summary
Oracle's 17 November 2026 update fixes CVE-2026-114938, a Compiler component flaw that Datadog Security Labs calls Java4Shell. The optimized Base64 decoder can write out of bounds when a vulnerable runtime decodes attacker-controlled data on an x86-64 CPU that takes the AVX-512 VBMI path. Oracle Java SE 17, 21, 25 and 27 have fixed releases. Oracle Java SE 8u511b33-perf and Oracle GraalVM are listed as affected without an independently verified CVE-specific fixed build.
Impact
Oracle rates the flaw CVSS 3.1 8.1 High: reachable over the network with no privileges or user interaction, but with high attack complexity, and a successful attack can take over the runtime. Datadog reports that a crash, in other words denial of service, is the easier outcome in testing, while code execution needs work tailored to the specific application and JVM. Datadog states that there is no universal exploit that works against any Java application.
Who is affected
Oracle's CNA entry lists exact affected builds: Java SE 8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3 and 27.0.1.0.3; GraalVM for JDK 17.0.21.0.3 and 21.0.13.0.3; GraalVM Enterprise Edition 21.3.20.0.3. Datadog describes a wider range of OpenJDK builds, for example Java 17 from 17.0.6 until releases before 17.0.21.1, so the two sources differ in both format and scope. Exploitation also requires an x86-64 CPU with AVX-512 VBMI and a code path where attacker-controlled Base64 reaches the affected decoder; native ARM64 JVMs do not execute this path according to Datadog. Ordinary Java 8 and Java 11 builds are not listed for this CVE, but the 8-perf listing means Java 8 is not a blanket all-clear, and other fixes in the November update are separate.
Products and versions
| Products and versions | Affected | Fixed |
|---|---|---|
| Oracle Java SE 17 | Oracle CNA affected build 17.0.21.0.3; Datadog describes 17.0.6 through releases before 17.0.21.1 | 17.0.21.1+4 |
| Oracle Java SE 21 | Oracle CNA affected build 21.0.13.0.3; Datadog describes releases before 21.0.13.1 | 21.0.13.1+4 |
| Oracle Java SE 25 | Oracle CNA affected build 25.0.5.0.3; Datadog describes releases before 25.0.5.1 | 25.0.5.1+4 |
| Oracle Java SE 27 | Oracle CNA affected build 27.0.1.0.3; Datadog describes releases before 27.0.1.1 | 27.0.1.1+4 |
| Oracle Java SE 8-perf | Oracle CNA lists 8u511b33-perf; do not infer all Java 8 builds are affected or unaffected | CVE-specific containing build not independently verified |
| Oracle GraalVM | Oracle GraalVM for JDK 17.0.21.0.3 and 21.0.13.0.3; GraalVM Enterprise Edition 21.3.20.0.3 | Vendor-specific containing builds not independently verified |
Exploitation evidence
Exploitation not established. Not established. The Oracle CNA entry and Datadog's research describe a difficult-to-exploit flaw and a research proof of concept; neither reports real-world attacks. The CISA Known Exploited Vulnerabilities catalog of 17 November 2026 does not list CVE-2026-114938, which is not proof of absence. Crashes observed during testing are not attacks.
Actions
- Inventory every service, job and container image that includes a Java runtime, recording vendor, full build string and whether it accepts data from the internet.
- Note the CPU type of each host and whether the application decodes untrusted Base64 input; prioritize internet-exposed x86-64 paths.
- For Oracle Java SE 17, 21, 25 and 27, move to the fixed releases 17.0.21.1+4, 21.0.13.1+4, 25.0.5.1+4 and 27.0.1.1+4 as confirmed in the Oracle release notes.
- For other vendors, distributions and bundled runtimes, use that vendor's own fixed build; backported distribution packages outrank raw upstream version comparisons.
- Where a provider manages the runtime, ask the provider which build is deployed.
- Take a tested backup, confirm application compatibility, update, rebuild and redeploy container images, and restart affected Java processes.
- Verify the running JVM itself, not the java on your shell path or the installed package list; where jcmd is available, run jcmd <PID> VM.version against the process.
- If updating is delayed, the service owner may compatibility-test one of the Datadog-tested startup options, -XX:-UseBASE64Intrinsics (narrower) or, on x86-64 only, -XX:UseAVX=2, restart the service, then confirm the effective flag with jcmd <PID> VM.flags -all. Native ARM64 JVMs do not recognize UseAVX and can fail to start if it is added to shared settings. This is a temporary measure, not a vendor patch.
Unknowns
- CVE-specific fixed builds for Oracle Java SE 8u511b33-perf and Oracle GraalVM were not independently verified at the time of checking.
- Fixed build numbers for non-Oracle OpenJDK vendors and distribution packages must be confirmed from each vendor.
- Whether a given deployment decodes attacker-controlled Base64 on an affected CPU path depends on the application and host and cannot be stated generally.
- Datadog's Basic/URL versus MIME decoder observations were made on the tested 17.0.6 build and are not confirmed for other versions.
Sources
- Oracle https://www.oracle.com/security-alerts/cspunov2026.html
- Oracle / CVE CNA https://cveawg.mitre.org/api/cve/CVE-2026-114938
- Oracle https://www.oracle.com/java/technologies/javase/17-0-21-1-relnotes.html
- Oracle https://www.oracle.com/java/technologies/javase/21-0-13-1-relnotes.html
- Oracle https://www.oracle.com/java/technologies/javase/25-0-5-1-relnotes.html
- Oracle https://www.oracle.com/java/technologies/javase/27-0-1-1-relnotes.html
- Datadog Security Labs https://securitylabs.datadoghq.com/articles/java4shell-remote-code-execution-in-openjdk-cve-2026-114938/
- CISA / cisagov KEV catalog https://raw.githubusercontent.com/cisagov/kev-data/main/known_exploited_vulnerabilities.json
Change history
- — Published: 18 November 2026: record created after Oracle's 17 November 2026 update, the CNA entry published 17 November 21:32 UTC and updated 18 November 02:06 UTC, and Datadog Security Labs research dated 17 November. Earlier third-party summaries that described the CVE as unpublished or its conditions as unknown predate these primary sources, which now document the exact affected builds and the CPU and decoder prerequisites. Oracle's CNA entry lists Java SE 8u511b33-perf as affected, so a flat statement that Java 8 is unaffected does not hold. Ordinary Java 8 and Java 11 builds are not listed for this CVE.