Cisco Talos reported that Cisco issued an advisory on November 18, 2026, for products potentially affected by Java4Shell (CVE-2026-114938). Administrators can start by inventorying Java runtimes embedded in applications, containers, and appliances, as the U.S. Cybersecurity and Infrastructure Security Agency (CISA) advises. Talos’s report and CISA’s guidance address different parts of the response: the reported Cisco advisory and the broader task of finding Java runtimes.

Treat Java inventory as part of the software inventory: a runtime can be bundled inside an application, container, or appliance.

What Java conditions does Talos describe?

Talos describes Java4Shell as a flaw triggered by malformed Base64 input. Its reported exposure conditions are OpenJDK Java 17.0.6 or later running on an x86-64 processor with AVX-512 VBMI enabled. Talos gives the vulnerability a CVSS 4.0 score of 9.2 and says the flaw may allow unauthenticated remote code execution under those conditions. These are Java runtime and processor conditions, not a Cisco product inventory. Talos’s technical description

Datadog’s analysis says denial of service is more readily achievable when attacker-controlled input reaches the vulnerable decoder, while reliable remote code execution requires additional work specific to the application and JVM environment. That distinction matters when teams assess possible impact: the reported RCE potential does not mean every vulnerable deployment can be reliably taken over.

Talos recommends applying the relevant software update. It also describes -XX:UseAVX=2 as an interim option for x86-64 systems; ARM-based processors do not recognize the flag, and applying it may prevent the JVM from starting. These are general Java mitigations, not Cisco product-specific instructions.

For more detail on Java version scope and administrator measures, see NeoTeo’s guide to the OpenJDK lines and Oracle builds affected by Java4Shell.

How should administrators look for bundled Java?

CISA advises organizations to inventory Java runtimes inside third-party applications, container images, and appliances, as those copies may not appear as separate entries in a software inventory. Include these embedded runtimes in the same review as standalone Java installations.

CISA also advises applying relevant Java and vendor patches, prioritizing internet-facing systems, and monitoring for suspicious runtimes, JVM crashes, and Java processes. That gives administrators concrete places to focus while assessing Java exposure across their environments.