ShinyProxy 3.2.5

We’ve released ShinyProxy 3.2.5. This is a security update: it upgrades all of
ShinyProxy’s dependencies to fix multiple CVEs. We strongly recommend updating
to this version. As always, detailed upgrade instructions are in
the docs.

In addition to these dependency updates, a critical vulnerability in the Java
virtual machine itself has been discovered.

CVE-2026-114938 (Java4Shell)

Like many other applications, ShinyProxy runs on Java and the OpenJDK JVM. A
critical vulnerability in OpenJDK was recently discovered. It has a CVSS score
of 8.1 because it can lead to a Denial of Service (DoS) and, in some cases,
unauthenticated remote code execution (RCE). The vulnerable code is an AVX-512
optimisation of base64 decoding, so the issue is only exploitable when the CPU
of the server running ShinyProxy supports the AVX-512 instruction set.

If you run ShinyProxy as a plain JAR: upgrade OpenJDK to a patched version
and restart ShinyProxy.

If you use the Docker images: at the time of writing, the base images used
by ShinyProxy do not yet contain the fix, which means the current ShinyProxy
images (openanalytics/shinyproxy) are not yet patched. Therefore, we have
updated the Docker image to include the -XX:-UseBASE64Intrinsics JVM flag.
This disables the vulnerable code. This flag was added to the images for
versions 3.2.5, 3.2.4, 3.1.1 and 3.0.2. Re-pull your image to get the
fix.

To confirm ShinyProxy picked it up, log in as an admin and check the JVM arguments in the admin panel.

Note that this flag was also added to version 2.3., 2.2.2, 2.1.0 and 2.0.0 of the ShinyProxy Operator.