CyberSIXT reportingUpdated
Java4Shell (Java2Shell): Java flaw CVE-2026-114938, what is known
Part of the CVE-2026-114938 story · since 17 Nov
- Tue 17 Nov, 11:10 UTC. cybersixt, first report. Java4Shell (Java2Shell): Java flaw CVE-2026-114938, what is known. This article, 1st of 1.
Updated 17 November, 17:26 UTC. Calif says it found and reported the flaw, which it calls Java4Shell, and will publish details after Oracle's patch; Oligo calls it memory corruption in the Java runtime.
Calif, a security research firm, says it discovered and reported the Java flaw tracked as CVE-2026-114938, which it calls Java4Shell, and that it will publish technical details by 13:00 Pacific time (21:00 UTC) on Tuesday 17 November, after Oracle releases a patch. "Since the vulnerability has leaked," Calif said on X at 16:11 UTC, explaining why it was naming itself before the fix. Until then the flaw had circulated only as unconfirmed reports of an unauthenticated remote code execution bug in OpenJDK 17.0.6 and later, which watchTowr, an attack surface management firm, flagged on Tuesday morning. Some early posts and reports call the same flaw Java2Shell.
The patch Calif is waiting for is Oracle's out-of-cycle Critical Security Patch Update, due on Tuesday with 652 new security patches, 11 of them for Java SE. Oracle's pre-release announcement says all 11 Java flaws "may be remotely exploitable without authentication", meaning they can be attacked over a network without user credentials. At 17:25 UTC the page still showed only that announcement, with no CVE numbers, so Oracle has not yet confirmed that Java4Shell is among its fixes. The CVE record had not been published either.
What is known about Java4Shell
Oligo Security, a runtime security company, describes Java4Shell on its website as "a critical memory corruption vulnerability in Java's core" that sits in the Java runtime itself rather than in a third-party library and exposes "Java applications running on affected x86 systems". It says its product blocks "attempts to trigger the vulnerable decoding path".
Waves, a blockchain project whose nodes run on Java, told its node operators on X that the flaw affects Java applications on x86 servers with the AVX-512 instruction set and that ARM servers are not affected. It advised them to start Java with the option -XX:-UseBASE64Intrinsics, which switches off the Java virtual machine's processor-optimised Base64 routines, until they can install their vendor's November build, and said there were no known exploits so far. Neither Oracle nor the OpenJDK project has published those details or that workaround, and none of these sources has said what kind of input an attacker would have to send to reach the flaw.
Oracle's Java update
The Java versions Oracle lists are Java SE 8u511, 11.0.33, 17.0.21, 21.0.13, 25.0.5 and 27.0.1, GraalVM for JDK 17.0.21 and 21.0.13, GraalVM Enterprise Edition 21.3.20.0.3 and JavaFX 21.0.13, 25.0.5 and 27.0.1. The highest CVSS 3.1 score among the Java flaws is 8.1. The rest of the update is heavier: Oracle Database Server gets seven patches with a highest score of 9.9, Oracle APEX and Oracle REST Data Services top out at 9.8, and Oracle Communications gets 28. The OpenJDK Vulnerability Group, which announces fixes for the open-source Java builds that most Linux distributions and other vendors ship, had not posted an advisory for 17 November.
What to do
Find every place Java runs, including runtimes bundled inside other applications and container images, so the fixed builds can go in as soon as they appear. Oracle's builds arrive with its update, while OpenJDK distributions such as those from Linux vendors ship their own fixed builds on their own timelines. Turning off Base64 intrinsics is a stopgap that only some third parties recommend; anyone who uses it should confirm the setting took effect and remove it once patched.
What is not known
Oracle has not named the Java CVEs or said which component Java4Shell is in, and Calif has not yet published its findings. Calif has not said how the vulnerability leaked or how widely the details have spread, and no one has reported exploitation.
How the story developed
1 article from 1 outlet since 17 Nov. Still developing; the latest report was 8 hours ago. This was the first report.
- Tue 17 Nov, 11:10 UTC. cybersixt, first report. Java4Shell (Java2Shell): Java flaw CVE-2026-114938, what is known. This article, 1st of 1.
- CVE not in KEV
- No CVE
- Larger: an outlet’s first report
- Coverage over time
Show all 1 articles as a listHide the list
- Tue 17 NovDay 01
- Java4Shell (Java2Shell): Java flaw CVE-2026-114938, what is known11:10 · cybersixt · First report · This article, 1st of 1
Sources
- Calif on X: Calif discovered and reported Java4ShellPrimary sourcex.com
- watchTowr on X: unconfirmed reports of a Java RCE, CVE-2026-114938Primary sourcex.com
- Oracle: Critical Security Patch Update pre-release announcement, November 2026Primary sourceoracle.com
- CVE.org: CVE-2026-114938cve.org
- Oligo Security: Java4ShellReportoligo.security
- Waves on X: Java4Shell note for node operatorsx.com
- OpenJDK Vulnerability Group advisoriesPrimary sourceopenjdk.org
More reporting
- Equinor cyber attack: IT systems hit, production unaffected17 Nov
- DonorPerfect outage: security incident locks out nonprofits17 Nov
- EU sanctions NoName057(16) hackers over DDoS attacks on Europe17 Nov
- California sues OpenAI over AI agent attack on Hugging Face17 Nov
- Contabo breach: VNC passwords reset on every customer server17 Nov
Written by CyberSIXT from the sources above.How we reportCorrectionsRSS