Java Vulnerability (Java4Shell) Mitigations and Remediation Steps
by Michael Ramalho on November, 2026
A Java vulnerability known as Java4Shell was announced on November 17th under CVE-2026-114938. This vulnerability is a memory-corruption vulnerability, and if exploited could lead to application crashes, remote code execution and sensitive information execution.
Java is used in a number of Managed File Transfer products. Below you can find the list of products affected by the vulnerability, with mitigations and remediation steps. This list was last updated on 19/11/2026.
|
Vulnerability |
CVE-2026-114938 |
|
Description |
Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: Compiler) |
|
Published Date |
2026-11-17 |
- GoAnywhere MFT
- Globalscape EFT
- Files.com
- Filecatalyst
- Quatrix/Maytech
- Progress MOVEit, MOVEit Automation, MOVEit Cloud
- ArcESB / CData
- VL Trader, Harmony / Cleo
- WS_FTP
GoAnywhere MFT
GoAnywhere MFT, Agents and Gateways’s packaged runtime uses Azul Zulu Java 11. Based on that configuration, it is not affected by Java4Shell. Azul lists Java 17, 21, 25, and 27 as affected, excluding Java 11. Azul’s official advisory (https://docs.azul.com/core/cve)
Response for Open PGP:
The reviewed OpenPGP Studio 1.2.3 Linux x64 package includes an affected Java runtime. Static analysis found that normal OpenPGP file processing uses Bouncy Castle's own decoder and identified no reachable path to the affected Java Base64 decoder in the default configuration. This supports the current applicability classification for that reviewed configuration. Runtime exploitation was not tested or reproduced. Other installer builds and modified configurations require separate verification.
Response for IBM Java: Not impacted.
Globalscape EFT
Globalscape have confirmed that currently there is no indication that this vulnerability affects EFT. It does, however, affect the EFT DMZ Gateway.
Globalscape EFT Gateway
Globalscape DMZ Gateway releases from this year 4.1.0.88, 4.1.0.89 and 4.1.0.92 all ship with a version of Java that is within the impacted list of products for this CVE.
Version 3.5.0.35 is shipped with 1.8.0_202-b08 which is not vulnerable to CVE-2026-114938
Currently no ETA on when a version will be available with an updated JRE but Java can be updated independently, the steps below are for an older version, but still apply to the later versions of Java:
https://kb.globalscape.com/Knowledgebase/11544/Updating-the-Oracle-JRE-for-DMZ-Gateway
Files.com
Files.com isn't affected by Java4Shell (CVE-2026-114938).
Java4Shell is a bug in the code Java uses to decode Base64 text. Java only runs that code on x86-64 processors that support a specific set of Intel and AMD instructions, called AVX-512 VBMI. The researchers who found this vulnerability confirmed that ARM processors aren't affected.
Every Files.com server that customers connect to runs on ARM processors. That includes our web app, our API, and our SFTP and FTP servers.
We use x86 servers only for a few specific, mostly legacy purposes, such as running third-party software. None of them serve customers directly.
FileCatalyst
FileCatalyst release notes states: Java 11+ is required for all FileCatalyst products. IBM Temurin JRE 11.0.17 is now bundled into all FileCatalyst product installers (Windows, macOS, Linux).
Fortra are currently awaiting confirmation from the FC team that customers can upgrade Java 11 to the latest version within existing installations.
Quatrix / Maytech
We have received confirmation that the mentioned vulnerability is not affecting Quatrix as Java was not/is not used in its development.
Progress MOVEit Transfer, MOVEit Automation, MOVEit Cloud
MOVEit Transfer – Currently Progress report this is unaffected
MOVEit Automation and Gateway:
The CVE does impact a component of the MOVEit Automation and MOVEit Gateway products. To protect and mitigate the risk to MOVEit environments, please use the Workarounds below.
MOVEit Automation Web Admin Steps
- On the server MOVEit Automation is installed on, navigate to the <HOME>\MOVEit Automation Web Admin\Tomcat\bin directory (<HOME> refers to the MOVEit Automation directory that is created during installation. For example, C:\Program Files\MOVEit\)
- Open an administrator command prompt window in this folder and run the following command: tomcat10w.exe //ES//MICAdmin
- The MOVEit Automation Web Admin Properties window should now be open. In this window, click the Java tab.
- In the Java Options textbox, add this text on a new line: -XX:-UseBASE64Intrinsics
- Click Apply, then restart the MOVEit Automation Web Admin service.
Note: beware that upgrading resets the Java Options, so if MOVEit Administrators upgrade after implementing these changes, they would need to perform this implementation again.
Gateway Steps
- In the registry on the Gateway server, navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IpswitchGateway\Parameters
- Edit AppParameters
- At the beginning of this existing value, add -XX:-UseBASE64Intrinsics
- The resulting value should look similar to this:
- -XX:-UseBASE64Intrinsics --add-opens java.base/java.lang=ALL-UNNAMED -jar "C:\Program Files\MOVEit\MOVEit Gateway\gateway-launcher.jar" --mgHome="C:\Program Files\MOVEit\MOVEit Gateway"
- Restart the MOVEit Gateway service.
Please note a fix for this defect will be available in a future MOVEit release.
ArcESB / CData
CData are currently working on a statement to address this, but this vulnerability can affect some editions of the cross-platform edition of CData Arc (the Windows/.NET edition is unaffected), if the JDK used by the application is one of the following Java versions:
|
Java line |
Not affected |
Affected |
|
Java 8 |
All versions (no vulnerable code) |
None |
|
Java 11 |
All versions (no vulnerable code) |
None |
|
Java 17 |
17.0.0 to 17.0.5; 17.0.21.1 and later |
17.0.6 up to (not including) 17.0.21.1. The bundled 17.0.21+9 is in this range |
|
Java 21 |
21.0.13.1 and later |
All versions before 21.0.13.1 |
|
Java 25 |
25.0.5.1 and later |
All versions before 25.0.5.1 |
|
Java 26 |
No fix; upgrade to 27.0.1.1 or later |
All builds released before 2026-11-17 |
|
Java 27 |
27.0.1.1 and later |
All versions before 27.0.1.1 |
In case of an affected version, there is a simple way to mitigate the issue, which is to pass a -XX:-UseBASE64Intrinsics flag to the JVM when you start Arc:
- Temporary mitigation
- In a new terminal where the environment variable is set, run the step 2 commands again. UseBASE64Intrinsics = false {environment} means it took effect.
- The JVM prints an extra line Picked up JAVA_TOOL_OPTIONS: ... at startup. This is expected.
- On Linux, confirm that the running process has the setting:
Add -XX:-UseBASE64Intrinsics to the Arc JVM to switch off the vulnerable optimization. Functionality isn't affected; Base64 decoding is slightly slower.
Windows (service) - if you are running the Cross-Platform edition on Windows
In an administrator cmd, run:
setx JAVA_TOOL_OPTIONS "-XX:-UseBASE64Intrinsics" /M
Then restart the server. A Windows service only sees a new system environment variable after a reboot.
Linux (systemd)
sudo systemctl edit <Arc service name>
Add these two lines in the editor:
[Service] Environment="JAVA_TOOL_OPTIONS=-XX:-UseBASE64Intrinsics"
Save, then run:
sudo systemctl daemon-reload sudo systemctl restart <Arc service name>
Docker
Add this when starting the container:
-e JAVA_TOOL_OPTIONS="-XX:-UseBASE64Intrinsics"
Verify the mitigation
sudo cat /proc/<pid>/environ | tr '\0' '\n' | grep JAVA_TOOL_OPTIONS
Note: This is only a temporary mitigation. Vulnerability scanners will still report the issue based on the JRE version. The permanent fix is an Arc build with Temurin 17.0.21.1 or later (which is not yet published as of this email).
![]()
3. One-line prompt for an AI agent
If an AI agent (for example GitHub Copilot CLI or Claude Code) is available in the customer environment, give it this prompt:
Read-only check: determine whether CData Arc on this server is affected by Java4Shell (CVE-2026-114938). Find the java that the Arc process actually uses (on Windows, also check the system environment variable CDATA_JAVA_PATH) and read its version; with JAVA_TOOL_OPTIONS and JDK_JAVA_OPTIONS cleared, run "java -XX:+PrintFlagsFinal -version" and read UseAVX and UseBASE64Intrinsics; check whether the process command line or its JAVA_TOOL_OPTIONS already contains -XX:-UseBASE64Intrinsics or -XX:UseAVX=2. Affected versions are Java 17.0.6 up to 17.0.21.1, 21 before 21.0.13.1, 25 before 25.0.5.1, all Java 26, and 27 before 27.0.1.1; Java 8 and 11 are not affected. If the version is affected: a mitigation flag in place means "mitigated"; UseAVX <= 2 or UseBASE64Intrinsics = false means "cannot be triggered on this CPU"; UseAVX >= 3 and UseBASE64Intrinsics = true means "affected". Report the verdict (not affected / mitigated / cannot be triggered on this CPU / affected) with evidence, and do not change any system configuration.
VLTrader, Harmony / Cleo
Cleo’s Security team has completed its review and confirmed that Cleo products and systems are not affected by the Java4Shell issue. No mitigation or product changes are required from customers at this time.
WS_FTP
Progress have reviewed WS_FTP Professional and WS_FTP Server for potential exposure to CVE-2026-114938 and found no indication that the affected Java component is included in either product.
Support with Upgrades
It is important to ensure your file transfer tools are updated and secure. If you require any assistance with running your upgrades or with the information above, please contact our support team.
Share this
Recent Blog Posts
The Ultimate MFT Software Tools List
Discover Your Ideal File Transfer Solution
Compare MFT SoftwareResources To Help Your Research
The Beginners Guide to Managed File Transfer
Download Pro2col's definitive guide for insights about file transfer needs, a review of the marketplace and use cases.
Read The Guide
Read Real Customer Success Stories
See real results across several industries, and learn how organisations solved their file transfer challenges.
Explore Case StudiesGet a Personalised File Transfer Recommendation
Take our short 5 minute quiz to discover the perfect file transfer match for your business requirements.
Use The Comparison Tool