CVE-2026-114938 could allow an attacker to execute code remotely on
OpenJDK 17 builds (including Temurin 17.0.17+10 bundled with Apigee hybrid
1.17.0 through 1.17.3) when the host CPU exposes the
AVX512_VBMI instruction set. This page shows how to mitigate
CVE-2026-114938 on Apigee hybrid 1.17.0 through 1.17.3 without upgrading
hybrid by setting
-XX:+IgnoreUnrecognizedVMOptions -XX:UseAVX=2 in your overrides
file.
Setting -XX:UseAVX=2 limits HotSpot to AVX2 instructions,
preventing the JVM from generating the vulnerable AVX-512 Base64 code, while
-XX:+IgnoreUnrecognizedVMOptions prevents startup failures on
non-x86 hosts. If your cluster runs Apigee hybrid 1.17.4 or later, or 1.16
and earlier (which run Java 11 and aren't affected), you don't need these
steps.
Before you begin
Confirm the following conditions and cluster prerequisites before you apply this mitigation:
-
Confirm you run an affected hybrid version (1.17.0 through 1.17.3). Set your hybrid namespace and check the deployed container image tags:
export APIGEE_NAMESPACE=APIGEE_NAMESPACE
kubectl -n "${APIGEE_NAMESPACE}" get pods \ -l 'app in (apigee-runtime,apigee-synchronizer,apigee-mart)' \ -o custom-columns=NAME:.metadata.name,IMAGE:.spec.containers[*].imageReplace APIGEE_NAMESPACE with the Kubernetes namespace where hybrid is installed (default:
apigee). If you enabled Monetization for Apigee hybrid, also check the CronJob image tag withkubectl -n "${APIGEE_NAMESPACE}" get cronjobs -o wide. -
Check whether your worker nodes expose
avx512vbmi. Inspect every runningapigee-runtime,apigee-synchronizer, andapigee-martpod in case different node pools use different machine types:for pod in $(kubectl -n "${APIGEE_NAMESPACE}" get pods \ -l 'app in (apigee-runtime,apigee-synchronizer,apigee-mart)' \ --field-selector=status.phase=Running \ -o jsonpath='{.items[*].metadata.name}'); do kubectl -n "${APIGEE_NAMESPACE}" exec "${pod}" -- \ grep -qw avx512vbmi /proc/cpuinfo && \ echo "${pod}: affected CPU" || echo "${pod}: unaffected CPU" doneMatch the exact flag
avx512vbmi; the similar flagavx512_vbmi2doesn't count. On nodes that don't exposeavx512vbmi(such as Compute Engine E2 machine types or ARM64 nodes), the JVM leavesUseBASE64Intrinsicsdisabled by default, though applying this configuration is still safe if pods later autoscale or move onto AVX-512 nodes. -
Confirm the cluster state is
running. Helm upgrades are rejected if an organization or environment is inreleasingstate:kubectl -n "${APIGEE_NAMESPACE}" get apigeeorg,apigeeenv - Ensure you have
kubectlandhelminstalled, your existingoverrides.yamlfile, and the hybrid Helm charts matching your installed 1.17.x version.
Properties to set for each component
Each Java 17 component in Apigee hybrid 1.17.0 through 1.17.3 reads JVM
options from a cwcAppend property in your
overrides.yaml file. Use the property name and quoting rules for
each component exactly as shown.
| Component | Helm chart | Property path | Value to set | Rules |
|---|---|---|---|---|
apigee-runtime |
apigee-env |
(and |
Recommended: Alternative: |
Keep the inner single quotes ( If If any environment sets
|
apigee-mart |
apigee-org |
mart.cwcAppend.bin_setenv_ext_jvm_opts |
Recommended: Alternative: |
Use the same inner single-quote rule when the value contains spaces. If |
apigee-synchronizer |
apigee-env |
synchronizer.cwcAppend.bin_setenv_compressed_class_space_size |
Recommended: Alternative: |
In hybrid 1.17.0 through 1.17.3,
Keep |
(Monetization only) |
apigee-org |
mintTaskScheduler.cwcAppend.bin_setenv_ext_jvm_opts |
Recommended: Alternative: |
Set this property only if you enabled Monetization for Apigee hybrid. Follows the same inner single-quote rule as |
Apply the mitigation
Edit your existing overrides.yaml file, upgrade the affected
Helm charts, and verify the flags on every running pod.
-
In your existing
overrides.yamlfile, add thecwcAppendentries from Properties to set for each component. Keep any existing keys undercwcAppendintact:runtime: cwcAppend: bin_setenv_ext_jvm_opts: "'-XX:+IgnoreUnrecognizedVMOptions -XX:UseAVX=2'" synchronizer: cwcAppend: bin_setenv_compressed_class_space_size: >- '256m -XX:+IgnoreUnrecognizedVMOptions -XX:UseAVX=2' mart: cwcAppend: bin_setenv_ext_jvm_opts: "'-XX:+IgnoreUnrecognizedVMOptions -XX:UseAVX=2'"
If you prefer single-line YAML formatting for
synchronizer, setbin_setenv_compressed_class_space_size: "'256m -XX:+IgnoreUnrecognizedVMOptions -XX:UseAVX=2'".If Monetization for Apigee hybrid is enabled, also add the
mintTaskSchedulerstanza:mintTaskScheduler: cwcAppend: bin_setenv_ext_jvm_opts: "'-XX:+IgnoreUnrecognizedVMOptions -XX:UseAVX=2'"
If your
overrides.yamlalready definesbin_setenv_ext_jvm_opts(globally or underenvs[].components.runtime.cwcAppend), append the mitigation flags inside the inner single quotes instead of overwriting existing options. For example:runtime: cwcAppend: bin_setenv_ext_jvm_opts: >- '-XX:MaxGCPauseMillis=500 -XX:+IgnoreUnrecognizedVMOptions -XX:UseAVX=2'
-
From the directory containing your hybrid Helm charts, validate and apply the
apigee-orgHelm chart upgrade (updatesapigee-mart, andapigee-mint-task-schedulerwhen Monetization is enabled). Replace ORG_RELEASE_NAME with yourapigee-orgHelm release name and OVERRIDES_FILE with the path to youroverrides.yamlfile:export ORG_RELEASE_NAME=ORG_RELEASE_NAME
export OVERRIDES_FILE=OVERRIDES_FILEhelm upgrade "${ORG_RELEASE_NAME}" apigee-org/ \ --install \ --namespace "${APIGEE_NAMESPACE}" \ -f "${OVERRIDES_FILE}" \ --dry-run=serverhelm upgrade "${ORG_RELEASE_NAME}" apigee-org/ \ --install \ --namespace "${APIGEE_NAMESPACE}" \ -f "${OVERRIDES_FILE}" -
Validate and apply the
apigee-envHelm chart upgrade for each Apigee environment (updatesapigee-runtimeandapigee-synchronizer). Replace ENV_RELEASE_NAME with yourapigee-envHelm release name and ENV_NAME with your Apigee environment name:export ENV_RELEASE_NAME=ENV_RELEASE_NAME
export ENV_NAME=ENV_NAMEhelm upgrade "${ENV_RELEASE_NAME}" apigee-env/ \ --install \ --namespace "${APIGEE_NAMESPACE}" \ --set env="${ENV_NAME}" \ -f "${OVERRIDES_FILE}" \ --dry-run=serverhelm upgrade "${ENV_RELEASE_NAME}" apigee-env/ \ --install \ --namespace "${APIGEE_NAMESPACE}" \ --set env="${ENV_NAME}" \ -f "${OVERRIDES_FILE}" -
Wait until
apigeeorgandapigeeenvreturn to therunningstate and old pods terminate:kubectl -n "${APIGEE_NAMESPACE}" get apigeeorg,apigeeenvkubectl -n "${APIGEE_NAMESPACE}" get pods \ -l 'app in (apigee-runtime,apigee-synchronizer,apigee-mart)' -
Verify that every running
apigee-runtime,apigee-synchronizer, andapigee-martpod restarted with the mitigation flags on its JVM command line:for app in apigee-runtime apigee-synchronizer apigee-mart; do for pod in $(kubectl -n "${APIGEE_NAMESPACE}" get pods \ -l "app=${app}" --field-selector=status.phase=Running \ -o jsonpath='{.items[*].metadata.name}'); do echo "=== ${pod} ===" kubectl -n "${APIGEE_NAMESPACE}" exec "${pod}" -c "${app}" -- sh -c ' for p in /proc/[0-9]*/cmdline; do tr "\0" "\n" < "$p" 2>/dev/null | grep -q \ -e "^com\.apigee\.server\.MessageProcessingServer$" \ -e "^com\.apigee\.server\.SyncServer$" \ -e "^com\.apigee\.server\.MartServer$" && \ tr "\0" "\n" < "$p" | grep \ -e "^-XX:+IgnoreUnrecognizedVMOptions$" \ -e "^-XX:UseAVX=" \ -e "^-XX:[-+]UseBASE64Intrinsics$" \ -e "^-XX:CompressedClassSpaceSize=" || true done ' done doneFor each pod, confirm the output shows
-XX:+IgnoreUnrecognizedVMOptionsand-XX:UseAVX=2(or-XX:-UseBASE64Intrinsicsif you chose the alternative flag), and shows-XX:CompressedClassSpaceSize=256m(or your custom size) forapigee-synchronizer.You can also confirm inside any
apigee-runtimepod that the JVM disablesUseBASE64Intrinsicswhen-XX:UseAVX=2is set (replace RUNTIME_POD with the pod name):kubectl -n "${APIGEE_NAMESPACE}" exec RUNTIME_POD -c apigee-runtime -- \ /usr/lib/jvm/temurin-17-jre-amd64/bin/java \ -XX:+IgnoreUnrecognizedVMOptions -XX:UseAVX=2 \ -XX:+PrintFlagsFinal -version 2>/dev/null | \ grep -E "UseAVX |UseBASE64Intrinsics|IgnoreUnrecognizedVMOptions"Expected output:
bool IgnoreUnrecognizedVMOptions = true {product} {command line} intx UseAVX = 2 {ARCH product} {command line} bool UseBASE64Intrinsics = false {product} {default}If you used
-XX:-UseBASE64Intrinsicsinstead, the JVM flag check must showbool UseBASE64Intrinsics = false {product} {command line}. If the pod command line doesn't include your expected flags, recheck the flag spelling and inner single-quote formatting in Properties to set for each component, updateoverrides.yaml, and re-runhelm upgrade.
Roll back the change after upgrading to 1.17.4 or later
Apigee hybrid 1.17.4 and later automatically pass
-XX:-UseBASE64Intrinsics to Java 17 components. After you
upgrade all organizations and environments to 1.17.4 or later, remove the
temporary mitigation properties:
- In your
overrides.yamlfile, delete the temporarybin_setenv_ext_jvm_optsandbin_setenv_compressed_class_space_sizeentries you added for CVE-2026-114938. If you also have other custom JVM options underbin_setenv_ext_jvm_optsor a custombin_setenv_compressed_class_space_sizesize, remove only the CVE-2026-114938 flags and preserve your custom settings. - Run
helm upgradeforapigee-organd eachapigee-envrelease to apply the cleaned configuration.