Thorn Tech Marketing Ad
Skip to main content
Version: 1.3.1

Java4Shell (CVE-2026-114938): impact on StorageLink

TLDR - Quick Summary

What: On November 17, 2026, a vulnerability in the Java runtime was published: CVE-2026-114938, also called Java4Shell. The flaw is in Java itself, not in StorageLink code.

Affected: StorageLink 1.1.0 and later, on x86-64 servers whose processor supports AVX-512 VBMI (Intel Ice Lake and newer, AMD Zen 4 and newer). ARM servers are not affected.

Action: Add one Java option and restart the service (Step 1). This protects a server today with no product upgrade. Then install the fixed Java package for your operating system (Step 2): Amazon Linux fixes are available now, Ubuntu fixes are not yet. No exploitation has been reported.

Last updated: 2026-11-18. We will update this article when Ubuntu releases its fixed Java packages.

Summary​

As of November 18, 2026, there are no public reports of this issue being used in real attacks. Oracle rates it 8.1 (High) and describes it as difficult to exploit. Because the affected code can be reached without signing in, we recommend acting now.

Affected versions​

StorageLink versionJava runtimeAffected
1.2.0 and laterJava 21Yes
1.1.0 through 1.1.6Java 17Yes
Earlier than 1.1.0Java 11No

To check a server directly, run java -version. Java 17 and Java 21 are affected. Java 8 and Java 11 are not.

Which servers are exposed​

The flaw only triggers on x86-64 processors that support a feature called AVX-512 VBMI: Intel Ice Lake and newer, and AMD Zen 4 and newer. ARM processors, such as AWS Graviton, are not affected. To check a server, run:

grep -o avx512vbmi /proc/cpuinfo | head -1

If the command prints avx512vbmi, the server is exposed. If it prints nothing, the server is not exposed on its current hardware. We still recommend applying the steps below, because some cloud instance types can land on different hardware after a stop and start. The Java option in Step 1 is harmless on processors that do not have the feature, including ARM.

What the risk is​

The affected Java code can be reached through the StorageLink web interface over HTTPS before sign-in. An attack that crashes the service would interrupt the web portal, its admin pages and any transfers in progress. In the worst case described by the researchers who found the flaw, an attacker could run code on the server.

If the web interface does not need to be reachable from the whole internet, restricting it to trusted IP addresses reduces your exposure right away.

Step 1: Apply the Java option (all platforms)​

These steps are written for a single server and for containers. If you run high availability or a custom build, adapt them to your environment; the option and the check are the same.

The option -XX:-UseBASE64Intrinsics turns off the affected Java code path. This option is the mitigation recommended by the researchers who found the flaw. The complete fix is the Java update in Step 2. The option does not change StorageLink behavior, and we do not expect a noticeable effect on performance.

Copy and paste the option.

On a VM​

  1. Find the service configuration file. Its name includes the product version:

    /opt/swiftgw/swiftgateway-<version>.conf

    If the folder holds more than one, for example after an in-place upgrade, use the one for the running version. This command shows which version the service starts:

    systemctl cat swiftgateway | grep -E '^(EnvironmentFile|ExecStart)='
  2. Find the line that starts with JAVA_OPTS= and add the option at the end, inside the closing quote:

    JAVA_OPTS="<existing options> -XX:-UseBASE64Intrinsics"

    Or make the same edit with one command. Replace <version> with your version, for example 1.4.0. It is safe to run more than once:

    f=/opt/swiftgw/swiftgateway-<version>.conf
    sudo grep -q UseBASE64Intrinsics "$f" || sudo sed -i -E '/^JAVA_OPTS=/ s/"[[:space:]]*$/ -XX:-UseBASE64Intrinsics"/' "$f"
  3. Restart the service. This interrupts the web interface and any uploads or downloads in progress for about half a minute, so choose a quiet time.

    sudo systemctl restart swiftgateway
  4. Confirm the option is active. This should print the running Java process:

    ps -ef | grep [U]seBASE64Intrinsics

If the check in item 4 prints nothing, check that the option sits inside the quotes on the JAVA_OPTS= line of the file for the running version.

If the restart reports Job for swiftgateway.service failed, the option is most likely mistyped. Java writes the error to the system journal, not to the StorageLink log files:

sudo journalctl -u swiftgateway | grep "Unrecognized VM option"

Correct the option in the file and restart.

After a product upgrade: the configuration file is replaced when you upgrade the product. If Java has not been updated yet (Step 2), add the option again after upgrading.

On a container (Docker, Kubernetes, Helm)​

Set this environment variable on the backend container, then recreate the container:

