Skip to content
[ SIGNAL VERIFIED ] INDEPENDENT CYBERCRIME JOURNALISMCLASSIFIED // THE UNDERGROUND HAS A NEWSROOM / RSS
.COM
Latest News
ALL NEWS
Newsroom

Cisco confirms Java4Shell exposure in Catalyst Center and other products

Cisco's November 18 advisory lists affected products, unresolved investigations and pending fixes for Java4Shell, with no malicious use reported.

Cisco confirms Java4Shell exposure in Catalyst Center and other products
PUBLISHED

Cisco published a product-specific Java4Shell advisory at 16:00 UTC on November 18, 2026. Catalyst Center is affected, alongside products including Secure Network Analytics, Secure Workload and Intersight Virtual Appliance. The vulnerability is tracked as CVE-2026-114938.

Confirmed exposure and unresolved investigations

ISE, IOS XE, IOS XR and NX-OS remain under investigation. Cisco lists ASA, FMC, FTD, Nexus Dashboard and the Catalyst SD-WAN Controller, Manager and Validator as unaffected. These classifications describe the advisory’s current findings; they are not interchangeable.

Cisco has not supplied a fixed release for Catalyst Center. Other affected-product entries also contain pending release information. The company lists no product workaround and says it knows of public proof-of-concept code, but no malicious use.

The November 17 Talos assessment explains that the underlying issue involves malformed Base64 processing in affected OpenJDK runtimes on x86-64 processors with AVX-512 VBMI support. That hardware condition matters when assessing exposure; the presence of Java alone does not establish that a deployment is vulnerable.

IPCRIME analysis: make the inventory actionable

Administrators should record each product, installed build, hosting platform and vendor status in their remediation plan. Keep unresolved products on a review list, with an owner responsible for checking the advisory again. An investigation entry is a reason to seek clarification, rather than evidence of either exposure or safety.

For an affected appliance, confirm the supported upgrade or mitigation with Cisco before changing its bundled runtime. A generic JVM setting can be inappropriate for a managed product. Preserve the advisory revision used for the decision so later vendor changes can be reconciled against the original assessment.

For the wider vulnerability and Oracle patch context, see IPCRIME’s Java4Shell and Oracle security update coverage.

Related reading: PaperCut Issues Java4Shell Guidance for NG/MF Servers on Affected Hardware.

Featured image: conceptual IPCRIME artwork, not a photograph or screenshot of this incident or product.

Editorial note

IPCRIME distinguishes public records and documented findings from allegations, analysis and commentary. Report corrections through our contact page.