Mitigate CVE-2026-114938 on Apigee hybrid 1.17

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[*].image
    

    Replace 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 with kubectl -n "${APIGEE_NAMESPACE}" get cronjobs -o wide.

  • Check whether your worker nodes expose avx512vbmi. Inspect every running apigee-runtime, apigee-synchronizer, and apigee-mart pod 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"
    done
    

    Match the exact flag avx512vbmi; the similar flag avx512_vbmi2 doesn't count. On nodes that don't expose avx512vbmi (such as Compute Engine E2 machine types or ARM64 nodes), the JVM leaves UseBASE64Intrinsics disabled 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 in releasing state:

    kubectl -n "${APIGEE_NAMESPACE}" get apigeeorg,apigeeenv
    
  • Ensure you have kubectl and helm installed, your existing overrides.yaml file, 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

runtime.cwcAppend.bin_setenv_ext_jvm_opts

(and envs[].components.runtime.cwcAppend if used)

Recommended:
"'-XX:+IgnoreUnrecognizedVMOptions -XX:UseAVX=2'"

Alternative:
"-XX:-UseBASE64Intrinsics"

Keep the inner single quotes ('...') inside the YAML double quotes whenever the value contains spaces. Startup scripts source the generated shell variable without quotes, so unquoted spaces break container startup.

If bin_setenv_ext_jvm_opts already exists in your overrides, append the flags inside its existing value wrapped in inner single quotes.

If any environment sets envs[].components.runtime.cwcAppend.bin_setenv_ext_jvm_opts, add the flags there too because environment-specific keys override top-level runtime.cwcAppend keys of the same name.

apigee-mart apigee-org mart.cwcAppend.bin_setenv_ext_jvm_opts

Recommended:
"'-XX:+IgnoreUnrecognizedVMOptions -XX:UseAVX=2'"

Alternative:
"-XX:-UseBASE64Intrinsics"

Use the same inner single-quote rule when the value contains spaces.

If bin_setenv_ext_jvm_opts already exists in your overrides, append the flags inside its existing value wrapped in inner single quotes.

apigee-synchronizer apigee-env synchronizer.cwcAppend.bin_setenv_compressed_class_space_size

Recommended:
"'256m -XX:+IgnoreUnrecognizedVMOptions -XX:UseAVX=2'"

Alternative:
"'256m -XX:-UseBASE64Intrinsics'"

In hybrid 1.17.0 through 1.17.3, apigee-synchronizer doesn't pass bin_setenv_ext_jvm_opts to its startup script. Set bin_setenv_compressed_class_space_size instead.

Keep 256m (the shipped default) or your custom configured size as the first token, followed by a space and the JVM flags, wrapped in inner single quotes inside YAML double quotes.

apigee-mint-task-scheduler

(Monetization only)

apigee-org mintTaskScheduler.cwcAppend.bin_setenv_ext_jvm_opts

Recommended:
"'-XX:+IgnoreUnrecognizedVMOptions -XX:UseAVX=2'"

Alternative:
"-XX:-UseBASE64Intrinsics"

Set this property only if you enabled Monetization for Apigee hybrid.

Follows the same inner single-quote rule as runtime and mart.

Apply the mitigation

Edit your existing overrides.yaml file, upgrade the affected Helm charts, and verify the flags on every running pod.

  1. In your existing overrides.yaml file, add the cwcAppend entries from Properties to set for each component. Keep any existing keys under cwcAppend intact:

    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, set bin_setenv_compressed_class_space_size: "'256m -XX:+IgnoreUnrecognizedVMOptions -XX:UseAVX=2'".

    If Monetization for Apigee hybrid is enabled, also add the mintTaskScheduler stanza:

    mintTaskScheduler:
      cwcAppend:
        bin_setenv_ext_jvm_opts: "'-XX:+IgnoreUnrecognizedVMOptions -XX:UseAVX=2'"

    If your overrides.yaml already defines bin_setenv_ext_jvm_opts (globally or under envs[].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'
  2. From the directory containing your hybrid Helm charts, validate and apply the apigee-org Helm chart upgrade (updates apigee-mart, and apigee-mint-task-scheduler when Monetization is enabled). Replace ORG_RELEASE_NAME with your apigee-org Helm release name and OVERRIDES_FILE with the path to your overrides.yaml file:

    export ORG_RELEASE_NAME=ORG_RELEASE_NAME
    export OVERRIDES_FILE=OVERRIDES_FILE
    helm upgrade "${ORG_RELEASE_NAME}" apigee-org/ \
      --install \
      --namespace "${APIGEE_NAMESPACE}" \
      -f "${OVERRIDES_FILE}" \
      --dry-run=server
    helm upgrade "${ORG_RELEASE_NAME}" apigee-org/ \
      --install \
      --namespace "${APIGEE_NAMESPACE}" \
      -f "${OVERRIDES_FILE}"
    
  3. Validate and apply the apigee-env Helm chart upgrade for each Apigee environment (updates apigee-runtime and apigee-synchronizer). Replace ENV_RELEASE_NAME with your apigee-env Helm release name and ENV_NAME with your Apigee environment name:

    export ENV_RELEASE_NAME=ENV_RELEASE_NAME
    export ENV_NAME=ENV_NAME
    helm upgrade "${ENV_RELEASE_NAME}" apigee-env/ \
      --install \
      --namespace "${APIGEE_NAMESPACE}" \
      --set env="${ENV_NAME}" \
      -f "${OVERRIDES_FILE}" \
      --dry-run=server
    helm upgrade "${ENV_RELEASE_NAME}" apigee-env/ \
      --install \
      --namespace "${APIGEE_NAMESPACE}" \
      --set env="${ENV_NAME}" \
      -f "${OVERRIDES_FILE}"
    
  4. Wait until apigeeorg and apigeeenv return to the running state and old pods terminate:

    kubectl -n "${APIGEE_NAMESPACE}" get apigeeorg,apigeeenv
    kubectl -n "${APIGEE_NAMESPACE}" get pods \
      -l 'app in (apigee-runtime,apigee-synchronizer,apigee-mart)'
    
  5. Verify that every running apigee-runtime, apigee-synchronizer, and apigee-mart pod 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
    done
    

    For each pod, confirm the output shows -XX:+IgnoreUnrecognizedVMOptions and -XX:UseAVX=2 (or -XX:-UseBASE64Intrinsics if you chose the alternative flag), and shows -XX:CompressedClassSpaceSize=256m (or your custom size) for apigee-synchronizer.

    You can also confirm inside any apigee-runtime pod that the JVM disables UseBASE64Intrinsics when -XX:UseAVX=2 is 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:-UseBASE64Intrinsics instead, the JVM flag check must show bool 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, update overrides.yaml, and re-run helm 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:

  1. In your overrides.yaml file, delete the temporary bin_setenv_ext_jvm_opts and bin_setenv_compressed_class_space_size entries you added for CVE-2026-114938. If you also have other custom JVM options under bin_setenv_ext_jvm_opts or a custom bin_setenv_compressed_class_space_size size, remove only the CVE-2026-114938 flags and preserve your custom settings.
  2. Run helm upgrade for apigee-org and each apigee-env release to apply the cleaned configuration.