JAVA_TOOL_OPTIONS=-XX:-UseBASE64Intrinsics

Java reads this variable itself, so it works on every StorageLink container version, including when the container's start command has been changed. If you already set JAVA_TOOL_OPTIONS, add the option to your existing value, separated by a space. If you already set JAVA_OPTS, you can leave it as is.

  • Docker: add -e JAVA_TOOL_OPTIONS=-XX:-UseBASE64Intrinsics to the docker run command of the backend container.

  • Docker Compose: add JAVA_TOOL_OPTIONS: "-XX:-UseBASE64Intrinsics" under environment: of the backend service, then run docker compose up -d.

  • Helm: add the option to config.javaOpts in your values file, keeping any options already there, then run helm upgrade as you normally do. The backend pods restart on their own.

    config:
    javaOpts: "-XX:-UseBASE64Intrinsics"
  • Other Kubernetes deployments: add the variable to the env: list of the backend container and apply the change. The pods restart with it.

To confirm, check the backend log. Java prints this line when it starts with the option:

Picked up JAVA_TOOL_OPTIONS: -XX:-UseBASE64Intrinsics
docker logs <backend-container> 2>&1 | grep "Picked up JAVA_TOOL_OPTIONS"
# Kubernetes
kubectl logs <backend-pod> | grep "Picked up JAVA_TOOL_OPTIONS"

On Helm, the option is on the Java command line instead, and the log line does not appear. The output of this command should include -XX:-UseBASE64Intrinsics:

kubectl exec <backend-pod> -- cat /proc/1/cmdline | tr '\0' ' '

Step 2: Update Java when a fixed package is available​

Once Java is updated, the option from Step 1 is no longer needed. It is safe to leave in place.

If you have added your own certificates to Java's trust store (for example for LDAPS, a private storage endpoint or an outbound proxy), back up the store and record its contents before you update Java:

sudo cp -L "$(java -XshowSettings:properties -version 2>&1 | awk '/java.home/{print $3}')/lib/security/cacerts" ~/cacerts.before-java-update
keytool -list -cacerts -storepass changeit | sort > ~/java-truststore-before.txt

After the update, compare. No change means your certificates are still in place:

keytool -list -cacerts -storepass changeit | sort | diff ~/java-truststore-before.txt - && echo "No change"

If certificates are missing, import them again before you restart the service. In our tests the update kept certificates added with keytool, but it replaced a trust store file that had been copied into place.

Amazon has released fixed Java packages. This one command updates Java 21 and Java 17, whichever your server has, so it works on every Amazon Linux 2023 server, including one upgraded in place that has both:

sudo dnf update --advisory ALAS2023-2026-3479 --advisory ALAS2023-2026-3478 --releasever 2023.12.20261117

The --releasever option is needed on servers launched from an earlier image, because Amazon Linux 2023 installs packages only from the release your server was built on. It applies to this command only and does not change the release your server follows.

sudo yum update --advisory ALAS2-2026-4123

Amazon Linux 2 installs security updates on a server's first boot, so a server launched recently may have the fix already. In that case the command reports No packages needed for security.

After updating on Amazon Linux​

Restart the service so it runs on the updated Java:

sudo systemctl restart swiftgateway

To confirm, list the installed Java packages, which is what security scanners read:

rpm -qa 'java-*corretto*'

Every line should show 21.0.13.1.2 or later for Java 21, and 17.0.21.1.2 or later for Java 17.

Ubuntu images (Azure, Google Cloud)​

As of November 18, 2026, Ubuntu has not released a fixed Java package. Updating Java today installs a build that is still affected, so keep Step 1 in place. When Ubuntu releases the fix, install it and restart the service:

sudo apt-get update
# Java 21 (StorageLink 1.2.0 and later)
sudo apt-get install --only-upgrade openjdk-21-jre-headless
# Java 17 (StorageLink 1.1.0 through 1.1.6)
sudo apt-get install --only-upgrade openjdk-17-jre-headless
sudo systemctl restart swiftgateway

To check whether the installed package has the fix, run the command for your Java version. It prints 0 until the fixed package is installed.

# Java 21
zgrep -c CVE-2026-114938 /usr/share/doc/openjdk-21-jre-headless/changelog.Debian.gz
# Java 17
zgrep -c CVE-2026-114938 /usr/share/doc/openjdk-17-jre-headless/changelog.Debian.gz

If automatic security updates are on, the fixed package may install by itself. The service still has to be restarted to run on it.

Container images​

The Java runtime is part of the container image, so it cannot be updated inside a running container. Step 1 protects the container.

References​