Mitigate Java4Shell (CVE-2026-114938
Mitigate vulnerabilities in your Kilter instance for Java4Shell (CVE-2026-114938).
Overview
CVE-2026-114938 (Java4Shell) is a memory corruption vulnerability in the OpenJDK Base64 decoder. It can only be triggered on CPUs that support a specific set of AVX-512 instructions. On an affected CPU, an attacker who can send crafted Base64 data to the appliance may be able to execute code.
An upcoming Kilter release removes this exposure from Kilter's code and turns on the mitigation below by default. Until you install that release, check your appliance's CPU and, if it is affected, add the mitigation by hand.
BackBox-hosted appliances are not affected. They run on CPUs that cannot trigger the vulnerability. No action is needed for them.
Need help? If you are unsure whether your appliance is affected, or would like assistance applying the mitigation, contact support@backbox.com.
Step 1: Verify if the CPU is Affected
Run the following on the appliance:
grep -m1 '^flags' /proc/cpuinfo | tr ' ' '\n' | grep -E '^(avx512f|avx512bw|avx512vbmi|bmi2)$' | sort
| Output | Meaning |
|---|---|
| All four flags listed | Affected. Continue to Step 2. |
| Fewer than four flags | Not affected. No action is required. |
Example affected CPUs: Intel Xeon Ice Lake and newer, and AMD EPYC Genoa (Zen 4) and newer (e.g., AWS m6i, m7i, m7a). Older Intel generations, AMD EPYC Milan and earlier, and ARM processors are not affected. Always rely on the command above rather than the instance type.
Step 2: Apply the Mitigation
- Edit
/backbox/app-server/bin/app-server.shand add-XX:-UseBASE64Intrinsicsas a new line inside theJAVA_OPTS=( ... )array:JAVA_OPTS=( ... -XX:+UseStringDeduplication -XX:-UseBASE64Intrinsics ... ) - Restart the BackBox service:
sudo systemctl restart backbox - Confirm the running JVM picked up the flag:
ps -eo args | grep -o -- '-XX:-UseBASE64Intrinsics' | head -1Expected output:
-XX:-UseBASE64Intrinsics
Note: Kilter upgrades keep this change.
Performance Impact
Note: With the mitigation in place, Base64 encoding and decoding run more slowly, because the JVM uses a standard code path instead of an optimized CPU instruction. For typical Kilter workloads, which handle small values such as keys and tokens, the slowdown is negligible. Operations that handle large Base64 payloads may be noticeably slower.
Remove the Mitigation
The flag is temporary. Remove it once the appliance's OpenJDK includes the fix from the November 2026 OpenJDK security update. Kilter will remove the flag in a future release once a patched OpenJDK ships with the appliance, and no manual step will be needed.
Related Articles
If you need additional information, contact support@backbox.com.