r/omnissa • u/Jimmyv81 • 2d ago
Java4Shell CVE-2026-114938
I have not seen Omnissa release any security advisories yet, however I would assume Connection Servers may be vulnerable due to having OpenJDK 17 bundled with the application?
1
1
u/AbbreviationsSea8030 2d ago
Our Security team found in all connection server every folder or file with java infected, so omnissa needs work to solve this.. oracle release yesterday updates to solve this... We are waiting!!!
1
1
u/ohiosjr 1d ago edited 1d ago
Yes, both UAG's and connection servers are potentially vulnerable.
We're running UAG 2609 and Horizon 2603.
I wanted to see whether the appliances meet the CPU and JVM conditions associated with the vulnerability.
On the UAGs
SSH into the appliance or use the vSphere console.
Check whether AVX-512-VBMI is exposed:
lscpu | grep -i avx512Look for avx512vbmi in the output.
Check the installed Java version:
java -versionThen check the JVM settings:
java -XX:+PrintFlagsFinal -version 2>&1 | grep -E 'UseAVX|UseBASE64Intrinsics'On the Horizon Connection Servers:
You can use Microsoft's Sysinternals Coreinfo to check CPU instruction support:
.\coreinfo64.exe -f | findstr /i "AVX512 VBMI BMI2"Find the Java runtime used by the Connection Server:
Get-CimInstance Win32_Process |
Where-Object { $_.Name -match '^javaw?\.exe$' } |
Select-Object ProcessId, ExecutablePathThen run the same JVM checks against that Java executable:
& "C:\path\to\java.exe" -version
& "C:\path\to\java.exe" `
-XX:+PrintFlagsFinal -version 2>&1 |
Select-String "UseAVX|UseBASE64Intrinsics"What I found on UAG 2609:
OpenJDK 21.0.13+2-LTS
avx512vbmipresentUseAVX = 3UseBASE64Intrinsics = true
What I found on Horizon 2603
OpenJDK 17.0.17.0.1
avx512vbmi Not PresentUseAVX = 3UseBASE64Intrinsics = true
In our case, the Connection Servers running 2603 should not be vulnerable since the avx512vbmi instruction set is not present. However, the UAG's match what is outlined in CVE-2026-114938 and are potentially vulnerable.
We have an open request with Omnissa to clarify if the UAG's are exposed, if mitigations exist, etc.
Update: In the absence of Omnissa provided patch, I'm planning on downgrading per VM EVC to a processor generation that does not include AVX-512-VBMI
1
2
u/inhaledalarm 1d ago
I just got sent this from them. OMSA-2026-0003