
Notice Links:
| Posted | Wed, 18 Nov 2026 21:10 PM UTC
Wed, 18 Nov 2026 16:10 PM EST |
|---|---|
| Last Update | Wed, 18 Nov 2026 21:12 PM UTC (206 minutes ago)
Wed, 18 Nov 2026 16:12 PM EST |
| Status | Open |
If your server runs Tomcat, WildFly, or another Java application, check the Java it uses and apply your vendor's November security update promptly. Start with internet-facing services. The update addresses Java4Shell (CVE-2026-114938), which can let an attacker run code in some affected services. Java4Shell affects certain 64-bit x86 builds of OpenJDK 17, 21, 25, and 27, and a specific Oracle Java 8 performance build. The November update also includes separate fixes for Java 8 and 11. Java 6 is outside the advisory's listed versions and is past regular security support. Plain-language summary Technical advisory Check the Java your service usesIf you have received an email notification from us, it is likely that we have detected java running on your server at some point. So you are likely affected by this issue. Check the Java path in the service configuration and run that executable with -version. Your login shell can use a different Java. If your application bundles Java or runs in a container, check the runtime it ships with. Update and restartUpdate to a patched build of the same Java major your application already uses. Use your package manager for a package-managed JDK, or your application vendor's update for bundled Java. For containers, update the image and redeploy. For a standalone Linux JDK, download and review RimuHosting's install-jdk.sh from https://github.com/pbkwee/install-jdk To preview the update for a service already on Java 21, run: sudo bash ./install-jdk.sh --jdk-version 21 --dry-run Replace 21 with the major your service uses. If the plan is correct, rerun without --dry-run. On 32-bit x86 Linux the installer offers Corretto 11 and requires glibc 2.12 or newer. If your application requires an older Java or the installer reports an incompatible OS, open a ticket before changing the Java major. Confirm the service points to the patched JDK, restart it, and verify the application is healthy and using the expected build. If you'd like a hand, pop in a RimuHosting support ticket with your server name, application, and Java version if you know it. | |
Log in to subscribe to changes to this notice.
Set your operation notice contact details for future notifications.