This is the information we currently have. This article will be updated as more information is made available. Most of the information comes from https://access.redhat.com/security/vulnerabilities/RHSB-2026-018 and https://github.com/Dungsocool/CVE-2026-114938
Conditions:
- It's only known to impact CPUs with AVX-512 VBMI instructions
- It only impacts java 17 and above (8 and 11 are safe). This only refers to LTS versions.
Check (both must be true):
-
java -version-> Results in 17.0.6 or newer -
grep -o avx512vbmi /proc/cpuinfo | head -1-> If the command outputsavx512vbmi, the system's CPU supports the vulnerable instruction set
Mitigation (any of them should work):
- On-premises
- Upgrade java to the latest release.
- Disable the vulnerable code by adding
-XX:-UseBASE64Intrinsicsto the JVM flags. The easiest way is via theTEAMCITY_SERVER_OPTSenvironment variable. This still runs the code but it's slower - Disable the AVX-512 instructions altogether by adding
-XX:UseAVX=2in the same way
- Cloud
- Our own team is working on our side of the infrastructure.
- The servers seem unaffected so far, as they aren't on x86_64 architecture.
- The agents are being checked, the instances we use most commonly don't seem to be impacted either
- Self-hosted agents, as they are not under our control, would need to be checked and updated accordingly
For impact and analysis, we'd recommend checking here: https://github.com/Dungsocool/CVE-2026-114938 In summary, DoS is the most likely attack vector, with a very low chance of RCE or data leak, and the main way to detect it is if network traffic carries unusual Base 64 loads, mainly larger and/or more padded than normal. Also large amounts of Base64 decode requests.
Comments
1 comment
Assuming that this is Java related vulnerability and not linux only, do you have any instructions for Windows as well?
Please sign in to leave a comment.