Home > Control panel > Operations notices

Related Links

Notice Links:

Notices

Java security update required (Java4Shell/CVE-2026-114938)

PostedWed, 18 Nov 2026 21:10 PM UTC
Wed, 18 Nov 2026 16:10 PM EST
Last UpdateFri, 20 Nov 2026 19:47 PM UTC (29 hours ago)
Fri, 20 Nov 2026 14:47 PM EST
StatusOpen

If your server runs Tomcat, WildFly, Jira, Jenkins, or another Java application, check which Java build it uses and apply your vendor's November 2026 security update promptly. Start with internet-facing services. Java4Shell (CVE-2026-114938) can let a remote attacker run code without signing in on some affected applications.

Java4Shell requires both an affected Java build and an x86-64 CPU with AVX-512 VBMI available to Java. Affected releases include unpatched OpenJDK 17 builds starting at 17.0.6, and unpatched builds of Java 21, 25, and 27. Oracle also lists a specific Java 8 Enterprise Performance Pack build. The November updates contain separate security fixes for Java 8 and 11. Java 6 is past regular security support.

Plain-language summary from CISA
https://content.govdelivery.com/accounts/USDHSCISA/bulletins/4332a87

Technical advisory from Oracle
https://www.oracle.com/security-alerts/cspunov2026.html#AppendixJAVA

Check the Java your service uses

If we emailed you about this issue, our records indicate Java has run on your server. Check what is running now to determine whether your application is affected.

Find the Java executable in the service configuration and run it with -version. Your login shell may use a different Java. For containers and applications that bundle Java, check the runtime inside the image or application. Compare the full build or package version with your vendor's advisory.

On Linux, run this on the VM or server running Java to check the CPU features available there.

grep -m1 '^flags[[:blank:]]' /proc/cpuinfo | tr -s '[:space:]' '\n' | grep -Ex 'avx512f|avx512bw|avx512vbmi|bmi2'

All four flags must be present for Java4Shell's CPU requirement to be met. Apply your vendor's November security updates for the other Java fixes as well.

Update and restart

Update to a patched build of the same Java major your application uses. Use your package manager for a package-managed JDK, or follow your application vendor's update instructions for bundled Java. For containers, update the image and redeploy.

For a standalone Linux JDK, you can download and review RimuHosting's Corretto installer.
https://github.com/pbkwee/install-jdk#get-started

For a service already using Java 21, preview the system-wide install with this command.

sudo bash ./install-jdk.sh --jdk-version 21 --dry-run

Replace 21 with the major your service uses. If the plan looks right, rerun without --dry-run. If your application needs an older Java or the installer reports an incompatible system, open a ticket before changing major versions.

Confirm the service points to the patched JDK, restart it, and check that it is healthy and running the expected build. If you rely on automatic package updates, verify both the installed build and the running service.

If you need more time to patch

For affected OpenJDK builds, add -XX:-UseBASE64Intrinsics to the service's JVM startup options and restart the service. This temporarily disables the affected Java code. Apply the security update as soon as you can.

If you'd like a hand, pop in a RimuHosting support ticket with your server name, application, and Java version if you know it.
https://rimuhosting.com/support/sindex.jsp

#

RimuHosting PHP updates 19th Nov 2026 (including phpAfterShell)

PostedThu, 19 Nov 2026 22:35 PM UTC
Thu, 19 Nov 2026 17:35 PM EST
Last UpdateThu, 19 Nov 2026 23:09 PM UTC (50 hours ago)
Thu, 19 Nov 2026 18:09 PM EST
StatusOpen

Multiple critical security vulnerabilities in PHP have been released, including one known as phpAfterShell. They have been described as critical, with potential to allow an attacker to run malicious code on an affected server without logging in.

For details of the posted vulnerabilities, see https://github.com/php/php-src/security/advisories

This includes CVE-2026-115560, CVE-2026-129182, CVE-2026-126714, CVE-2026-129289, CVE-2026-129474, CVE-2026-129481, CVE-2026-129496, CVE-2026-129291

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.

Emergency maintenance: proactive security updates

As an initial response to the vulnerabilities we have a process to install the latest PHP packages available from 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 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:
https://rimuhosting.com/cp/serverpatchstate.jsp?issue_id=8221642932

Details

If 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.

A build date of 19th November 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.

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 yourself

These 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 packages

These 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 updates

On 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:
https://almalinux.org/ko/blog/2026-10-21-php2shell-cve-2026-109618-cve-2026-109619/

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.

2a. Mitigations

If your application does not need the to track upload progress, set the following in php configuration and restart all php services...

session.upload_progress.enabled = 0

This removes the easiest path to the flaw, not the flaw itself. You still need the upgrade.

Also limit untrusted data your application stores in sessions. If session tracking is not needed for your site, disabling this may also help. The following are possibilities and should get targeted testing in your environment.

# disable autmatic session tracking
session.auto_start = 0
# disable url based session tracking
session.use_trans_sid = 0
session.use_only_cookies = 1

3. Restart the processes using PHP

Package 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 result

Run 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 updates

Older 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

#

VM host restarts re CVE-2026-98432 | TCP Flaw

PostedWed, 4 Nov 2026 20:58 PM UTC
Wed, 4 Nov 2026 15:58 PM EST
Last UpdateWed, 4 Nov 2026 20:58 PM UTC (17 days ago)
Wed, 4 Nov 2026 15:58 PM EST
StatusOpen

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 kernels

We 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 kernels

Where a server uses its own kernel, for example when booting with pvgrub, customers should check with their Linux distributor for applicable security updates.

#

host1163.rimuhosting.com operations notice

PostedFri, 20 Nov 2026 01:36 AM UTC
Thu, 19 Nov 2026 20:36 PM EST
Last UpdateFri, 20 Nov 2026 03:27 AM UTC (45 hours ago)
Thu, 19 Nov 2026 22:27 PM EST
StatusClosed
Affected service

Fri, 20 Nov 2026 03:26 AM UTC: All services restored.

Fri, 20 Nov 2026 03:15 AM UTC: VPSs are starting back up.

Fri, 20 Nov 2026 02:58 AM UTC: Remote hands found an issue with one of the power connectors on the server. That has been remedied and server is alive again.

While the server is under maintenance we are completing some scheduled updates as well. Full service should be restored in approximately 30 minutes.

Fri, 20 Nov 2026 01:59 AM UTC: There was adjacent work occuring in the cabinet, We have reached out to remote hands to check network connections to this server.

host1163.rimuhosting.com is not responding normally.  We are investigating and may have it restarted.

#

RimuHosting VMs PHP2Shell CVE CVE-2026-109618 and CVE-2026-109619

PostedWed, 21 Oct 2026 23:02 PM UTC
Wed, 21 Oct 2026 19:02 PM EDT
Last UpdateFri, 20 Nov 2026 01:02 AM UTC (48 hours ago)
Thu, 19 Nov 2026 20:02 PM EST
StatusClosed

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:
https://www.malwarebytes.com/blog/bugs/2026/10/php2shell-why-websites-are-going-offline-for-emergency-security-updates

Emergency maintenance: PHP2Shell security updates

As 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:
https://rimuhosting.com/cp/serverpatchstate.jsp?issue_id=8221642932

About php2shell

If 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:
https://www.php.net/archive/2026.php#2026-10-21-5

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:
https://ubuntu.com/blog/php2shell-vulnerability-fixes-available

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 yourself

These 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 packages

These 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 updates

On 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:
https://almalinux.org/ko/blog/2026-10-21-php2shell-cve-2026-109618-cve-2026-109619/

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 PHP

Package 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 result

Run 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 updates

Older 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

#