CVE-2026-114938 can let an attacker gain remote code execution on some
Java 17 and 21 builds, including Oracle JDK and OpenJDK builds, when the
host CPU exposes the AVX512_VBMI instruction set. This page shows how to
mitigate CVE-2026-114938 on Apigee Edge for Private Cloud 4.54.00 by
adding the JVM option -XX:UseAVX=2 to each Java-based component,
without upgrading Edge for Private Cloud or the JDK. This option limits HotSpot to
AVX2 instructions, which prevents the JVM from generating the vulnerable
AVX-512 Base64 code.
If you can upgrade the JDK on every node to a Java 17 or Java 21 build that fixes CVE-2026-114938, you don't need these steps.
Before you begin
In the commands on this page, replace COMPONENT with a component
name from Properties to set for each component, for
example edge-message-processor. Replace JDK_HOME with
the installation directory of the JDK that the component runs on.
Apply this mitigation to a node only if all of the following are true:
- The node runs Edge for Private Cloud 4.54.00.00 or 4.54.00.01.
-
The node runs a Java 17 or 21 build that isn't fixed for CVE-2026-114938. To see the version a running component uses, run:
sudo -u apigee JDK_HOME/bin/jcmd "$(cat /opt/apigee/var/run/COMPONENT/COMPONENT.pid)" VM.version
-
The host CPU exposes AVX512_VBMI. The following command prints
affected CPUif it does:grep -wq avx512vbmi /proc/cpuinfo && echo "affected CPU"
Match the exact flag
avx512vbmi; the similar flagavx512_vbmi2doesn't count.
You need sudo access on each node. Plan a rolling restart:
each component restarts once.
Properties to set for each component
Each component reads its JVM options from a different property, and each property has its own quoting rule. Use the line for your component exactly as shown.
| Component | Properties file | Line to add | Rules |
|---|---|---|---|
edge-message-processor |
message-processor.properties |
bin_setenv_ext_jvm_opts="-Djava.security.debug=properties -XX:UseAVX=2" |
Keep the double quotes. Without them, Keep If the property already exists, add
|
edge-management-server |
management-server.properties |
||
edge-router |
router.properties |
||
edge-qpid-server |
qpid-server.properties |
||
edge-postgres-server |
postgres-server.properties |
||
edge-uapim-connector (optional) |
uapim-connector.properties |
||
apigee-cassandra |
cassandra.properties |
conf_jvm_options_custom_settings=-XX:UseAVX=2 |
Don't add quotes. A quoted value is silently ignored. To set more than one flag, separate them with a literal
Don't also set the flag in
|
apigee-zookeeper |
zookeeper.properties |
lib_settings_zk_jvm_opts=-XX:UseAVX=2 |
Don't add quotes. Separate more than one flag with spaces. |
apigee-qpidd |
qpidd.properties |
bin_run-qpidd_qpid.run.jvm.misc_args=-XX:UseAVX=2 |
Don't add quotes. This property accepts exactly one JVM option with no spaces. |
Apply the mitigation
Repeat these steps for each component on each node. In the commands, replace FILE with the component's properties file from Properties to set for each component.
- Open
/opt/apigee/customer/application/FILEin an editor. Create the file if it doesn't exist. - Add the line for the component from the table, following its rules.
-
Make sure the
apigeeuser owns the file and can read it:sudo chown apigee:apigee /opt/apigee/customer/application/FILE
sudo chmod 0644 /opt/apigee/customer/application/FILE -
Restart the component and wait until it's ready:
sudo /opt/apigee/apigee-service/bin/apigee-service COMPONENT restart
sudo /opt/apigee/apigee-service/bin/apigee-service COMPONENT wait_for_ready -
Confirm the running JVM uses the option:
sudo -u apigee JDK_HOME/bin/jcmd "$(cat /opt/apigee/var/run/COMPONENT/COMPONENT.pid)" VM.flags -all=true | grep -wE "UseAVX|UseBASE64Intrinsics"
The output must show
UseAVX = 2with{command line}, for example:int UseAVX = 2 {ARCH product} {command line} bool UseBASE64Intrinsics = true {product} {default}If you used
-XX:-UseBASE64Intrinsicsinstead, the output must showUseBASE64Intrinsics = falsewith{command line}. If the expected line doesn't show both{command line}and the expected value, recheck the flag spelling and the quoting rule for the component, then restart again. - Move to the next node only after
wait_for_readysucceeds, in the order described in Restart order.
Restart order
Restart one node at a time so that traffic and quorum are kept:
- Message Processors and Routers: One node at a time;
wait for
wait_for_readybefore the next. - Cassandra: One node at a time; wait for
wait_for_readybefore the next. - ZooKeeper: Followers first, the leader last, one node
at a time; wait for
wait_for_readybefore the next. - Management Servers, Qpid Servers, Postgres Servers, Qpid
brokers, and UAPIM connectors: One node at a time; wait for
wait_for_readybefore the next.
Roll back the change
-
In
/opt/apigee/customer/application/FILE, remove the line you added. If the line also holds other options you set, remove only the option you added for this CVE:- For the
edge-*components, keep the double quotes and-Djava.security.debug=properties. If you remove the wholebin_setenv_ext_jvm_optsline, the shipped default is restored. - For
apigee-cassandra, also remove the\nseparator next to the option.
- For the
-
Restart the component and wait until it's ready:
sudo /opt/apigee/apigee-service/bin/apigee-service COMPONENT restart
sudo /opt/apigee/apigee-service/bin/apigee-service COMPONENT wait_for_ready
Rolling back reopens exposure to CVE-2026-114938 on that node unless the JDK has been upgraded to a fixed build.