Black October: Critical PHP and Node.js Flaws Test How Fast Websites Can Be Patched
Las Vegas, United States - October 27, 2026 / Whisenhunt Media /
LAS VEGAS, Oct. 27, 2026. Two of the most widely used programming platforms on the web disclosed critical security flaws on the same day this week, and the speed of what followed is forcing businesses to ask a question most have never had to answer: how fast can their website actually be patched?
On October 21, the PHP project shipped emergency fixes for two vulnerabilities, tracked as CVE-2026-109618 and CVE-2026-109619 and nicknamed PHP2Shell. The flaws sit in the PHP runtime itself, which underpins WordPress, Drupal, Magento and Laravel, and allow an attacker to run code on a server without logging in. Every PHP version released since 5.4 is affected. Researchers at watchTowr reported live exploitation attempts nineteen minutes after the patches were published. Amazon's threat intelligence team later traced one attempt to October 17, four days before public disclosure, and Cloudflare reported attempts climbing from tens of thousands to millions within a day.
Hours later, Node.js released fixes for ten vulnerabilities across its supported versions. The most serious, CVE-2026-111497, is a flaw in the Brotli decompression code bundled with Node that the project says can lead to remote code execution. Within two days, Imperva's red team published a proof of concept it called Node2Shell.
Parts of the security community have started calling it Black October. Both sets of flaws were found with help from frontier AI models, and researchers warn that the same tools shorten the path from discovery to attack. "Millions of unrelated services depend on a comparatively small collection of languages, runtimes, libraries, and infrastructure components," Sai Molige, senior manager of threat hunting at Forescout, told Cybernews. He cautioned that "millions of attempted attacks do not mean millions of compromised websites," but said organizations need to patch faster to keep pace.
Patching, it turns out, is harder than it sounds. Updating a WordPress or Laravel installation does not update the PHP runtime underneath it, and the vulnerable code stays loaded in memory until every server process is restarted. "The only mitigation is patching / upgrading PHP," PHP core developer Gina Peter Banyard said, as a widely shared configuration workaround was walked back by the firm that first proposed it. For Node.js, Shane Barney, chief information security officer at Keeper Security, warned that the platform "runs the back end of many large platforms, and these applications typically hold database credentials, API keys, and tokens."
For many companies, the gap is not technical skill but process. A typical business website is built by one vendor, hosted by another and maintained through support tickets, a chain that can take days to complete while exploit code circulates within hours.
Some firms are trying a different model. Whisenhunt Media, a Las Vegas video production and digital marketing agency, runs its own and its clients' websites as code repositories with automated tests, using software agents to prepare and test updates that a person then approves. Founder Ben Whisenhunt said the Node.js alert reached his team overnight. "We received an email from Stripe saying that Node.js was affected as well, and we received that email at 3 am. By 10 am, all of our client sites, our sites, and all systems were updated and secure," he said. "That's the speed that we need to be working at when it comes to being able to address cybersecurity issues. In the future, that window is going to have to close even further and be fully agentic."
Security vendors agree that the window is narrowing, even as they caution against assuming every flaw will be exploited at scale. Sansec, which tracks attacks on online stores, said on October 22 that mass exploitation of PHP2Shell looked less likely than it had on release day, because public exploits require conditions a default installation does not have. Google Cloud's guidance was blunt on the remedy: firewall rules help, but upgrading PHP and redeploying is "required to fully resolve these vulnerabilities."
Fixed versions are PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35, and Node.js 26.12.1, 24.22.1 and 22.23.4. PHP 8.1 and Node.js 20 and earlier will not receive fixes. A longer analysis, including a timeline of both disclosures and the steps a complete patch requires, is available on the Whisenhunt Media blog.
About Whisenhunt Media
Whisenhunt Media is an Emmy Award-winning video production and digital marketing agency based in Las Vegas, Nevada. Since 2017 the agency has combined cinematic video production with web development, SEO and AI visibility, paid advertising, social media and experiential marketing for SaaS companies and medium-to-large businesses. Learn more at whismedia.com.
Media Contact
Whisenhunt Media
contact@whismedia.com
(702) 832-7882
7912 Mountain Lilac St, Las Vegas, NV 89113
whismedia.com
Contact Information:
Whisenhunt Media
7912 Mountain Lilac Street
Las Vegas, NV 89113
United States
Ben Whisenhunt
+1 (702) 832-7882
https://whismedia.com