PowerConnect for SAP Solutions
Auto Light Dark
Auto Light Dark

KB 248 - PowerConnect Cloud and CVE-2026-114938


Category: Information

Priority: Normal

Platform: Cloud

Version: 1 from 23.10.2026

PowerConnect Cloud and CVE-2026-114938 (Java4Shell)

Last updated: 18 November 2026

Summary

CVE-2026-114938, nicknamed "Java4Shell", is a reported memory corruption flaw in the Java virtual machine (JVM). It affects Java 17, 21 and 25 on x86-64 CPUs that support the AVX-512 VBMI instruction set.

According to current public analysis, the flaw is in the JVM's hardware-accelerated Base64 decoder (java.util.Base64). A specially crafted Base64 string can make the JVM write past the end of a memory buffer.

The CVE record has not yet been published, and Oracle and OpenJDK have not released technical details. Reports describe it as remote code execution. Analysis so far suggests the realistic impact is a JVM crash, which stops the PowerConnect Cloud node.

Like most web applications, PowerConnect Cloud decodes standard HTTP authentication data such as session cookies and access tokens, which are Base64-encoded. On an affected JVM and CPU, a specially crafted request to the PowerConnect Cloud web port could trigger the flaw before authentication takes place. This is a flaw in the Java runtime, not in PowerConnect Cloud, and it affects any Java application running under the same conditions.

This article will be updated as vendors publish more information.

Am I affected?

You are only affected if all of these are true:

  1. You are running PowerConnect 8.x or later (see the table).

  2. PowerConnect runs on Java 17 or later.

  3. The host CPU supports AVX-512 VBMI.

PowerConnect version

Java 11

Java 17 or later

8.x, 9.0, 9.1, 9.2.x

Not affected

Affected if the CPU supports AVX-512 VBMI

9.3.0 (requires Java 17)

n/a

Affected if the CPU supports AVX-512 VBMI

The Cloud Foundry deployment manifests for PowerConnect 8.x to 9.2.x use Java 11, so those deployments are not affected unless the manifest has been changed. PowerConnect 9.3.0 on Cloud Foundry runs on Java 17.

CPUs with AVX-512 VBMI include:

  • Intel Xeon Ice Lake (3rd gen Scalable) and later, including Sapphire Rapids, Emerald Rapids and Granite Rapids.

  • AMD EPYC and Ryzen Zen 4 and later, including EPYC 9004, 8004 and 9005, and Ryzen 7000 and 9000.

CPUs without it, and therefore not affected:

  • Intel Skylake, Cascade Lake and Cooper Lake Xeons.

  • AMD EPYC Naples, Rome and Milan (Zen 1 to 3).

  • Intel desktop and laptop CPUs from 12th gen (Alder Lake) onwards.

  • All ARM CPUs, such as AWS Graviton, Ampere and Apple Silicon.

The check below is the reliable test, because virtual machines do not always expose every CPU feature.

How to check

Standalone

On each PowerConnect host:

java -version
grep -c avx512vbmi /proc/cpuinfo

If java -version reports 11, or grep returns 0, the host is not affected.

Cloud Foundry

cf ssh <app-name> -c "grep -c avx512vbmi /proc/cpuinfo"
  • "You are not authorized to perform the requested action": SSH is disabled for the app, or you are not a Space Developer in that space. A Space Developer can run cf enable-ssh <app-name> and then cf restart <app-name>.

A result of 0 only applies to the hardware the app is running on now. Cloud Foundry can move an app to different hardware when it is restaged, scaled or evacuated. For that reason we recommend applying the mitigation on Cloud Foundry regardless of the result.

Mitigation

Add the JVM option -XX:-UseBASE64Intrinsics. It turns off the accelerated Base64 code that contains the flaw, so the JVM uses its standard Base64 implementation instead. It is supported on Java 11, 17 and 21, and is safe to set on any CPU.

Standalone

Set JAVA_OPTS before starting PowerConnect. The start script adds it to its own JVM options.

bin/powerconnect.sh stop
export JAVA_OPTS="-XX:-UseBASE64Intrinsics"
bin/powerconnect.sh start

Add the export to the environment PowerConnect starts from, such as the service unit or the profile of the PowerConnect user, so that it persists across restarts. In a cluster, apply it on every node.

For systemd update the service file to include JAVA_OPTS:

[Service]
...
Environment=JAVA_OPTS=-XX:-UseBASE64Intrinsics

Reload the daemon and restart the service

sudo systemctl daemon-reload
sudo systemctl restart powerconnect

To verify, check that the running process has the option:

ps -ef | grep -c "[U]seBASE64Intrinsics"

A result of 1 or more means it is set.

Cloud Foundry

cf set-env <app-name> JAVA_OPTS "-XX:-UseBASE64Intrinsics"
cf restage <app-name>

To verify:

cf ssh <app-name> -c "ps -ef | grep -c '[U]seBASE64Intrinsics'"

Side effects of the mitigation

There is no functional impact. Base64 encoding and decoding gives the same results.

The option can stay in place after the JVM is patched.

Permanent fix

Upgrade to a Java build that includes the fix, then restart PowerConnect:

  • Oracle Java SE: the November 2026 Critical Patch Update (17.0.21, 21.0.13), released 17 November 2026. Oracle has not yet confirmed which CVEs it fixes.

  • Other distributions (Eclipse Temurin, Amazon Corretto, Azul Zulu, Red Hat, SapMachine, Linux distribution packages): no fixed builds were announced at the time of writing. Check your vendor's advisory.

  • Cloud Foundry: the Java version comes from the Java buildpack. A fix is available once the buildpack ships Java 17.0.21 or later and the app is restaged.