Java’s November 2026 update and Java4Shell (CVE-2026-114938): find every Java on your fleet, the bundled ones too
Update, November 18
Calif published its write-up after Oracle’s patch, and OpenJDK’s November 17 advisory lists CVE-2026-114938 in the HotSpot compiler at 8.1 under CVSS 3.1. Calif’s 9.2 is under CVSS 4.0.
- What it is. On x86-64, OpenJDK decodes Base64 with hand-written AVX-512 VBMI assembly. Malformed input makes it write 62 bytes past the end of the output array before Java rejects the input. Calif turned that into memory leaks and remote code execution.
- Which Java. OpenJDK 17.0.6 and later, on the 17, 21, 25 and 27 lines. OpenJDK’s advisory doesn’t list 8 or 11 for this CVE. Oracle’s list adds one Java 8 build, 8u511b33-perf. Temurin, Corretto, Zulu, Liberica, SapMachine, the Microsoft and Red Hat builds and GraalVM for JDK are built from OpenJDK, so they’re affected too.
- Which computers. Only x86-64 CPUs with AVX-512 VBMI. Calif lists Intel Xeon Ice Lake, Sapphire Rapids, Emerald Rapids and Granite Rapids, and AMD EPYC and Ryzen on Zen 4 or newer. ARM64 isn’t affected.
- Which apps. Calif showed pre-auth RCE in Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate in their default configs, and post-auth RCE in Kafka, Solr, Elasticsearch, Gerrit and Spinnaker. A Java program that connects to a malicious TLS server can be compromised too. Calif is holding back the app-specific exploits for now.
Oracle’s fixed builds are in the table below: 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1. Amazon released Corretto 17.0.21.1.2 and 21.0.13.1.2 on November 17, though their release notes don’t list CVEs. Early on November 18, Eclipse Temurin’s newest builds were still the October ones (17.0.21+9, 21.0.13+9, 25.0.5+8).
Until you can update, Calif says either of these JVM flags stops it:
-XX:-UseBASE64Intrinsics
-XX:UseAVX=2
Use them on x86-64 only. OpenJDK on ARM doesn’t recognize them and won’t start.
On Linux, Calif’s command checks the CPU. It’s exposed only when all four flags print:
grep -m1 '^flags' /proc/cpuinfo | tr ' ' '\n' | grep -E '^(avx512f|avx512bw|avx512vbmi|bmi2)$'
My lab VMs run on a Ryzen 5 2600 (Zen+). The command printed only bmi2 there, so I couldn’t reproduce Java4Shell in the lab.
The original post, November 17
Oracle released its November Java update on November 17, 2026. Its advance notice lists 11 Java SE vulnerabilities, all exploitable over the network without credentials, with a top CVSS 3.1 score of 8.1. Oracle hasn’t published their CVE numbers or the affected components yet.
Separately, the security firm Calif reported Java4Shell (CVE-2026-114938), a pre-auth remote code execution flaw it says affects OpenJDK 17.0.6 and later, scored 9.2 under CVSS 4.0 (The Hacker News). The CVE record is still reserved, watchTowr called the details unconfirmed, and nobody has said yet whether it’s one of Oracle’s 11. Calif says it will publish the technical details after Oracle’s patch. As of this afternoon there are no reports of exploitation.
The fixed builds
Oracle says to stop using the current builds of every supported line and move to these:
| Java line | Affected (Oracle) | Fixed |
|---|---|---|
| 8 | 8u511 | 8u513 |
| 11 | 11.0.33 | 11.0.33.1 |
| 17 | 17.0.21 | 17.0.21.1 |
| 21 | 21.0.13 | 21.0.13.1 |
| 25 | 25.0.5 | 25.0.5.1 |
| 27 | 27.0.1 | 27.0.1.1 |
Oracle’s notice also lists GraalVM for JDK 17.0.21 and 21.0.13, GraalVM Enterprise 21.3.20.0.3 and JavaFX 21.0.13, 25.0.5 and 27.0.1.
Other OpenJDK builds (Eclipse Temurin, Amazon Corretto, Azul Zulu, the Microsoft Build of OpenJDK, Red Hat’s) ship their fixes on their own schedule and with their own build numbers. When I downloaded Temurin 17 for my lab test this afternoon, the newest build was still 17.0.21+9 from October 20.
The Java your inventory doesn’t list
Plenty of applications ship their own Java in a jre folder inside the app and never register it with Windows. Add/Remove Programs doesn’t list it, and that list is where most software inventory and CVE matching start. A shortcut that starts an app like that looks something like this:
C:\SomeApp\jre8_191\bin\javaw.exe -classpath app.jar ...
A folder named jre8_191 is Java 8 update 191, from October 2018. Updating Java on the machine leaves it alone. Only the app’s vendor can update it, or you can replace the folder yourself if the vendor supports that.
Check one computer
In PowerShell as an administrator. It finds every java.exe on the C: drive and prints the version and vendor from the release file next to it:
cmd /c "dir C:\java.exe /s /b 2>nul" | Where-Object { $_ -match '\\bin\\java\.exe$' } | ForEach-Object {
$javaHome = Split-Path (Split-Path $_)
$rel = Join-Path $javaHome 'release'
$v = if (Test-Path $rel) { (Select-String -Path $rel -Pattern '^(JAVA_VERSION|IMPLEMENTOR)=').Line -join ' ' }
[pscustomobject]@{ Home = $javaHome; Release = $v }
} | Format-Table -AutoSize -Wrap
Use dir /s for the search. This command took 40 seconds on my lab VM. Walking a whole drive with Get-ChildItem -Recurse has taken more than 25 minutes on another one.
JAVA_VERSION="1.8.0_191" is Java 8 update 191. IMPLEMENTOR is the vendor whose fix you need.
What I found in the lab
I ran the RFF check as SYSTEM on a Windows Server 2025 lab VM with one real Java, Temurin 17.0.21+9, and stand-ins for the Oracle cases: a renamed system exe as java.exe with a release file for each version.
- An Oracle 8u191 bundled inside an app folder and an Oracle 17.0.21 came back as needing the update. Oracle 17.0.21.1 and 21.0.13.1 came back fixed.
- An Oracle Java 16 came back as end of life. Oracle’s notice has no fix for 16, or for any line other than 8, 11, 17, 21, 25 and 27.
- Temurin 17.0.21 came back as “compare with Eclipse Adoptium’s November release”, with a note that 17.0.6 and later is the range named in the Java4Shell reports.
- My first version reported the run as fine even when it found vulnerable Java, so RFF’s job page would have said “No issue found”. A library test caught it, and I fixed the same mistake in another check that was already live.
What to do
- Find every Java, including the bundled copies.
- Update Oracle builds to the fixed build for their line, and move anything on an unsupported line (9, 10, 12 to 16, 18 to 20, 22 to 24, 26) to a supported one.
- For Temurin, Corretto, Zulu, Microsoft and Red Hat builds, install that vendor’s November release when it ships.
- For Java bundled inside an app, ask the app’s vendor for an update that carries a fixed Java.
- Start with anything internet-facing that runs on Java.
Doing it with RFF
The RFF Script Library has a new Windows entry, “Java (November 2026 update, Java4Shell) - Find Every Java and Its Version”. It walks every fixed drive for java.exe as SYSTEM, so it finds the bundled copies too, reads each one’s version and vendor, and reports each as needing the update, end of life, check with the vendor, or fixed, and whether it’s running right now. I tested it on the lab VM above, and the walk took about two and a half minutes.
RFF is free for your first 100 endpoints: getrff.com.
Sources
- Calif, Java4Shell: the Base64 bug, affected Java and CPUs, the apps it showed RCE in, the two JVM flags and the Linux CPU check
- OpenJDK Vulnerability Advisory, November 17: CVE-2026-114938 in the HotSpot compiler, CVSS 8.1, the 17, 21, 25 and 27 lines
- Amazon Corretto 17 and Corretto 21 releases, November 17
- Eclipse Adoptium API: Temurin’s newest builds, checked early on November 18
- Oracle Critical Patch Update notice, November 2026: 11 Java SE flaws, CVSS 8.1, affected builds, GraalVM and JavaFX
- The Hacker News, November 17: the planned fixed builds from ops.java, Calif’s Java4Shell report, watchTowr’s caution, the reserved CVE record
- Oracle Java SE release notes: the update guidance
- CVE-2026-114938: the CVE record, reserved on November 17 and published since
Comments
Comments use GitHub Discussions, so you'll need a GitHub account to post. Corrections are especially welcome.