A permanent fix for Unified Access Gateway is still pending, but Omnissa has published a workaround. Here’s how I tested it in my lab on UAG 2609 running on vSphere.
🔗 Advisory: https://www.omnissa.com/omsa-2026-0003/
🔗 Workaround KB: https://kb.omnissa.com/s/article/6001933
1️⃣ Download the script
Get uag-java4shell-workaround.sh from the KB above.
2️⃣ Take a snapshot
Snapshot the UAG VM before making any changes.
3️⃣ Copy the script to the appliance with PowerCLI
Connect-VIServer <vCenter FQDN>
$cred = Get-Credential root
Copy-VMGuestFile -Source .\uag-java4shell-workaround.sh -Destination /tmp/ -VM “<UAG VM name>” -LocalToGuest -GuestCredential $cred
4️⃣ Run the script
Log in as root from the VM web console. First set the permissions and make the script executable:
cd /tmp
chmod +x /tmp/uag-java4shell-workaround.sh
Then run it from the root home directory:
./uag-java4shell-workaround.sh
5️⃣ Verify
Check that the output has no errors, then review the log file:
cat /var/log/java4shell-workaround.log
✅ Once everything checks out, you can remove the snapshot.
⚠️ This is a temporary mitigation, not the final fix. Keep an eye on the advisory for the runtime patch.
📝 Disclaimer: I tested these steps in my own lab environment only. Use them at your own risk. Always follow the official KB, as Omnissa may update the procedure: https://kb.omnissa.com/s/article/6001933