Datadog Security Labs reports Java4Shell remote code flaw in OpenJDK
A flaw nicknamed Java4Shell could let an outsider run code on systems using recent Java. Details are preliminary and vendor confirmation is still pending.
Written by the SecurityTabs AI newsroom from the original posts by Datadog Security Labs, Rapid7 Blog; vulnerability scores come from NVD, FIRST and CISA, not the AI.
Datadog Security Labs has published research on a remote code execution vulnerability in OpenJDK, which it calls Java4Shell and tracks as CVE-2026-114938. [1]
Rapid7 says that on November 17, 2026, public reports described the issue as memory corruption affecting Java 17 and newer, exploitable by a remote attacker with no login. Rapid7 notes a reported severity of Critical, with a CVSSv4 score of 9.2. [2]
Rapid7 stresses that these details are preliminary and still await confirmation in Oracle or OpenJDK advisories. It says it is monitoring the situation and will update its post. CISA has not listed the flaw in its Known Exploited Vulnerabilities catalogue. [2]
Vulnerabilities
Explained
The technology and terms in this story. Learn more
- AttackRemote code execution · RCEA flaw that lets an attacker run their own code on someone else's machine over the network.
- WeaknessMemory corruptionBugs that let a program write where it shouldn't in memory, often leading to code execution.
- ConceptKEV · Known Exploited Vulnerabilities catalogCISA's list of vulnerabilities with evidence of real-world exploitation.
- ConceptCVE · Common Vulnerabilities and ExposuresThe public ID system for vulnerabilities, such as CVE-2026-12345, so everyone means the same bug.
Original sources
- [1]Datadog Security Labs
Java4Shell: Remote Code Execution in OpenJDK (CVE-2026-114938) - [2]Rapid7 Blog
CVE-2026-114938: Reported Critical Pre-authentication Remote Code Execution in Java 17