Is MetaDefender Aether affected by Java4Shell CVE-2026-114938?

Answer

Yes, under specific conditions. The analysis components of MetaDefender Aether (transform and broker) run on a Java runtime that is affected by CVE-2026-114938. The vulnerability can only be exploited when MetaDefender Aether runs on a server whose processor supports the AVX-512 VBMI instruction set (for example Intel Xeon Ice Lake or newer, AMD EPYC Zen 4 or newer). Servers without AVX-512 VBMI, and ARM servers, are not affected.

About the vulnerability

Java4Shell (CVE-2026-114938) is a heap out-of-bounds write in the AVX-512 Base64 decoder of the OpenJDK HotSpot virtual machine. A Java application that passes attacker-controlled Base64 data to the JDK's built-in decoder on a processor with the AVX-512 VBMI instruction set can be made to run attacker code. The upstream CVSS 3.1 score is 8.1, with high attack complexity.

The following Java versions are affected:

  • Java 17, from 17.0.6

  • Java 21, 25 and 27

  • Oracle Java 8 Performance Pack (8u511b33-perf)

  • Oracle GraalVM for JDK 17 and 21

Java 8 (standard), Java 11 and Java 17.0.0 to 17.0.5 are not affected, and neither are ARM processors. Oracle released fixed builds on November 17, 2026: 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1.

Why MetaDefender Aether is affected

MetaDefender Aether analyzes submitted files, and some file types contain Base64-encoded data that the analysis engine decodes with the JDK's built-in decoder. An attacker can therefore deliver the malicious input in a file submitted for analysis, without authentication.

In OPSWAT's tests on an affected processor, a crafted file caused the analysis service to stop and restart automatically. Analyses in progress at that moment did not complete. Code execution was not attempted in these tests and cannot be excluded.

To check whether your server's processor is affected, run:

grep -c avx512vbmi /proc/cpuinfo

If the result is 0, the processor does not support AVX-512 VBMI and the vulnerability cannot be exploited on this server.

Affected versions

Version

Java runtime

Affected

MetaDefender Aether 2.5.1 to 3.3.x

Ubuntu OpenJDK 17, installed when the containers are built

Yes, if the installed build is older than 17.0.21.1 and the processor supports AVX-512 VBMI

MetaDefender Aether engine for MetaDefender Core

Java 17 or 21 installed on the MetaDefender Core server

Yes, if that Java is older than 17.0.21.1 / 21.0.13.1 and the processor supports AVX-512 VBMI

Action required

No action is required on servers whose processor does not support AVX-512 VBMI (grep -c avx512vbmi /proc/cpuinfo returns 0).

1. Interim mitigation (all versions; takes a few minutes; also works offline)

In both /home/sandbox/sandbox/transform/docker-compose.yml and /home/sandbox/sandbox/broker/docker-compose.yml, add the following under the service, after the line restart: unless-stopped:

environment:
- JAVA_TOOL_OPTIONS=-XX:-UseBASE64Intrinsics

Then run sudo service sandbox restart.

A later install or upgrade overwrites these files, so re-apply the change afterwards if it is still needed.

2. Permanent fix for online installations on MetaDefender Aether 3.3.1

  1. If you added custom YARA rules, back them up.

  2. Run sudo systemctl stop sandbox.

  3. Run sudo docker builder prune -af. This clears the Docker build cache only; analysis data, users, API keys, license and configuration are kept.

  4. Run the MetaDefender Aether 3.3.1 installer: sudo ./install.sh.

  5. Verify that sudo docker exec transform java -version and sudo docker exec broker java -version show 17.0.21.1 or later.

  6. Restore your custom YARA rules, if you backed them up.

Plan a maintenance window of about 30 minutes; analysis is unavailable during the update.

MetaDefender Aether engine for MetaDefender Core: update the Java runtime on the MetaDefender Core server to 17.0.21.1 / 21.0.13.1 or your vendor's equivalent, then restart MetaDefender Core.

References

  • CVE-2026-114938

  • OpenJDK Vulnerability Advisory, November 17, 2026