Critical PHP security release today: our timeline for getting you patched
Today, November 19, between 14:00 and 14:30 UTC, the PHP project will release security fixes for every supported version: 8.2, 8.3, 8.4, and 8.5. The most serious issue is rated critical. We’re following the releases from PHP and CloudLinux, and we’ll install the fixes across our platform as they arrive. On Hostinger hosting plans we’re handling the update, and if you run PHP yourself on a VPS, you can prepare now.
In short:
- What happened: The PHP security team announced a coordinated release that fixes several vulnerabilities, some of which are critical.
- What we know: PHP says the critical issues need a non-default configuration or an uncommon setup. Until the details are out, we can’t tell which setups those are.
- What we’re doing: We’ll install each fix across our servers as soon as CloudLinux releases it, starting with the most widely used PHP versions. Estimated timings are below.
- What you need to do: If your site is on a Hostinger hosting plan, you don’t need to do anything. We install PHP’s fix on our servers for you.
What we know so far
PHP has announced the release date and severity, but hasn’t published full details of the vulnerabilities yet. PHP says the critical issues need an unusual setup. One affected setting is already known, but the full list won’t be public until the advisory is out, so we’re treating every site as potentially affected.
The fixed versions are expected to be 8.2.36, 8.3.37, 8.4.28, and 8.5.13. We’ll confirm them once PHP publishes the release, together with the CVE numbers and severity scores.
These issues are in PHP itself, so the fix has to come from a new PHP build. Updating your CMS, theme, or plugins won’t change anything.
When fixes should become available
Our PHP builds come from CloudLinux, so we can only start installing a fix once its packages are available. These are our current estimates for package availability, counted from the moment PHP publishes the release:
- First packages: about 1.5 to 2 hours, so roughly 15:30 to 16:30 UTC
- Remaining versions the PHP project still supports: about 3 hours, so roughly 17:00 to 17:30 UTC
- Older versions that need backported fixes, such as 8.1 and earlier: about 6 hours, so roughly 20:00 to 20:30 UTC
If PHP publishes within its 14:00 to 14:30 UTC window, the first packages should appear between about 15:30 and 16:30 UTC, the remaining supported versions between about 17:00 and 17:30 UTC, and the older versions between about 20:00 and 20:30 UTC. Once packages are available, we install them across our servers and post here and on our status page when the fix is deployed.
These are estimates, and we’ll tell you if they change. When each stage finishes, we’ll post the actual time in UTC here and on our status page.
What you need to do
On Hostinger hosting plans (every plan except VPS): You don’t need to do anything. We install the fix on our servers, and we’ll tell you in this post and on our status page as soon as it’s deployed.
If you run PHP yourself on a VPS, our platform patching doesn’t reach your server, so the update is yours to apply. You can prepare now:
- List everywhere PHP runs: servers, containers, base images, and CI runners.
- Plan your update or rebuild so you can start as soon as the release is out. For containers, rebuild on a patched base image.
- When the advisory is published, check whether your configuration matches the vulnerable setups. Update everything, and start with the servers that match.
We’ll add exact versions and any interim configuration change here as soon as PHP shares them.
What happens next
We’ll update this post as news arrives, starting with what PHP’s advisory means for our customers, and again as each rollout stage finishes. In the meantime, our Customer Success team is available 24/7 via live chat in the Hostinger dashboard if you have questions about your site.