Two critical PHP vulnerabilities put websites and servers at risk
Website owners, businesses, developers and server administrators are being urged to update their PHP installations following the release of critical security patches on 21 October 2026.
The PHP development team has addressed two vulnerabilities, CVE-2026-109618 and CVE-2026-109619, each rated 9.2 out of 10 under the CVSS v4.0 severity scale. Successful exploitation could allow an unauthenticated attacker to execute malicious code remotely on an affected server.
Security advisories have highlighted the urgency of applying the patches, particularly for internet-facing servers running vulnerable PHP versions. Official PHP security advisory.
What are the vulnerabilities?
The two vulnerabilities affect the PHP runtime, the software responsible for executing PHP code used by websites and web applications.
CVE-2026-109618 – Remote code execution through memory corruption: Improper handling of out-of-memory conditions can leave internal memory in an unsafe state, potentially allowing an attacker to execute malicious code.
CVE-2026-109619 – Remote code execution through stale global state: PHP may retain references to memory that should no longer be in use, creating an opportunity for an attacker to exploit the affected process.
Both flaws can expose vulnerable servers to serious security risks. Depending on the server's configuration and the privileges available to the PHP process, a successful attack could threaten website files, databases and other accessible resources.
How PHP vulnerabilities can lead to malware infections
PHP is widely used to build and operate websites, content management systems and online applications. When attackers exploit weaknesses in PHP, they may gain an entry point into the underlying server.
Once access is obtained, attackers may attempt to:
Upload malicious files or web shells to maintain unauthorised access.
Inject harmful code into legitimate website files.
Steal database credentials, customer information or other sensitive data.
Redirect website visitors to fraudulent or malicious pages.
Install scripts that send spam, distribute malware or consume server resources.
Create unauthorised accounts, scheduled tasks or other persistence mechanisms.
A vulnerable PHP installation does not automatically mean a website is infected with malware. However, leaving a vulnerable system unpatched increases exposure to attacks. Organisations should update their systems and investigate suspicious activity where compromise is suspected.
Which servers and websites are affected?
The vulnerabilities affect PHP installations that process web requests, including configurations using PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP and LiteSpeed.
Websites using platforms such as WordPress, Joomla, Drupal, and custom PHP applications may also be exposed when their hosting environment runs a vulnerable PHP version.
The PHP project has released these fixed versions:
| PHP branch | Patched version |
|---|---|
| PHP 8.5 | 8.5.12 |
| PHP 8.4 | 8.4.27 |
| PHP 8.3 | 8.3.36 |
| PHP 8.2 | 8.2.35 |
PHP 8.1 and earlier versions no longer receive regular security updates from the PHP project. Organisations using these older versions should plan to migrate to a supported release or confirm that an appropriate security backport is available from their vendor.
The correct update may depend on the Linux distribution, hosting control panel and PHP packages installed on the server. Always verify the applicable vendor advisory before updating.
What should website owners and server administrators do?
Bramwa Tech Solutions recommends taking the following steps to reduce exposure to these vulnerabilities.
1. Back up your systems. Create a verified backup or server snapshot before making significant changes. Ensure that recovery procedures are available.
2. Update PHP immediately. Install the appropriate patched packages through your Linux distribution's package manager or hosting control panel.
3. Restart the relevant services. Depending on your configuration, restart PHP-FPM, Apache or the applicable web service so that the updated code is loaded by running processes.
4. Verify every PHP installation. Check the PHP version used by command-line tools and the version serving web requests. Servers may have several PHP versions installed, and updating one does not necessarily update all of them.
5. Update website software. Install available security updates for content management systems, plugins, themes, frameworks and other application dependencies.
6. Review server activity. Investigate unfamiliar files, unexpected administrative accounts, suspicious cron jobs, unusual processes, unexplained outbound connections and abnormal CPU or memory consumption.
7. Strengthen your security controls. Restrict administrative access, use multi-factor authentication where available, maintain least-privilege permissions and consider a web application firewall. These measures provide additional protection but do not replace the PHP security update.
If you suspect that a server has already been compromised, updating PHP alone may not remove malware or eliminate unauthorised access. Consider isolating the affected system where appropriate, preserving logs and engaging a qualified security professional to investigate and recover the environment.
Protecting your website is an ongoing responsibility
Cybersecurity is not a one-time task. Vulnerabilities can emerge in programming languages, operating systems, applications and third-party components, making regular maintenance essential for businesses that depend on digital services.
For organisations hosting websites on VPS, VDS or dedicated servers, responsibility for applying updates may rest with the server administrator or hosting customer. A hosting provider may supply the infrastructure without managing every software component installed on it.
Keeping systems patched, monitoring activity and maintaining reliable backups can significantly improve resilience against cyber threats.
How Bramwa Tech Solutions can help
Bramwa Tech Solutions encourages businesses, website owners, and system administrators to treat critical security advisories as a priority.
Whether you operate a business website, an online platform or a self-managed server, regular updates and proactive security checks are essential to protecting your digital assets.
Do not wait for a website to display suspicious behaviour before taking action. Check your PHP version, apply the appropriate security patches, and review your server's security posture today.
Stay updated. Stay protected. Keep your business online.
Technical reference: Official PHP security advisory | PHP security advisories on GitHub