Security advisory
Java4Shell: find and update every copy of Java 17, 21, 25, and 27
On November 17, 2026, CISA urged organizations to patch a Java vulnerability right away. It is called Java4Shell (CVE-2026-114938). Crafted Base64 data can crash Java and could let an attacker run code on a server without signing in. Oracle has released fixed versions. Many products include their own copy of Java, so check those too.
Published · Last updated
Ask about this advisory- Identifier
- CVE-2026-114938
- Severity
- High (CVSS 8.1, rated by Oracle). CISA calls it critical.
- Affected
- Java 17, 21, 25, and 27 on x86-64 systems
- Status
- Fixes available. Not in the CISA Known Exploited Vulnerabilities (KEV) catalog when we checked on November 18, 2026.
Affected and fixed versions
| Product | Fixed in | Affected |
|---|---|---|
| Java 17 | 17.0.21.1 | Before 17.0.21.1 |
| Java 21 | 21.0.13.1 | Before 21.0.13.1 |
| Java 25 | 25.0.5.1 | Before 25.0.5.1 |
| Java 27 | 27.0.1.1 | Before 27.0.1.1 |
The fixed versions are Oracle JDK release numbers. Other Java vendors use their own numbers. Java 8 and Java 11 are not affected, except Oracle's 8u511b33-perf build.
Who is affected
- Servers and applications that run Java 17, 21, 25, or 27 with the HotSpot Java virtual machine (JVM) on x86-64 processors (Intel and AMD). This includes Oracle JDK and most OpenJDK builds.
- Products that include their own copy of Java, such as business applications, servers, and appliances. CISA warns that these copies may not appear in your software inventory.
- Container images that include Java.
- Oracle GraalVM for JDK 17 and 21, and Oracle GraalVM Enterprise Edition 21.3.
The risk is highest for internet-facing services that accept data without a sign-in, such as web services.
How to check your systems
Check every server. Include the copies of Java inside other products and containers.
- Show the version of the default Java on a server.
java -version - On Linux, find all other copies of Java. Then run each result with -version.
find / -type f -path '*/bin/java' 2>/dev/null - On Windows, find every java.exe file. Then run each result with -version.
where /r C:\ java.exe - Check the Java inside a container image. Replace IMAGE with the name of the image.
docker run --rm --entrypoint java IMAGE -version - For products that include Java, ask the vendor whether the product is affected and when a fix will be ready.
The output shows the version number, for example 21.0.13. Compare it with the table of fixed versions.
How to fix it
- Update Java on internet-facing systems first. For Oracle JDK, install 17.0.21.1, 21.0.13.1, 25.0.5.1, or 27.0.1.1, or a later version.
- If your Java comes from another vendor, install the build that the vendor says fixes CVE-2026-114938. Examples are Eclipse Temurin, Amazon Corretto, Azul Zulu, Microsoft, and Red Hat. On November 18, 2026, Eclipse Temurin had not yet published a fixed build.
- Restart every Java application after the update. A running application keeps using the old version until it restarts.
- Rebuild your container images from an updated base image, and deploy them again.
- For products that include Java, install the vendor's update as soon as it is available.
- Update Java 8 and Java 11 too. Oracle's November 2026 update also fixes other vulnerabilities in them.
If you cannot update today
CISA lists these temporary measures. They reduce the risk, but they do not fix the vulnerability.
- Check Base64 data where it enters your applications, and reject input that is too large.
- Limit who can reach services that accept data without a sign-in.
- Watch for unexpected Java crashes, copies of Java that you did not install, and unusual Java processes.
Signs of an attack
An attack can crash Java. A crash usually leaves a file whose name starts with hs_err_pid. Look for recent crash files on your servers.
- On Linux, list the crash files from the last 7 days.
find / -name 'hs_err_pid*.log' -mtime -7 2>/dev/null
A crash does not prove an attack. If you find recent crash files on an internet-facing server, have a security engineer check that server.
Sources
Need help with Java4Shell?
We can help you find every copy of Java in your systems, including copies inside other products and containers. We tell you which ones to update first, and we can check the updates afterward. Send us a question below. We reply within two business days.
You can also email info@maxtsogt.com
This advisory summarizes the public sources listed on this page, as of the date of the last update. It is general information. For advice about your own systems, ask us.