Tanium is aware of and closely tracking CVE-2026-114938, nicknamed "Java4Shell," which leaked ahead of its coordinated disclosure today, November 17, 2026. Here are some tips on what you can do right now.
What's reported so far
The reports describe a critical flaw, and several key facts are still unconfirmed.
These details are preliminary and may change.
What Tanium is tracking, and what Tanium customers can do now
Tanium is tracking this closely. Details have been released and Tanium is actively working to update the Tanium Vulnerability Library (TVL) with applicable definitions and provide a Tanium Guardian dashboard and a Tanium Atlas page template.
In the meantime, a few steps are recommended:
How Tanium helps
Tanium customers can build that inventory across managed endpoints, including multiple and application-bundled runtimes, by combining several sources of evidence. No single source proves complete coverage, so each one fills a gap in the others.
- Installed software sensor. Search Tanium's installed-application data for Java, JDK, JRE, OpenJDK, Temurin, Corretto, GraalVM and JavaFX, and keep the vendor, full version and install location.
- Deploy. Use Deploy to update vulnerable versions of Java and software with Java components once they are available.
- Containers. Include container image inventory, since endpoint results alone don't cover every image.
The patch is only as useful as your picture of where Java actually runs. That's the part you can get ahead of today.