
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 (7 hours 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. | |
| Posted | Wed, 4 Nov 2026 20:58 PM UTC
Wed, 4 Nov 2026 15:58 PM EST |
|---|---|
| Last Update | Wed, 4 Nov 2026 20:58 PM UTC (14 days ago)
Wed, 4 Nov 2026 15:58 PM EST |
| Status | Open |
A critical security vulnerability, identified as CVE-2026-98432, has recently been disclosed in the Linux kernel. The vulnerability affects TCP connection handling and may allow a remote attacker to compromise an affected system. Out of an abundance of caution, we will be restarting our VM hosts so they are running a patched kernel. This will result in VMs running on that host also being restarted. The VMs will restart with the current/latest/patched kernel on the VM's selected kernel version. Fixed kernelsWe have patched all our currently supported RimuHosting VM kernels, and updated versions are now available. Our 4.14 kernel has also been patched, and we expect to make that available shortly. Older kernels, prior to 4.4, are not affected by this vulnerability. Should you wish to restart your VM prior to the host restart, you can select an updated kernel and arrange a reboot using our kernel selector in the control panel: Kernel selection page: https://rimuhosting.com/cp/vps/kernel.jsp You can check which kernel your VM is currently running using the command uname -r. Other kernelsWhere a server uses its own kernel, for example when booting with pvgrub, customers should check with their Linux distributor for applicable security updates. | |
| Posted | Wed, 21 Oct 2026 23:02 PM UTC
Wed, 21 Oct 2026 19:02 PM EDT |
|---|---|
| Last Update | Sat, 24 Oct 2026 16:22 PM UTC (25 days ago)
Sat, 24 Oct 2026 12:22 PM EDT |
| Status | Open |
Two critical security vulnerabilities in PHP, known as PHP2Shell (CVE-2026-109618 and CVE-2026-109619), can allow an attacker to run malicious code on an affected server without logging in. PHP powers websites and applications such as WordPress, Moodle and Joomla, as well as parts of hosting panels such as cPanel and Plesk. Updating your website's plugins or application alone does not update the underlying PHP software. For a plain-language explanation, see Malwarebytes: Emergency maintenance: PHP2Shell security updatesAs an initial response to the PHP2Shell vulnerabilities we have a process to install the latest PHP packages available from the server's existing package repositories and restart the services using PHP. Websites may be briefly interrupted during those restarts. Older, unsupported distributions are outside the scope of this first pass. Hosting panels, custom PHP installations and containers may also need separate work. We are still working on options for those servers. You can access the results of the work at: About php2shellIf your VM serves PHP websites, please check for the security updates now. Install the patched packages and restart the processes running PHP. Please do not wait for our checking tool. The PHP project released fixes in 8.2.35, 8.3.36, 8.4.27 and 8.5.12. Linux distributions may instead apply the fixes to an older PHP version while keeping its existing version number. Check the complete package version against your distribution's security advisory. PHP's security advisory: A build date of 21 October 2026 or later is not proof that PHP is patched. Also, php -v reports the command-line PHP installation, which may differ from the PHP version used by your websites. For example, Ubuntu 24.04's fixed package is 8.3.6-0ubuntu0.24.04.13, despite its PHP version number being below 8.3.36. Ubuntu's package versions and update guidance: If a patched package is unavailable, consider temporarily removing public access to affected PHP applications. A WordPress maintenance plugin or login page is insufficient: some attack paths run before the application's own code. Updating your server yourselfThese instructions are a starting point for servers using maintained package repositories. Servers with old operating systems, hosting panels, custom PHP builds or containers may need a different approach. Before updating, check that you have a current backup and access to your VM's console. Package updates and restarts can briefly interrupt websites and other services. Run the commands over SSH. If you are already logged in as root, omit sudo. 1. Identify your operating system and PHP packagesThese commands display operating-system information and the command-line PHP version: cat /etc/*release /etc/debian_version 2>/dev/null php -v On Debian or Ubuntu, list matching packages: dpkg-query -W -f='${Package} ${Version}\n' 'php*' 'libapache2-mod-php*'
On AlmaLinux, Rocky Linux, RHEL or CentOS: rpm -qa '*php*' If php -v reports "command not found", that does not establish that your websites do not use PHP. Hosting panels and custom installations may store their own PHP binaries elsewhere. 2. Install available updatesOn Debian or Ubuntu, refresh the package information and preview the updates: sudo apt-get update && sudo apt-get -s upgrade If refreshing the package information reports repository or signature errors, resolve those before continuing. Review the proposed changes, then install the updates: sudo apt-get upgrade Check whether any PHP packages were held back. If they were, the update may be incomplete. dist-upgrade can resolve additional dependencies, but it can also remove packages, so review its proposed changes before using it. On AlmaLinux, Rocky Linux or RHEL using DNF: sudo dnf --refresh upgrade On an installation using YUM: sudo yum clean all sudo yum update Review the package transaction before confirming it. These commands update packages from your configured repositories; they do not guarantee that those repositories contain the PHP2Shell fixes. "No updates available" is not confirmation that your server is safe. The fix may not yet be published for your distribution, your PHP stream may no longer receive updates, or PHP may come from another provider. AlmaLinux's response, for example, distinguishes supported and retired PHP streams: If you use cPanel, Plesk or another hosting panel, follow that vendor's PHP update procedure too. Updating the operating system's default PHP package may leave the versions serving your websites unchanged. 3. Restart the processes using PHPPackage updates sometimes restart services automatically. Do not assume that happened successfully. Once patched packages are installed, rebooting the VM is a straightforward way to replace running processes: sudo reboot This interrupts all services on the VM. Confirm it returns and your websites work. Alternatively, restart the relevant services individually. On Debian/Ubuntu, for example, if you use PHP 8.3 FPM: sudo systemctl restart php8.3-fpm Replace 8.3 with your installed version. On RPM distributions, the service is commonly: sudo systemctl restart php-fpm These are examples: use your actual service names. Very old systems may use service or /etc/init.d/ instead of systemctl. If Apache runs PHP directly through mod_php, restart Apache instead: its service is commonly called apache2 on Debian/Ubuntu or httpd on RPM distributions. Restart every PHP version serving websites, plus long-running PHP workers. Restarting nginx alone does not restart PHP-FPM. Containers need their own updated images and replacement processes. 4. Check the resultRun the package-listing commands again and compare the installed revisions with the advisory for your package provider. Visit your websites and check that important functions still work. On Linux, this command can help identify PHP and web-server processes and their start times: ps -eo pid,lstart,args | grep -E '[p]hp-fpm|[a]pache2|[h]ttpd|[n]ginx' A recent process start time helps confirm a restart; it does not prove that the process loaded patched software. Older servers or unavailable updatesOlder servers may need migration to a maintained operating system, an extended-support service, or a carefully planned PHP upgrade. Some older Ubuntu releases have fixes through Ubuntu Pro/ESM, where that coverage is enabled. We are investigating options for older installations, including third-party repositories such as Sury. Please do not add repositories or switch PHP versions blindly: compatibility and available fixes depend on the operating-system release and application. If you cannot obtain a confirmed fix, remove public access to the affected PHP applications while arranging an update. If you would like RimuHosting to assist you migrating your server to a currently supported distro - which may require a reinstall and migration - please reach out to us. We can assist with these as time permits. The process is described at https://rimuhosting.com/knowledgebase/rimuhosting/migration | |
| Posted | Thu, 12 Nov 2026 02:41 AM UTC
Wed, 11 Nov 2026 21:41 PM EST |
|---|---|
| Last Update | Thu, 12 Nov 2026 03:12 AM UTC (7 days ago)
Wed, 11 Nov 2026 22:12 PM EST |
| Status | Closed |
| Affected service | |
Thu, 12 Nov 2026 03:11 AM UTC: All changes are complete, redundancy has been restored. host1105.rimuhosting.com requires a change to its storage that will temporarily affect disk redundancy. No service impact is expected. There may be some extra io latency over the next few hours. The work will start shortly, and is expected to complete within 2-3 hours. | |