JAVA4SHELL · CVE-2026-114938 · CVSS 9.2 (v4.0)
Patching Java? Start by finding every runtime.
A critical flaw reported in OpenJDK builds beginning with 17.0.6 (CVE-2026-114938, CVSS 4.0 9.2) can allow unauthenticated remote code execution. It was disclosed on November 17, 2026, and known exploited as of November 18, 2026. The patch is the easy part. The hard part is finding every Java runtime you're running — including JDKs bundled inside applications and container images — and confirming the build that's actually live.
9.2score
CVSS 4.0 score reported by Calif (Oracle rates it 8.1 under CVSS 3.1)
17.0.6+ firstaffected
OpenJDK builds reported as affected
17.0.21.1patched
Oracle's patched Java 17 build, shipped November 17; the CVE’s published description now lists the affected Oracle versions. Azul has also released fixed Zulu builds.
Java4Shell Expert Advice
Get help finding, prioritizing and verifying Java across your environment.
Loading...
THE HARD PART
The patch is only as useful as your picture of where Java actually runs
Java can sit inside applications and container images as a bundled runtime that never shows up as "Java" in a software list. If you can't see every runtime, you can't be sure every one is updated.
4-STEP RESPONSE
How to respond
A practical order of operations, whatever tools you use.
STEP 1
Find it
Start the Java inventory now. Look for Java, JDK, JRE, OpenJDK, Temurin, Corretto, GraalVM and JavaFX, and record the vendor, full version and install location, including runtimes bundled inside applications and container images.
STEP 2
Prioritize
Start with externally reachable and business-critical Java services, especially Java 17 deployments. Installation or version evidence alone does not confirm exploitability or compromise.
STEP 3
Update & restart
Plan coordinated updates and JVM restarts through the appropriate Java distribution or application vendor. Patched builds are available, including 17.0.21.1 for Java 17. The CVE’s published description now lists the affected Oracle versions. Azul has also released fixed Zulu builds.
STEP 4
Verify
Re-run the same inventory to confirm the build that's actually running. A deployment report alone is not proof that the vulnerable runtime is gone.
HOW TANIUM HELPS
Respond to Java4Shell and build readiness for what comes next.
Use the response to today’s critical vulnerability to build a stronger operating model — connecting current endpoint data, exposure context and governed action across IT and security.
| Response stage | How Tanium helps with Java4Shell | A stronger response to the next critical vulnerability |
|---|---|---|
Find | Build the Java inventory across managed endpoints from several sources of evidence, including Tanium's installed-software data and container image inventory, where available. Use Tanium Vulnerability Library (TVL), the Java4Shell dashboard or Tanium Atlas page template to find vulnerable Java runtimes across your environment. | Start with a current picture of your environment rather than rebuilding an inventory during every incident. Give IT and security a shared foundation for investigation. |
Prioritize | Use the inventory to focus on externally reachable and business-critical Java services, especially Java 17 deployments. Installation or version evidence alone does not confirm exploitability or compromise. | Move beyond severity scores alone. Bring exposure and potential business consequences into the same conversation so teams can focus effort where it matters most. |
Update & verify | Use Tanium Deploy to update vulnerable versions of Java, and software with Java components, once fixes are available, following the appropriate Java distribution or application vendor's guidance. Then re-run the same inventory to confirm the running build. Applications that bundle their own Java runtime may need an update from the application vendor. | Build verification into the response process rather than treating a successful deployment report as proof of remediation. Define ownership, approvals and evidence requirements before the next incident. |
Operating model | Bring questions about Java exposure, response priorities and update status into a shared IT and security workflow. | Leverage Tanium Atlas page template for permissions, approvals and an audit trail to keep operators in control. |
Capabilities vary by deployment model and licensing. Speak to your Tanium team about what's available in your environment.
Response resources
Technical guidance from Tanium's Guardian Research team. Free to use, whatever tools you run.
EXPERT SUPPORT
Need any support with Java4Shell?
Our team can walk you through how to find, prioritize and verify Java across your environment. The guidance and resources on this page are free to use either way.