Active PHP2Shell attacks threaten millions of web servers
Two critical PHP vulnerabilities are under active attack. Learn how to audit your web infrastructure and patch servers to prevent remote takeover.
On October 26, 2026, the U.S. Cybersecurity and Infrastructure Security Agency (opens in a new tab) added two critical PHP vulnerabilities to its Known Exploited Vulnerabilities catalog. The agency made this move after confirming that attackers are actively exploiting the flaws in the wild. PHP is a server-side scripting language that runs on roughly 70% of all websites. A vulnerability at this fundamental level means external attackers can take control of a web server. Business owners must treat this as an immediate threat to their digital operations.
Security researchers refer to these two flaws collectively as PHP2Shell. They are officially tracked as CVE-2026-109618 and CVE-2026-109619. Both carry a severe risk rating of 9.2 on the CVSS scoring system. The first vulnerability involves memory corruption, while the second stems from a stale internal request state.
The technical details matter because of what they enable. Both flaws facilitate unauthenticated remote code execution. This means an attacker can send a specially crafted request to a website and run malicious commands on the server. They do not need a username, a password, or any prior access to the systems.
The vulnerabilities affect all PHP installations that serve web requests. This includes common server runtimes like Apache with mod_php, PHP-FPM, php-cgi, FrankenPHP, and LiteSpeed. The threat surface is enormous. The Hacker News (opens in a new tab) reported that Censys estimates more than 32.51 million PHP services are still running an affected version globally.
The PHP maintainers released emergency patches on October 21, 2026, according to a separate CISA alert (opens in a new tab). They addressed the issues in PHP versions 8.5.12, 8.4.27, 8.3.36, and 8.2.35. The gap between the patch release and the confirmation of active attacks was only 5 days. This rapid escalation shows how quickly malicious actors weaponize vulnerabilities.
What it means for your business
Small and mid-sized companies often do not know they rely on PHP. The language operates quietly behind the scenes. It runs marketing websites, customer support portals, and internal financial tools. Your technology team or external hosting provider must act immediately to secure these hidden assets.
The first operational step is a complete infrastructure inventory. You need to identify every system running any version of PHP across your organization. This requires checking both public websites and internal applications. CISA notes that PHP is frequently a component of other software, meaning its presence might not be directly observable. These forgotten servers are prime targets for automated attacks.
Once identified, your team must apply the patches without delay. Internet-facing systems require the highest priority because they are exposed to the public internet. If a system cannot be updated immediately, CISA advises taking PHP-based systems offline entirely until they can be patched.
This strict guidance also applies to applications running on PHP 8.1 or older unsupported versions. Those legacy versions will not receive a security fix for PHP2Shell. Running unsupported software is a business risk that now carries a direct path to compromise. You must migrate those applications to a modern version or retire them.
A web application firewall may provide some protection while your team works on the updates. It filters incoming traffic and can block known malicious patterns. However, a firewall is not a permanent substitute for patching. The root vulnerability remains in the code until the software is upgraded.
The broader software supply chain
The PHP2Shell vulnerabilities highlight a broader issue with how web servers process complex requests. On October 26, 2026, the PHP Foundation also released Windows builds to address a separate out-of-bounds write vulnerability in the Brotli decoder library.
This secondary vulnerability affects Brotli versions 1.0.3 through 1.0.9, 1.1.0, and 1.2.0. It can also result in privilege escalation and unauthenticated remote code execution. The flaw is not limited to PHP. It impacts other widely used projects that include the C library, such as Node.js, Bun, Envoy Proxy, Istio, .NET, and Python.
In PHP Windows builds, the vulnerable decoder is reachable through the cURL extension when automatic HTTP response decompression is enabled. While this is disabled by default in cURL, applications and HTTP client libraries can enable it. This demonstrates how a single vulnerable component can ripple across different programming languages and server environments.
What to watch
Federal agencies face a strict compliance deadline. They have until October 29, 2026, to apply the necessary fixes. Private companies should treat this government timeline as a benchmark for their own security operations. If federal networks must be patched within days, small businesses should aim for the same urgency.
Watch your server logs for specific indicators of compromise. CISA advises monitoring for suspicious activity, including PHP worker processes launching shells. Another red flag is a web server unexpectedly downloading tools. Your technical team should configure automated alerts for these specific behaviors.
Pay attention to advisories from your software vendors. The severity of the PHP vulnerabilities prompted alerts from numerous companies, including Broadcom, Dell, IBM, and Okta. If you use third-party software that relies on PHP, you must wait for the vendor to release an update and apply it immediately.
Infrastructure security depends entirely on visibility. You cannot protect software you do not know you have. These active exploits prove that maintaining an accurate inventory of your web technologies is a strict requirement for doing business safely.