Java4Shell (CVE-2026-114938): impact on SFTP Gateway
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 SFTP Gateway code.
Affected: SFTP Gateway 3.5.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.
Fix: Update Java from your operating system's packages and restart the service. Fixed Java is available now for Amazon Linux 2023 and Ubuntu: Java 21.0.13.1 and Java 17.0.21.1. The fix also ships in SFTP Gateway 3.10.1, our next patch release, currently planned for early December.
Containers, and servers you cannot update yet: set one Java option until you can update. There is no fixed container image before 3.10.1. No exploitation has been reported.
Last updated: 2026-11-19. Fixed Java packages are available for Amazon Linux and Ubuntu.
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 logging in, we recommend acting now.
Affected versions
| SFTP Gateway version | Java runtime | Affected |
|---|---|---|
| 3.9.0 and later | Java 21 | Yes |
| 3.5.0 through 3.8.3 (3.5.x is end of life) | Java 17 | Yes |
| Earlier than 3.5.0 | Java 11 or earlier | No |
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 updating Java, because some cloud instance types can land on different hardware after a stop and start.
What the risk is
The affected Java code can be reached through the web admin interface over HTTPS before login. We have not found a route to it through the SFTP port. SFTP and the web admin interface run as one service, so an attack that crashes the service would interrupt SFTP as well. In the worst case described by the researchers who found the flaw, an attacker could run code on the server.
If your web admin interface is open to the internet, restricting it to trusted IP addresses reduces your exposure right away.
Update Java (the fix)
Updating Java from your operating system's packages and restarting the service is the complete fix. These steps are written for a single server. If you run high availability or a custom build, adapt them to your environment; the commands and the checks are the same.
The fixed Java packages are:
| Operating system | Java 21 (SFTP Gateway 3.9.0 and later) | Java 17 (SFTP Gateway 3.5.0 through 3.8.3) |
|---|---|---|
| Amazon Linux 2023 | 21.0.13.1.2-1.amzn2023.1 | 17.0.21.1.2-1.amzn2023.1 |
| Ubuntu 24.04 | 21.0.13.1+2-1~24.04.1 | 17.0.21.1+2-1~24.04.1 |
| Ubuntu 22.04 | 21.0.13.1+2-1~22.04.1 | 17.0.21.1+2-1~22.04.1 |
After the update, java -version reports 21.0.13.1 or 17.0.21.1. The fix also ships in SFTP Gateway 3.10.1, our next patch release, currently planned for early December.
If you already added the Java option described under If you cannot update Java yet, it is no longer needed once Java is updated. 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 Linux 2023 (AWS Marketplace AMIs)
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.
Then restart the service so it runs on the updated Java:
sudo systemctl restart sftpgw-admin-api
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 (Azure, Google Cloud)
Install the fixed package for your Java version:
sudo apt-get update
# Java 21 (SFTP Gateway 3.9.0 and later)
sudo apt-get install --only-upgrade openjdk-21-jre-headless
# Java 17 (SFTP Gateway 3.5.0 through 3.8.3)
sudo apt-get install --only-upgrade openjdk-17-jre-headless
Then restart the service so it runs on the updated Java:
sudo systemctl restart sftpgw-admin-api
If automatic security updates are on, the fixed package may already be installed. The service still has to be restarted to run on it.
To confirm, run the commands for your Java version. The version should match the table above or be later, and the changelog check should print 1 or more. It prints 0 on a build without the fix.
# Java 21
dpkg-query -W openjdk-21-jre-headless
zgrep -c CVE-2026-114938 /usr/share/doc/openjdk-21-jre-headless/changelog.Debian.gz
# Java 17
dpkg-query -W openjdk-17-jre-headless
zgrep -c CVE-2026-114938 /usr/share/doc/openjdk-17-jre-headless/changelog.Debian.gz
Containers (Docker, Kubernetes, Helm)
There is no fixed container image yet. The Java runtime is part of the image, so it cannot be updated inside a running container. The fix ships in the SFTP Gateway 3.10.1 images, our next patch release, currently planned for early December.
Until you run 3.10.1, protect the backend container with the Java option -XX:-UseBASE64Intrinsics. It turns off the affected Java code path and is the mitigation recommended by the researchers who found the flaw. It does not change SFTP Gateway behavior, and we do not expect a noticeable effect on performance.
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 SFTP Gateway 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:-UseBASE64Intrinsicsto thedocker runcommand of the backend container.Docker Compose: add
JAVA_TOOL_OPTIONS: "-XX:-UseBASE64Intrinsics"underenvironment:of the backend service, then rundocker compose up -d.Helm: add the option to
config.javaOptsin your values file, keeping any options already there, then runhelm upgradeas 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' ' '
If you cannot update Java yet
If you cannot update Java on a VM right away, add the Java option -XX:-UseBASE64Intrinsics until you can. As on containers, it turns off the affected Java code path and does not change SFTP Gateway behavior. It is harmless on processors without AVX-512 VBMI, including ARM. The complete fix is the Java update above.
Copy and paste the option.
Find the service configuration file. Its name includes the product version:
/opt/sftpgw/sftpgateway-admin-api-<version>.confIf 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 sftpgw-admin-api | grep -E '^(EnvironmentFile|ExecStart)='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 example3.10.0. It is safe to run more than once:f=/opt/sftpgw/sftpgateway-admin-api-<version>.conf sudo grep -q UseBASE64Intrinsics "$f" || sudo sed -i -E '/^JAVA_OPTS=/ s/"[[:space:]]*$/ -XX:-UseBASE64Intrinsics"/' "$f"Restart the service. This disconnects active SFTP sessions and the web admin interface for about half a minute, so choose a quiet time.
sudo systemctl restart sftpgw-admin-apiConfirm 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 sftpgw-admin-api.service failed, the option is most likely mistyped. Java writes the error to the system journal, not to the SFTP Gateway log files:
sudo journalctl -u sftpgw-admin-api | 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, add the option again after upgrading.
References
OpenJDK vulnerability advisory: https://openjdk.org/groups/vulnerability/advisories/2026-11-17
Researchers' write-up (Calif): https://calif.io/java4shell
Amazon Linux security center: https://explore.alas.aws.amazon.com/CVE-2026-114938.html
Ubuntu security notices: https://ubuntu.com/security/notices/USN-9156-1 (Java 21) and https://ubuntu.com/security/notices/USN-9155-1 (Java 17)
Ubuntu security tracker: https://ubuntu.com/security/CVE-2026-114938
Tenable FAQ: https://www.tenable.com/blog/java4shell-cve-2026-114938-frequently-asked-questions-about-openjdk-rce-vulnerability