[Security advisory] Impact of CVE-2026-114938 (Java4Shell) on the OpManagerNexus portfolio

[Security advisory] Impact of CVE-2026-114938 (Java4Shell) on the OpManagerNexus portfolio

Dear customers,

The recently disclosed OpenJDK vulnerability, CVE-2026-114938 (Java4Shell), has raised security concerns across products that rely on Java. Following a thorough assessment, we would like to clarify its impact on OpManager Nexus and the rest of the network management portfolio.

Products covered

  • OpManager and OpManager Enterprise Edition

  • OpManager Nexus and OpManager Nexus Enterprise Edition

  • OpManager MSP

  • NetFlow Analyzer and NetFlow Analyzer Enterprise Edition

  • Network Configuration Manager (NCM) and Network Configuration Manager Enterprise Edition

  • OpUtils

  • Firewall Analyzer and Firewall Analyzer Enterprise Edition

Affected preconditions :

  •   Customers running product in v12.9 or above.

About the vulnerability

CVE-2026-114938 is a critical memory corruption vulnerability in OpenJDK that could potentially allow remote code execution under certain conditions.

Impact

On-premises OpManager Nexus products:

  • The Java runtime bundled with OpManager Nexus v12.9 and above is the vulnerable range. This covers the bundled JRE used by the OpManager Nexus and rest of the network management services. 

We continuously monitor vulnerabilities in third-party components, assess their applicability to our products, and take timely action wherever necessary.

Interim Remediation (Stopgap Arrangement)

We are currently assessing all affected product lines and preparing permanent patches and service packs that include updated Java Runtime Environment (JRE) builds. Until the official patch for your product is available, we strongly recommend that customers running affected versions on eligible x86-64 hardware apply the workaround below.

This workaround disables the hardware-accelerated Base64 intrinsic affected by the vulnerability.

Steps

  1. Stop the ITOM product service.

  2. Before proceeding, create a backup of the existing files.

  3. Open the JVM configuration file in the product installation directory:

    • Windows:<Product_Home>/conf/itom_wrapper.conf

    • Linux:<Product_Home>/conf/itom_wrapper_linux.conf

    • If your product uses a server startup script instead, edit that script.

  1. Add the following JVM argument:

  1. -XX:-UseBASE64Intrinsics
  2. If you are editing itom_wrapper.conf or itom_wrapper_linux.conf, add it as a new entry: wrapper.java.additional.3100=-XX:-UseBASE64Intrinsics
  1. Save the file and restart the ITOM service for the change to take effect.

Note: This is a temporary measure only. Please apply the official patch or service pack as soon as it is released for your product, and remove this argument afterward if the patch notes advise it.

Notes
If you're using APM Plugin, refer here. 

 If you have questions, please contact our support team or reply to this thread.

Regards,
ManageEngine Team