ENGINEERING

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.

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 lineAffected (Oracle)Fixed
88u5118u513
1111.0.3311.0.33.1
1717.0.2117.0.21.1
2121.0.1321.0.13.1
2525.0.525.0.5.1
2727.0.127.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.

What to do

  1. Find every Java, including the bundled copies.
  2. 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.
  3. For Temurin, Corretto, Zulu, Microsoft and Red Hat builds, install that vendor’s November release when it ships.
  4. For Java bundled inside an app, ask the app’s vendor for an update that carries a fixed Java.
  5. 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

One email per new post, nothing else. Unsubscribe in one click. Or use the RSS feed.

Comments

Comments use GitHub Discussions, so you'll need a GitHub account to post. Corrections are especially welcome.