Tanzu Advisory for CVE-2026-114938 (OpenJDK Base64 decoder memory corruption)
39639
18 November 2026
18 November 2026
OPEN
HIGH
8.1
CVE-2026-114938
|
Advisory ID: |
TNZ-2026-1107 |
|
Severity: |
High |
|
CVSSv3 NVD: |
|
|
CVSSv3 Tanzu: |
8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H (unchanged from the CVE record for now; Tanzu has not yet applied environmental adjustments, see Tanzu Details) |
|
Issue Date: |
2026-11-18 |
|
Updated on: |
2026-11-18 |
|
CVE(s): |
CVE-2026-114938 |
|
Synopsis: |
A memory corruption flaw in the OpenJDK HotSpot Java runtime, in the hardware-accelerated Base64 decoder behind java.util.Base64, lets an unauthenticated remote attacker who can supply crafted Base64 input to an application corrupt memory. This can crash the application (denial of service) and, per the CVE record, can result in takeover of the affected Java process. It affects Java 17 (17.0.6 and later), 21, 25 and 27, and only when the application runs on an x86-64 CPU that supports AVX-512 VBMI. Several Tanzu products include affected Java runtimes. Tanzu is still assessing each product and applying fixes as fixed builds of the Java runtimes we ship become available. This advisory will be updated as products are assessed and fixed versions are released. |
Advisory links:
- https://www.cve.org/CVERecord?id=CVE-2026-114938
- https://openjdk.org/groups/vulnerability/advisories/2026-11-17
- Java4Shell Security Advisory - https://nvd.nist.gov/vuln/detail/CVE-2026-114938
- Symantec Protection Bulletin
Workaround: Until a fixed Java runtime is available for your product, start affected JVMs with one of the following options, then restart them:
- -XX:-UseBASE64Intrinsics (preferred): disables only the hardware-accelerated Base64 implementation.
- -XX:UseAVX=2: disables AVX-512 instructions entirely. Use it only on x86-64 hosts: JVMs on ARM64 do not recognize it and fail to start. It can also slow cryptographic and other vectorized code.
Option: Temporary Mitigation for apps on Tanzu Platform(Tanzu Platform-Wide Environment Variable)
If you cannot immediately deploy the patched buildpack, disable the vulnerable Base64 intrinsic across your foundation using the JDK_JAVA_OPTIONS environment variable.
1. Inspect the current running environment variable group (setting a new group overwrites existing keys):
- cf running-environment-variable-group
2. Add JDK_JAVA_OPTIONS to the group, preserving all existing variables returned in Step 1:
- cf set-running-environment-variable-group '{...existing keys..., "JDK_JAVA_OPTIONS":"-XX:-UseBASE64Intrinsics"}'
3. Apply per-app overrides (if applicable): Check whether individual applications explicitly define their own JDK_JAVA_OPTIONS (cf env <app>), as app-level variables override the running environment variable group. For those apps, append the flag directly:
- cf set-env <app> JDK_JAVA_OPTIONS "<existing-value> -XX:-UseBASE64Intrinsics"
4. Perform a rolling restart of affected Java applications (a restage is not required):
- cf restart <app> --strategy rolling
Hosts that are not exposed to the flaw do not need the workaround (see Conditions below). Treat the options as interim measures and remove them once the fixed runtime is deployed.
Additional Information
- Why JDK_JAVA_OPTIONS instead of JAVA_TOOL_OPTIONS or JAVA_OPTS?
- Java 8 Compatibility: JDK_JAVA_OPTIONS was introduced in Java 9, meaning Java 8 JVMs silently ignore it. Passing -XX:-UseBASE64Intrinsics via JAVA_TOOL_OPTIONS (even with -XX:+IgnoreUnrecognizedVMOptions) can cause Java 8 runtimes to fail on startup.
- Fewer App Collisions: Many applications already define JAVA_OPTS in their manifests, which would override a group-level JAVA_OPTS setting.
- No Restage Required: Environment variable groups are injected when application containers start, so a simple restart (cf restart) is sufficient to activate the mitigation.
- Virtualization Note: In vSphere environments, guest VMs running on older VM hardware versions or legacy EVC baselines may not expose AVX-512 instructions to the guest OS, which limits exploitability even on AVX-512-capable physical CPUs.
Tanzu Details
Status. The OpenJDK project has published fixed builds (17.0.21.1, 21.0.13.1 and 25.0.5.1). Products are being assessed individually; where a product can ship an interim configuration change before a fixed runtime is available, its release notes will say so.
Why the Tanzu CVSS score equals the CVE record for now. The CVE record scores the issue 8.1 with attack complexity High, which reflects that exploitation depends on the CPU feature and on the decoder being compiled to its accelerated form. Tanzu has not yet identified a product-specific reason to change any metric, so the table above repeats the CVE record. This section will be updated if the assessment of a product changes the score.
Conditions. A deployment is exposed only if all of these are true:
- It runs an affected Java version: 17.0.6 up to 17.0.21.0.3, 21 up to 21.0.13.0.3, 25 up to 25.0.5.0.3, or 27.0.1.0.3 and earlier. Builds that look older, such as 17.0.20.1 or 25.0.4.1, are affected.
- It runs on an x86-64 CPU with AVX-512 VBMI (Intel Ice Lake and newer server processors, AMD Zen 4 and newer). ARM64 and older x86-64 processors do not use the affected code.
- The JVM was not started with -XX:UseAVX=2 (or lower) or -XX:-UseBASE64Intrinsics.
- An attacker can send input that the application Base64-decodes with java.util.Base64 (the basic or URL decoder, not the MIME decoder), for example HTTP Basic credentials, tokens or certificates.
Not affected: Java 11 and Java 17.0.5 and earlier do not contain the affected code. Tanzu is still verifying Java 8 runtimes that ship in some products.
Impact. Remote code execution and denial of service in the Java process that decodes the crafted input (confidentiality, integrity and availability all High), within the trust boundary of the affected component. What an attacker gains depends on the component: whether it decodes untrusted input before authentication, and whether the decoder is reachable from outside the platform.
Mitigation
- Apply the fixed product versions as they are released.
- Use the interim options under Workaround, starting with the products and applications that are reachable from untrusted networks, especially authentication services.
- Hosts without AVX-512 VBMI (ARM64, Intel Cascade Lake and older, AMD before Zen 4) are not exposed. Choosing such hosts is a valid compensating control, but verify it with the detection steps above.
- Applications that you run on Tanzu Platform with the Java buildpack use the runtime inside the buildpack. Apply the workaround to them, and update the buildpack when a fixed version is released.
- Customer-built Java applications and container images that bundle their own Java runtime are not covered by this advisory. Check them against the affected range above.
Per product impact
|
Product |
Impact on Tanzu product |
Fixed version |
|
Java Buildpack (offline and offline-performance packages) |
Affected before 5.5.0: the packaged Java 17, 21 and 25 runtimes are in the affected range (5.4.0 carries 17.0.21.0.3, 21.0.13.0.3 and 25.0.5.0.3; 4.100.0 carries 17.0.20.1 and 21.0.12.1). Version 5.5.0 carries Java 17.0.21.1, 21.0.13.1 and 25.0.5.1. Java 11 runtimes are not affected. The Java 8 runtimes are still being verified. Applications you stage with the buildpack use these runtimes. |
5.5.0 |
|
Ruby Buildpack (offline packages for all stacks) |
Affected in 1.10.103: the packaged Java 21 runtime (21.0.13.0.3) is in the affected range. Version 1.10.104 carries Java 21.0.13.1. |
1.10.104 |
|
VMware Tanzu Distribution of OpenJDK, Java 17 |
Affected before 17.0.21.1 (17.0.6 up to 17.0.21.0.3). |
17.0.21.1+5 |
|
VMware Tanzu Distribution of OpenJDK, Java 21 |
Affected before 21.0.13.1 (up to 21.0.13.0.3). |
21.0.13.1+5 |
|
VMware Tanzu Distribution of OpenJDK, Java 25 |
Affected before 25.0.5.1 (up to 25.0.5.0.3). |
25.0.5.1+5 |
|
VMware Tanzu Distribution of OpenJDK, Java 11 |
Not affected: Java 11 does not contain the affected code. Release 11.0.33.1+5 is published with the same update. |
Not applicable |
|
VMware Tanzu Distribution of OpenJDK, Java 8 |
Still being verified. Release 8u514+5 is published with the same update. |
History
2026-11-18: Initial vulnerability report published. Product assessment is in progress; this advisory will be updated as fixed versions are released.
2026-11-18: Fixed versions released for Java Buildpack (5.5.0), Ruby Buildpack (1.10.104) and VMware Tanzu Distribution of OpenJDK (17.0.21.1+5, 21.0.13.1+5, 25.0.5.1+5). =
2026-11-18: Updated with Tanzu Platform specific mitigation commands.
Contact
E-mail: [email protected]
VMware Tanzu Security Advisories https://tanzu.vmware.com/security