CISA adds PHP2Shell flaws to its KEV catalog as honeypots log working shells
The US cybersecurity agency CISA added two critical PHP remote code execution flaws (CVE-2026-109618 and CVE-2026-109619, together called PHP2Shell) to its Known Exploited Vulnerabilities catalog on October 26, 2026. Federal agencies have until October 29. A Perplexity researcher logged working shells on honeypots.
Federal agencies must patch by October 29
CISA added two critical PHP flaws to its KEV catalog on Monday, October 26, 2026. According to BleepingComputer, both let unprivileged attackers gain remote code execution on unpatched systems through high-complexity attacks. The catalog entries are named "PHP Memory Corruption Vulnerability" (CVE-2026-109618) and "PHP Stale Internal Request-State Vulnerability" (CVE-2026-109619), and both carry a due date of October 29, 2026.
The PHP security team had released fixes on Wednesday, October 21. This piece follows up our October 21 report on the emergency patches: back then the story was a call to update, and now the flaws sit on the official list of exploited vulnerabilities. We do not repeat patched version numbers here; for those, see PHP's official advisories and the earlier article.
A four-stage chain and 35 shells on honeypots
According to BleepingComputer, Perplexity's Adel Karimi was the first to confirm in-the-wild exploitation. SecurityWeek says his honeypots serve ordinary PHP-backed pages from a single-worker PHP 8.4.26 setup running as Apache mod_php. His first report, spanning a little over 26 hours, recorded 30 out-of-memory errors and 11 crashed workers but no code execution. On October 24 his sensors recorded 35 shells across three honeypots: a single IP address was behind three shells on one honeypot, and a second address launched 32 spread over all three.
The attack chained four HTTP request stages. Some stages drained PHP's memory, some exposed memory contents, and the final one executed a shell command. Karimi says the traffic was a close match for a publicly available proof-of-concept and fits exploitation of CVE-2026-109618. SecurityWeek notes that no download of a second-stage payload was seen. Karimi also cautions that the result comes from a deliberately favorable single-worker profile and says nothing about how reliably the exploit works with other worker counts, other PHP builds or other applications.
From attempts tagged as failed to shells that ran
BleepingComputer reports that Cloudflare, Amazon, Hadrian, watchTowr, Previdian and Patchstack all detected exploitation attempts before public disclosure but tagged them as unsuccessful. Amazon Threat Intelligence says attackers began targeting the flaws four days before the patches shipped. SecurityWeek adds that when CISA updated its alert on October 23 with a Sigma detection rule, the agency reported no successful exploitation it had seen. The honeypot data and the KEV listing show the picture has changed since then.
CISA warned, in the words BleepingComputer quotes, that "These types of vulnerabilities are a frequent attack vector for malicious cyber actors" and pose significant risks to federal systems. The directive binds only Federal Civilian Executive Branch agencies, but CISA urges every organization to manage vulnerabilities on a risk basis and to put KEV entries first. Separately, the PHP team shared mitigation on Friday for a third RCE flaw (CVE-2026-115560) that has no patch yet; BleepingComputer says it is exploitable on systems with an unusual combination of configuration and application code. PHP powers roughly 70 percent of websites, and VirusTotal estimates more than 5.1 million exposed PHP hosts, of which about 3.8 million have one or more ports open to attackers.
The articles we read do not mention Türkiye, so this section is commentary
Neither the BleepingComputer nor the SecurityWeek article contains any Türkiye-specific data: no count of exposed PHP servers in the country, no local agency advisory and no exploitation record from Türkiye. This section is therefore not a fact drawn from the sources but explicitly UNALSOFT commentary.
Our reading is that many small business sites in Türkiye run on PHP-based WordPress, WooCommerce or custom software, and that the hosting provider often manages the PHP version. Once a flaw is on record as exploited, updating moves from a 'sometime' list to a 'today' list. That is an inference, not reported data; if you do not know which PHP version your site runs or who applies updates, finding that out comes first.
The UNALSOFT view
The practical takeaway for a business is plain: find out today which PHP version your site runs and who applies the updates, update it together with your hosting provider, and review your plugin and theme list. The flaws are no longer discussed as a theoretical risk; there is an official exploitation record. In web design we treat building sites as maintained systems with monitored versions as core work for this reason. This piece does not replace a security audit, and since the sources hold no Türkiye-specific data we do not propose a local conclusion.
Is your PHP site up to date, and who maintains it?
A short conversation is enough to review your site's PHP version and maintenance routine together.