Is My OPSWAT Central Management Affected by Java4Shell (CVE-2026-114938)?

Is My OPSWAT Central Management Affected by Java4Shell (CVE-2026-114938)?

Category: Security / Vulnerability Assessment

Summary

OPSWAT has reviewed CVE-2026-114938, a vulnerability in OpenJDK known as Java4Shell, for My OPSWAT Central Management (CM10).

  • CM10 Cloud: OPSWAT manages the Cloud service and has already addressed this vulnerability. No action is required.

  • CM10 On-premises (MSI, RPM, OVA): addressed in CM10 10.8.26110.2842. We recommend upgrading to this version or later. If you cannot upgrade right away, a simple workaround is available in this article.

Overview

CVE-2026-114938 is a vulnerability in the Base64 decoder of OpenJDK, the Java runtime used by many enterprise applications. It is rated Critical (CVSS 4.0: 9.2). Under specific conditions, specially crafted input could allow remote code execution.

A system can be affected only when both of these conditions are met:

  • It runs OpenJDK 17.0.6 or later, or Java 21, 25 or 27, before the fixed builds released on November 17, 2026 (for Java 21: earlier than 21.0.13.1).

  • It runs on an x86-64 CPU that supports AVX-512 VBMI, such as Intel Xeon Ice Lake or newer, or AMD EPYC Zen 4 or newer.

Servers with ARM-based CPUs, or with CPUs that do not support AVX-512 VBMI, are not affected.

Which OPSWAT products are affected?

The following table summarizes the assessment as of November 19, 2026.

Product

Status

Details

My OPSWAT Central Management (CM10) – Cloud

Addressed

No customer action is required.

My OPSWAT Central Management (CM10) – On-premises

Fixed in 10.8.26110.2842

Earlier versions bundle a Java runtime in the affected range. Whether a server is affected depends on its CPU (see Overview). Upgrade to 10.8.26110.2842 or later, or apply the workaround below.

Is any customer action required?

CM10 Cloud: No action is required.

CM10 On-premises: Action is needed only when both of the following are true:

  • The server runs a CM10 version earlier than 10.8.26110.2842.

  • The server's CPU supports AVX-512 VBMI. You can check this with step 1 of the workaround below.

If both are true, choose one of the following:

  1. Upgrade (recommended). Upgrade to CM10 10.8.26110.2842 or later, which includes the patched Java runtime. No other steps are needed after upgrading.

  2. If you cannot upgrade right away, apply the workaround. The steps below take a few minutes, need only a service restart, and do not change how CM10 works. If you are unsure of your CPU type, applying the workaround is a safe choice.

If your server's CPU is not in scope, your server is not affected. We still recommend upgrading to 10.8.26110.2842 or later during your next maintenance window, so that vulnerability scanners no longer report this CVE.

Workaround for CM10 On-premises

Use this workaround only if you cannot upgrade to 10.8.26110.2842 or later right away.

The workaround adds the Java option -XX:-UseBASE64Intrinsics through the JAVA_TOOL_OPTIONS environment variable, which Java reads at startup, and then restarts Central Management. It turns off one CPU optimization in Java and does not change Central Management functionality.

RPM and OVA (Linux)

  1. Check whether your server's CPU is in scope, using the Java runtime bundled with Central Management. If the output contains avx512_vbmi, apply the workaround in the next steps. If it does not, your server is not affected and no action is needed.

<product-install-dir>/jre/bin/java -Xlog:os+cpu -version 2>&1 | grep -i "CPU:"

The default <product-install-dir> is

  • RPM: /opt/mocm

  • OVA: /var/opt/mocm

  1. As root, create a systemd drop-in that applies to all Central Management (mocm-*) services:

mkdir -p /etc/systemd/system/mocm-.service.d
cat > /etc/systemd/system/mocm-.service.d/java4shell.conf <<'EOF'
[Service]
Environment="JAVA_TOOL_OPTIONS=-XX:-UseBASE64Intrinsics"
EOF
  1. Reload systemd and restart Central Management:

systemctl daemon-reload
systemctl restart mocm-all.target
  1. Confirm Central Management is running normally: mocm-all.target is active and no MOCM unit is listed as failed.

systemctl status mocm-all.target
systemctl --failed
  1. Confirm every running Java process has the option. Each line should end in ok.

for p in $(pgrep java); do tr '\0' '\n' < /proc/$p/environ | grep -q UseBASE64Intrinsics && echo "$p ok" || echo "$p MISSING"; done

MSI (Windows)

  1. Check whether your server's CPU is in scope, using the Java runtime bundled with Central Management. In Command Prompt, run the command below. If the output contains avx512_vbmi, apply the workaround in the next steps. If it does not, your server is not affected and no action is needed.

"<product-install-dir>\java\bin\java.exe" -Xlog:os+cpu -version 2>&1 | findstr /i "CPU:"

The default <product-install-dir> on Windows is C:\Program Files\OPSWAT\MOCM.

  1. In PowerShell as Administrator, set the machine-wide variable. If JAVA_TOOL_OPTIONS already has a value on this server, add the option to the existing value instead of replacing it.

[Environment]::SetEnvironmentVariable("JAVA_TOOL_OPTIONS", "-XX:-UseBASE64Intrinsics", "Machine")
  1. Restart the server. Windows services read machine-wide variables only at system startup, so restarting the My OPSWAT Central Management service alone is not enough.

  2. After the restart, confirm the service is running and the variable is set:

Get-Service -Name "My OPSWAT Central Management"
[Environment]::GetEnvironmentVariable("JAVA_TOOL_OPTIONS", "Machine")

The service logs under C:\Program Files\OPSWAT\MOCM\tomcat\logs also show Picked up JAVA_TOOL_OPTIONS: -XX:-UseBASE64Intrinsics at startup.

This setting also applies to any other Java application on the same server.

After upgrading to 10.8.26110.2842 or later

The workaround is no longer needed after upgrading. To remove it:

  • RPM and OVA: delete /etc/systemd/system/mocm-.service.d/java4shell.conf, then run systemctl daemon-reload and systemctl restart mocm-all.target.

  • MSI: remove the JAVA_TOOL_OPTIONS machine variable (or the option from it) and restart the server.

How can I verify my environment?

  1. Identify your CM10 deployment type (Cloud or On-premises), version and build, and platform (MSI, RPM or OVA).

  2. For On-premises, if the version is 10.8.26110.2842 or later, no further action is needed. Otherwise, check the server CPU as shown above.

  3. If a vulnerability scanner reports CVE-2026-114938, check the detected file path to see whether it belongs to the CM10 Java runtime or to another application on the server.

  4. Upgrade, or apply the workaround, as described above.

Frequently asked questions

My scanner still reports the CVE after I applied the workaround. Is that expected?

Yes. The workaround turns off the affected code path but does not change the Java version, so version-based scanners may still report it. The finding clears after you upgrade to 10.8.26110.2842 or later.

Is CM10 on an ARM server affected?

No. The affected code is used only on x86-64 CPUs with AVX-512 VBMI.

Does this article cover other Java software on my server?

No. Please check with the vendors of any other Java applications on the same server.

Additional resources

Support

If you need help confirming whether this CVE applies to your deployment, please submit a support case. Include the product name, version and build number, deployment platform, CPU model, and any scanner evidence.

This article applies to the product and version scopes specified above. Last updated: 2026-11-19.