Java4Shell (CVE-2026-114938) Impact on EEM
search cancel

Java4Shell (CVE-2026-114938) Impact on EEM

book

Article ID: 462982

calendar_today

Updated On:

Products

Autosys Workload Automation

Issue/Introduction

CA Embedded Entitlements Manager (EEM) ships with a bundled Java 17 runtime ($EIAM_HOME/jre17) and an EEM Java SDK that may be exposed to CVE-2026-114938 ("Java4Shell"), a vulnerability in OpenJDK's Base64 decoding implementation.

An EEM host is impacted only if all three of the following conditions are met:

  1. The host runs an affected EEM version (12.6.9.0, 12.7.0.0, 12.7.1.0, 12.7.2.0, or 12.7.2.1).

  2. The host runs on an x86-64 CPU that supports the AVX-512 VBMI instruction set.

  3. The bundled JRE version is older than the upstream fixed release (OpenJDK 17.0.21.1), and the UseBASE64Intrinsics flag is active (true).

Environment

 

  • Product: CA Embedded Entitlements Manager (EEM) 12.6.9.0 through 12.7.2.1 (and corresponding EEM Java SDK) 

  • Product Associated:  Workload Automation Autosys
  • Operating Systems: Linux and Windows on x86-64 architecture with AVX-512 VBMI CPU support

  • Runtime: Bundled Eclipse Temurin / OpenJDK 17 ($EIAM_HOME/jre17)

 

Cause

CVE-2026-114938 is caused by a flaw in OpenJDK's Base64 decoding intrinsic code path (UseBASE64Intrinsics), which is utilized when running on x86-64 processors equipped with the AVX-512 VBMI instruction set.

 

Resolution

  1. Check for AVX-512 VBMI CPU support:

    • Linux: Run the following command. If it outputs avx512_vbmi, the CPU is supported (no output means the host is not impacted):

      Bash
       
      grep -o avx512_vbmi /proc/cpuinfo | head -1
      
    • Windows: Run Sysinternals Coreinfo and check for AVX-512 VBMI support, or verify your CPU vendor specifications (typically present on newer Intel Xeon and AMD server CPUs).

  2. Check the bundled JRE version and active intrinsic flag:

    • Check the Java version (must be older than 17.0.21.1 to be vulnerable):

      Bash
       
      $EIAM_HOME/jre17/bin/java -version
      
    • Check if the vulnerable code path is enabled (true indicates it is active; false indicates it is already disabled):

      Bash
       
      $EIAM_HOME/jre17/bin/java -XX:+PrintFlagsFinal -version | grep UseBASE64Intrinsics
      

Step 2: Apply Permanent Fix (Preferred)

Once a fixed Eclipse Temurin 17 build (corresponding to OpenJDK 17.0.21.1 or later) is published on the Temurin release status page, upgrade the bundled JRE:

  1. Stop the iGateway service.

  2. Back up or move the existing jre17 directory located under $EIAM_HOME.

  3. Place the new Temurin 17 JRE (matching the host OS and CPU architecture) into $EIAM_HOME and name the folder jre17.

  4. Start the iGateway service.

  5. Verify the updated Java version:

    Bash
     
    $EIAM_HOME/jre17/bin/java -version
    

(Note: To roll back this change, stop iGateway, restore the backed-up jre17 folder, and restart the service.)

Step 3: Apply Interim Workaround (Disable Base64 Intrinsics)

If a fixed Temurin 17 build is not yet available, disable the vulnerable code path in igateway.conf:

  1. Stop the iGateway service and create a backup of igateway.conf (located in the iGateway home directory).

  2. Open igateway.conf and locate the <JVMSettings> section.

  3. Ensure <loadjvm> is set to true, and add the following <Properties> block adjacent to the existing jvm_heapsize block:

    XML
     
    <Properties name="jvm_base64">
      <jvm-property>-XX:-UseBASE64Intrinsics</jvm-property>
    </Properties>
    
  4. Start the iGateway service.

  5. Verify the flag took effect: Identify the iGateway process ID (<pid>). Using a JDK of the same Java 17 line as the same OS user (the bundled JRE does not include jinfo), run:

    Bash
     
    jinfo -flag UseBASE64Intrinsics <pid>
    
    • Expected Output: -XX:-UseBASE64Intrinsics (confirms the Base64 intrinsic is disabled).

    • Unmitigated Output: -XX:+UseBASE64Intrinsics (indicates the default intrinsic is still active).

Additional Notes for the Interim Workaround:

  • Silent Flag Ignorance: If the JRE does not recognize the flag, iGateway will still start normally and silently ignore the setting. Always perform the jinfo verification in Step 5.

  • Performance: The performance impact of disabling Base64 intrinsics has not been benchmarked; compare EEM login times before and after applying the change.

  • Persistence: Re-verify that the jvm_base64 block remains intact in igateway.conf following any product upgrades or failover reconfigurations.

  • EEM Java SDK: Applications embedding the EEM Java SDK on affected versions should either upgrade their host Java runtime to 17.0.21.1+ or pass -XX:-UseBASE64Intrinsics to their JVM startup arguments where possible.

Upgrading Java for EEM:

Upgrade JRE for AutoSys EEM and iGateway: Supported Methods and Symlink Fix