Skip to main content
Emerging Issue

Java4Shell (CVE-2026-114938): Tanium Is Tracking Closely, and Helping You Find Every Java Runtime

Learn what's reported so far, what Tanium is tracking and how to find every Java runtime with Tanium.

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.

  • The flaw: Java4Shell can allow unauthenticated remote code execution in affected OpenJDK builds beginning with 17.0.6. Patched builds are available; exposure depends on the Java distribution, build, hardware and application. Oracle also lists a specific Java 8 Enterprise Performance Pack build as affected.
  • Severity: Calif rates the flaw 9.2 (Critical) under CVSS 4.0; Oracle rates it 8.1 under CVSS 3.1.
  • Patches: Oracle shipped patched Java builds today, including 17.0.21.1 for Java 17, as part of a wider update. It hasn't yet tied a specific fix to this CVE.
  • Details and POC code are now available: Calif has released the technical details of the vulnerability.
  • Exploitation: no confirmed exploitation has been reported as of this writing.

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:

  • Start the Java inventory now, including bundled runtimes and container images.
  • Prioritize externally reachable and business-critical Java services, especially Java 17 deployments.
  • Plan coordinated updates and JVM restarts, then re-run the same inventory afterward to confirm the running build.

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.

  1. 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.
  2. Deploy. Use Deploy to update vulnerable versions of Java and software with Java components once they are available.
  3. 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.