|
Last Updated |
20 November 2026 |
|---|
Peer Software has been monitoring the news around the recently discovered remote code execution vulnerability that involves Java (CVE-2026-114938). As this vulnerability is new, we will continue to review and post updates to this advisory as necessary.
Based on the information currently available, this vulnerability does affect Peer Global File Service (PeerGFS) and PeerIQ.
|
Product/Tool |
Version(s) |
Status |
Description |
|---|---|---|---|
|
Peer Global File Service |
v5.2 and later |
Impacted |
Multiple components used by PeerGFS use Java, including the PMC, Broker, and Agent. |
|
PeerIQ |
v5.2 and later |
Impacted |
Multiple components used by PeerIQ use Java, including the PMC, Broker, and Agent components, as well two containers within the PeerIQ virtual appliance. |
|
PeerSync |
All |
Not impacted |
PeerSync does not use Java. |
|
File System Analyzer |
All |
Not impacted |
File System Analyzer does not use Java. |
|
File Activity Analyzer |
All |
Not impacted |
File Activity Analyzer does not use Java. |
|
Health Checker |
All |
Not impacted |
Health Checker does not use Java. |
Background and Impact
CVE-2026-114938, also known as Java4Shell, is a critical vulnerability involving memory corruption in Java's hardware-accelerated Base64 decoder. Exploitation requires an affected Java runtime running on an x86-64 processor supporting the AVX-512 VBMI instruction set, with the vulnerable Base64 decoding functionality enabled. The application must also process specially crafted Base64 input through the affected decoder.
PeerGFS
PeerGFS uses several Java-based components, including the Peer Management Center, Peer Management Broker, and Peer Agent. PeerGFS v6.2 and later use Java 23, 24, or 25 runtimes from the Eclipse Temurin project, while PeerGFS v5.2 through v6.1 use affected versions of Eclipse Temurin Java 17. Releases prior to v5.2 use older Java 17 runtimes that are not known to be affected by this specific vulnerability.
PeerGFS components are typically deployed within secured internal networks and are not generally exposed directly to the public internet. This deployment model reduces exposure to external attacks. However, customers who have made PeerGFS services accessible from the public internet may face increased risk.
Although Peer Software has not confirmed a specific exploitation path within PeerGFS, given its use of affected Java versions and Java’s Base64 decoding functionality, we are treating affected releases as potentially vulnerable and recommend applying the mitigation outlined in this advisory.
PeerIQ
PeerIQ uses several Java-based components, including the Peer Management Center, Peer Management Broker, and Peer Agent. The PeerIQ virtual appliance itself also has a pair of containers that use Java. PeerIQ v6.2 and later use Java 23, 24, or 25 runtimes from the Eclipse Temurin project, while PeerIQ v5.2 through v6.1 use affected versions of Eclipse Temurin Java 17. Releases prior to v5.2 use older Java 17 runtimes that are not known to be affected by this specific vulnerability.
PeerIQ components are typically deployed within secured internal networks and are not generally exposed directly to the public internet. This deployment model reduces exposure to external attacks. However, customers who have made PeerIQ services accessible from the public internet may face increased risk.
Although Peer Software has not confirmed a specific exploitation path within PeerIQ, given its use of affected Java versions and Java’s Base64 decoding functionality, we are treating affected releases as potentially vulnerable and recommend applying the mitigation outlined in this advisory.
Recommended Next Steps
PeerGFS Security Updates
Peer Software is planning security updates for PeerGFS v6.5, v6.4, and v6.3, all of which are actively supported under our Peer Software Lifecycle Policy. We also intend to provide a security update for PeerGFS v6.2 as an exception to its end-of-support status.
These security updates depend on the availability of patched Eclipse Temurin 25.0.5.1 binaries from the Eclipse Adoptium project. Once the binaries are available, Peer Software will begin integrating, testing, and validating the updated runtime before releasing the corresponding PeerGFS updates. We will provide additional updates to this advisory as testing progresses and security patches become available.
For customers running PeerGFS v5.2 through v6.1, which are no longer actively supported, we recommend applying the mitigation outlined below and planning an upgrade to a supported PeerGFS release.
In the meantime, we recommend applying the mitigation described in this advisory rather than waiting for the security updates.
PeerIQ Security Updates
Peer Software is planning security updates for PeerIQ v6.5, v6.4, and v6.3, all of which are actively supported under our Peer Software Lifecycle Policy.
These security updates depend on the availability of patched Eclipse Temurin 25.0.5.1 binaries from the Eclipse Adoptium project, as well as updates to the base Docker container that include Java. Once the binaries are available, Peer Software will begin integrating, testing, and validating the updated runtime before releasing the corresponding PeerIQ updates. We will provide additional updates to this advisory as testing progresses and security patches become available.
For customers running PeerIQ v5.2 through v6.1, which are no longer actively supported, we recommend applying the mitigation outlined below and planning an upgrade to a supported PeerIQ release.
In the meantime, we recommend applying the mitigation described in this advisory rather than waiting for the security updates.
Immediate Recommendations
Until the security updates are available, Peer Software recommends that customers:
-
Apply the mitigation outlined below to all potentially affected PeerGFS and PeerIQ installations.
-
Review network accessibility to PeerGFS and PeerIQ components (including the PeerIQ virtual appliance) and ensure they are not unnecessarily exposed to the public internet.
-
Restrict access to PeerGFS and PeerIQ components to trusted systems and networks.
-
Prioritize mitigation for systems with publicly accessible components.
Mitigation for PeerGFS and PeerIQ Shared Components
PeerGFS and PeerIQ share several Java-based components, including Peer Management Center (PMC), Peer Management Broker, and Peer Agent.
The following mitigation instructions apply to these components in both products and involve disabling Java's hardware-accelerated Base64 functionality by updating the applicable .vmoptions files and restarting the associated services. For PeerIQ installations, you must also apply the mitigation described in Mitigation for PeerIQ Virtual Appliance.
Configuration Files
Update only the configuration files corresponding to the installed components.
Peer Management Center (PMC)
-
<PMC Install Folder>/PL-Hub-Service.vmoptions -
<PMC Install Folder>/PL-Hub-Web-Service.vmoptions -
<PMC Install Folder>/API/PMC-API-Service.vmoptions -
<PMC Install Folder>/Broker/PL-Broker.vmoptions -
<PMC Install Folder>/Topology/Peer-Management-Topology-Service.vmoptions
If the Peer Management Center rich client is installed, also update:
-
<PMC Install Folder>/PL-Hub.vmoptions
Peer Management Broker
-
<Broker Install Folder>/Broker/PL-Broker.vmoptions -
<Broker Install Folder>/Topology/Peer-Management-Topology-Service.vmoptions
Peer Agent
-
<Agent Install Folder>/PL-Agent.vmoptions -
<Agent Install Folder>/Peer Master Data Service/PeerMasterDataService.vmoptions
Applying the Mitigation
-
Locate the applicable
.vmoptionsfiles listed above for each installed component.
If an applicable.vmoptionsfile does not exist, create it using the exact filename and location listed above. -
Before making changes, create a backup of each existing
.vmoptionsfile. -
Open each
.vmoptionsfile in a text editor and add the following option on a new line:-XX:-UseBASE64IntrinsicsIf a
.vmoptionsfile already exists, append this option to the bottom of the file, unless the option is already present. -
Save the modified
.vmoptionsfile and restart the corresponding service for the changes to take effect.
Restarting these services may temporarily interrupt PeerGFS and/or PeerIQ operations. We recommend scheduling the restarts according to your organization's maintenance procedures. -
Repeat this process for every applicable
.vmoptionsfile across all Peer Management Center, Peer Management Broker, and Peer Agent installations, including installations at remote sites. -
After restarting the services, confirm that they have started successfully and that normal operations have resumed.
Where JVM diagnostic tools are available, administrators can also check that theUseBASE64Intrinsicsoption is correctly set for the running Java process
Important Considerations
-
This mitigation disables Java's hardware-accelerated Base64 functionality, preventing use of the affected decoding implementation.
-
The mitigation does not replace or update the underlying Java runtime.
-
Changes to
.vmoptionsfiles do not take effect until the associated services are restarted. -
Customers should install the forthcoming security updates when available, even if the mitigation has already been applied.
Mitigation for the PeerIQ Virtual Appliance
The PeerIQ virtual appliance consists of several Docker containers, including two that use Java. The following script applies the mitigation by disabling the UseBASE64Intrinsics option in the applicable Java-based containers.
PeerIQ deployments require mitigation of both the shared PMC, Broker, and Agent components and the Java-based services within the PeerIQ virtual appliance. Customers should apply the mitigation instructions for PMC, Broker, and Agent described above, wherever those components are installed, in addition to the virtual appliance mitigation outlined below.
This mitigation does not persist across PeerIQ appliance upgrades. If you upgrade to a version of PeerIQ that does not include a permanent fix for this vulnerability, you must re-run the script after the upgrade to reapply the mitigation.
sudo docker exec -i brokerinternal sh <<'EOF'
file="/opt/peersoftware/peer-management-broker/Broker/PL-Broker.vmoptions"
default_flag="-Xmx4096m"
flag="-XX:-UseBASE64Intrinsics"
if [ ! -f "$file" ]; then
printf '%s\n' "$default_flag" "$flag" > "$file" || exit 1
echo "Created $file with $default_flag and $flag."
elif ! grep -qE '^[[:space:]]-XX:-UseBASE64Intrinsics[[:space:]]$' "$file"; then
printf '\n%s\n' "$flag" >> "$file" || exit 1
echo "Added $flag to $file."
else
echo "$flag is already present in $file."
fi
file="/opt/peersoftware/peer-management-broker/Topology/Peer-Management-Topology-Service.vmoptions"
printf '%s\n' "$flag" > "$file" || exit 1
echo "Created $file with $flag."
EOF
sudo docker restart brokerinternal
sudo docker exec -u root broker_blob_message sh -c '
set -e
cp -p /app/start.sh /app/start.sh.bak
sed -i "s|java -jar /app/fileAnalytics.jar|java -XX:-UseBASE64Intrinsics -jar /app/fileAnalytics.jar|" /app/start.sh
cat /app/start.sh
' && sudo docker restart broker_blob_message
Note: If PeerIQ is installed on a RHEL- or Rocky- based server, replace docker with podman in the commands above.
Additional Information and References
-
https://openjdk.org/groups/vulnerability/advisories/2026-11-17
-
https://adoptium.net/news/2026/11/temurin-november-2026-cspu-java4shell
Peer Software will update this advisory as our investigation progresses and security updates become available. If you have additional questions, please contact our support team through the Peer Service Desk.