Oracle rates its Compiler component flaw CVSS 3.1 8.1 High. Calif assigns CVSS 4.0 9.2 Critical to its research finding.Oracle says an unauthenticated network attacker may compromise affected Oracle Java SE and GraalVM installations when supplied data reaches the component's APIs. The Canadian Centre for Cyber Security says vulnerable processing also requires x86-64 hardware with AVX-512 VBMI. Those conditions matter when assessing individual services.
What it allows
How Does CVE-2026-114938 Work?
Calif traces the defect to the x86-64 HotSpot Base64 intrinsic, where a malformed padded tail produces the wrong write mask. The optimized routine can write beyond the allocated result array before Java rejects the input. Neighboring heap objects may already be corrupted.
The researcher reports turning this corruption into memory disclosure and remote code execution in tested Java applications. That is a research demonstration, not evidence that every Java service is exploitable. Oracle describes the flaw as difficult to exploit and requires supplied data to reach the affected APIs.
For prioritization across exposed services, use the Vulnerability Intelligence platform alongside runtime and hardware inventory. The vulnerability intelligence glossary explains how exposure and impact inform the decision.
What Is Known About Exploitation?
The Canadian Cyber Centre said on 17 November 2026 that it was unaware of active exploitation at that time. Calif's public demonstration proves a research capability, but does not establish attacks against other organizations. Treat incident claims separately from the technical proof.
From 20 August through 18 November 2026, Brandefense Blackhole counted 14 dark-chat posts matching CVE-2026-114938. This is a post count, not 14 incidents or 14 distinct actors. A separate GitHub search at 23:59 UTC on 17 November found eight public repositories named for the CVE; repository descriptions include scanners, laboratory reproductions and other research material. These counts may overlap in subject matter and do not establish active exploitation.
Who is affected
Which Java4Shell Versions and Configurations Are Affected?
Oracle lists 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. It also lists GraalVM for JDK 17.0.21.0.3 and 21.0.13.0.3, plus GraalVM Enterprise Edition 21.3.20.0.3. These are affected versions in Oracle's CVE-specific matrix, not fixed-version thresholds.
The Canadian Cyber Centre says the relevant processor must support AVX-512 VBMI, while the application must pass attacker-controlled Base64 data to the affected Java path. A bundled runtime in an appliance or container deserves the same inventory check. Do not infer that every installation of another Java distribution shares Oracle's exact version list.
Record the runtime vendor, complete build string, application and processor features for each deployment. Compare the result with that vendor's current advisory and patch guidance. The patch management process helps document the installed and replacement builds.
Timeline
-
2026-11-17
Oracle published CVE-2026-114938 and included the affected Oracle products in its November Critical Security Patch Update.
-
2026-11-17
Calif published its Java4Shell research and reported application-level remote code execution demonstrations.
-
2026-11-17
The Canadian Centre for Cyber Security issued alert AL26-029 with hardware conditions and defensive actions.
What to do
-
Inventory Java runtimes and hardware
Identify Java processes in services, appliances and containers. Record vendor, full build version and processor support for AVX-512 VBMI, including behind public entry points.
-
Prioritize reachable Base64 processing
Trace whether untrusted input reaches the affected Base64 APIs in Internet-facing or otherwise exposed applications. Prioritize those deployments while reviewing all affected runtimes.
-
Apply vendor updates
Apply the applicable Oracle security patch or another runtime vendor's fixed release. Oracle's public matrix lists affected builds but does not give one comparable fixed threshold for every branch.
-
Verify the running build
Restart affected processes after updating. Record each process's actual Java vendor and full build string, then compare it with that vendor's fixed-release guidance.
-
Investigate suspicious activity
Review web, application, authentication and endpoint logs for anomalous activity around exposed Java services. The Canadian Cyber Centre recommends this review; individual anomalies do not prove exploitation of this CVE.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-114938 in Brandefense Atlas
The Atlas record of CVE-2026-114938: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
What is Java4Shell?
Java4Shell is Calif's name for CVE-2026-114938, a heap overflow in an optimized Java Base64 decoding path. Oracle identifies affected Java SE and GraalVM builds.
Does every Java server have the same exposure?
No. The Canadian Cyber Centre names AVX-512 VBMI hardware, and Oracle requires supplied data to reach the affected APIs. Check each runtime and application path.
Has Java4Shell been used in attacks?
Calif demonstrated remote code execution in research tests. The Canadian Cyber Centre said on 17 November 2026 that it was unaware of active exploitation at that time.
Which version should administrators install?
Use the current fixed release or patch identified by the installed runtime's vendor. Oracle's public CVE matrix identifies affected builds without a universal fixed-version threshold.
Sources
- CVE-2026-114938 RecordOracle via CVE Program
- November 2026 Critical Security Patch UpdateOracle
- Java4Shell ResearchCalif
- AL26-029 Oracle Java AlertCanadian Centre for Cyber Security