This week's NGINX and PHP vulnerabilities on our shared hosting servers and VPS platform. What it means for you, and the steps we ask every customer to take.
Several serious vulnerabilities were published this week in software that runs a large part of the web, including our own platform. Below is what happened, what we did, and what we ask of you.
A faster pace of vulnerabilities
Security flaws in widely used software used to arrive every few weeks. Now new critical vulnerabilities are published every week, and some weeks almost every day. Part of the reason is that both researchers and attackers now use AI tools to find weaknesses in code and to turn them into working exploits.
The time between a flaw being made public and the first attacks has also become much shorter. In many cases it is now a matter of hours, not weeks. For anyone who runs servers, that means updates can no longer wait for the next maintenance window.
Our team follows these advisories every day, and works to apply fixes across all our servers as soon as they are available. This week was a clear example.
What was published
- NGINX, CVE-2026-123007 (18 November). A flaw in NGINX’s HTTP/2 handling that can let a remote attacker run code on the server without logging in.
- PHP security release (19 November). PHP fixed 18 vulnerabilities, including CVE-2026-115560 and several other flaws that can lead to remote code execution. Fixed versions are 8.2.36, 8.3.37, 8.4.28 and 8.5.13.
- CVE-2026-99312. Over the same days we saw malware on some customer VPS servers exploiting this vulnerability.
What we did
Shared hosting (Plesk). We updated NGINX and PHP on all shared hosting servers as soon as the fixes were available, and applied the recommended workarounds where a fix had not yet been released. The upgrades caused short interruptions on some servers while services restarted. We apologise for any inconvenience this caused.
VPS platform. We updated the host machines that run our VPS service. Affected VPS servers were rebooted as part of this work. Where we found malware on a VPS, we contacted the owner directly.
Our own systems. Our website, client area and network services were checked and updated in the same way.
All shared hosting servers are now running patched software. We continue to monitor all our systems closely.
What we ask of you
Turn on two-factor authentication (2FA), and keep it on. Most break-ins start with a stolen or reused password. With 2FA, a password alone is not enough to get into your account. Turn it on in the client area under your account’s security settings, and in Plesk if you manage a hosting account.
VPS owners: patch your servers now. A VPS is managed by its owner, and we cannot update the software inside it for you. Please:
- update the operating system and all packages (
apt update && apt upgrade on Ubuntu and Debian, dnf upgrade on AlmaLinux and Rocky Linux);
- check that NGINX, PHP and any other web software are at the fixed versions, and restart them;
- change passwords and SSH keys if you have any doubt that the server was accessed;
- look for unknown processes, cron jobs and user accounts.
If you need help, or you think your server may have been compromised, contact our support team and we will help you check it.
Thank you for your trust.
The Host.al team