Taiwan Information Security Association

Runtime vulnerabilityWed, 18 Nov 2026

Java4Shell: update Java runtimes and assess Base64 exposure

CVE-2026-114938 affects a hardware-specific Java Base64 decoding path. Inventory internet-facing and internal services, containers and bundled runtimes, then follow each vendor’s fixes.

01

Article

Calif demonstrated Java4Shell (CVE-2026-114938), a memory corruption issue in a HotSpot Base64 acceleration path. When an affected JVM decodes attacker-controlled data on specific x86-64 hardware, an application-specific chain may disclose memory or execute code. Exposure depends on the application and its data path.

Oracle, as CNA, published CVSS v3.1 8.1 on 17 November 2026 with high attack complexity. Calif separately reports CVSS v4.0 9.2; these are different assessments. CISA ADP recorded exploitation: none on 17 November. A research demonstration is not evidence of exploitation in the wild.

OpenJDK lists affected branches 17, 21, 25 and 27. Oracle also identifies the specific Java SE 8u511b33-perf build and affected GraalVM versions. OpenJDK reports the issue fixed in its November update; Oracle released Java 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1 updates. Red Hat and Amazon Linux publish separate downstream status; verify the installed distribution and product vendor’s fix.

Calif identifies x86-64 with AVX-512 VBMI, the vulnerable JVM intrinsic and an exposed decoding path as conditions. ARM64 does not use that x86-specific path. Check CPU features presented to VMs and the JDK inside each image.

Attack flowAttacker-controlled data → Memory corruption
  1. 01

    Attacker-controlled data

    The reachable route depends on the application and authentication

  2. 02

    Decoder route

    Untrusted Base64 is decoded by the affected runtime

  3. 03

    Hardware and JVM

    The affected intrinsic runs on supported x86-64 CPUs

  4. 04

    Memory corruption

    A tailored chain may disclose memory, disrupt service or execute code

Actions: from the external boundary to the internal core

Response flowActions: from the external boundary to the internal core
  1. 01

    Inventory runtimes

    Include internal and outsourced services, containers and bundled JDKs; identify vendor, build, CPU and data path.

    See what to doResources: 1

    TWISA member solutions

    Inventory runtimes

    Include internal and outsourced services, containers and bundled JDKs; identify vendor, build, CPU and data path.

  2. 02

    Patch and restart

    Apply the vendor’s update, rebuild images, restart and verify the running JVM.

  3. 03

    Apply interim mitigation

    Calif recommends -XX:-UseBASE64Intrinsics as an interim measure; verify vendor support and performance before restarting.

  4. 04

    Monitor and recover

    Review JVM crashes, process, network and service logs; preserve evidence and verify backups.

    See what to doResources: 1

    TWISA member solutions

    Monitor and recover

    Review JVM crashes, process, network and service logs; preserve evidence and verify backups.

Within an authorized scope, perform asset discovery, vulnerability scanning, penetration and API tests, attack simulation and retesting. For web traffic, verify the request, WAF alert, actual block and backend outcome. Examine internal and client-side paths separately. A WAF does not replace the runtime update.

Defense architectureLayered protection from entry to core

Include internal and outsourced services, containers and bundled JDKs; identify vendor, build, CPU and data path.

Allow authorized traffic and apply controls at each layer.

  1. 01

    Entry and services

    Limit exposure and map reachable data paths

    Inventory runtimesLimit exposure and map reachable data paths

  2. 02

    Runtime

    Patch JDKs, containers and bundled components

    Patch and restartPatch JDKs, containers and bundled components

  3. 03

    Internal core

    Apply least privilege, segmentation and data safeguards

    Limit privilegesApply least privilege, segmentation and data safeguards

Feed logs and traffic data from each layer into monitoring and response.

  1. Monitor and recoverCorrelate JVM and service anomalies; preserve evidence and restore safely.

Contact TWISA members for further information about their products and services.

Alert updated: 2026/11/18. Refer to the vendor for current support and remediation status.