03.03LogsSecurity
PHP2Shell - The Critical PHP Vulnerabilities That Have the FBI, NSA and CISA Sounding the Alarm
Oct 22, 2026 · Digitalis Creative Inc.

Two critical PHP remote code execution vulnerabilities dubbed PHP2Shell have prompted emergency advisories from the FBI, NSA, and CISA. Every PHP server on the internet is potentially affected. Here is what you need to know and what to do right now.
What Happened
On October 20, 2026, details of two critical PHP vulnerabilities leaked ahead of a coordinated disclosure date of October 22. By October 21, the FBI Cyber Division, NSA, and CISA had all issued urgent emergency advisories — a rare convergence that underscores the severity. PHP patches dropped the same day, but the exploit code was already circulating.
Cybersecurity firm watchTowr reproduced CVE-2026-109618 before the official patches even landed. Wiz demonstrated successful attacks against WordPress, Drupal, and Joomla installations. A total of 42 organizations across 6 advisory groups issued warnings within 24 hours.
This is not a theoretical risk. This is active, in-the-wild exploitation.
The Two Vulnerabilities
CVE-2026-109618 — RCE via Out-of-Memory Corruption
When PHP runs low on memory during a request, it triggers an out-of-memory (OOM) handler. This vulnerability exploits a flaw where the OOM handler can interrupt PHP while internal request data is only partially initialized. Multipart form parsing — the kind every file upload form uses — is one confirmed trigger.
An attacker sends a crafted multipart request designed to push PHP's memory usage to the edge. When the OOM handler fires at the exact right moment, it corrupts the internal request structures. The attacker then leverages that corruption to execute arbitrary code on the server.
Think of it like this: Imagine a bank vault that briefly unlocks its door whenever the fire alarm goes off. The attacker just needs to pull the fire alarm at the right moment.
CVE-2026-109619 — RCE via Stale Global State
PHP processes requests through worker threads that get recycled. This vulnerability exploits a flaw where internal state tied to one request can outlive its freed memory. When a later request on the same worker reads that stale pointer before it is reset, the attacker controls what it finds.
The session upload progress mechanism (session.upload_progress) is one confirmed attack path. Setting session.upload_progress.enabled=0 in your php.ini blocks that specific vector, but the underlying flaw has other potential triggers that remain unconfirmed.
Think of it like this: Imagine leaving your house key under the mat, throwing the mat away, but the new tenant finds the key still works because no one changed the locks.
Who Is Affected
Both vulnerabilities affect:
- PHP 8.2.x below 8.2.35
- PHP 8.3.x below 8.3.36
- PHP 8.4.x below 8.4.27
- PHP 8.5.x below 8.5.12
If you are running PHP on a web server — which powers roughly 77% of all websites — you are likely affected. WordPress alone runs on 43% of all websites. Drupal, Joomla, Laravel, Symfony, Magento, and every custom PHP application are all in scope.
What To Do Right Now
1. Check Your PHP Version
``bash
php -v
` If your version is below the patched versions listed above, you are vulnerable. 2. Update PHP Immediately Most hosting providers offer PHP version management through cPanel's MultiPHP Manager, Plesk, or similar control panels. Update to the latest patched version for your branch: PHP 8.2 → 8.2.35 PHP 8.3 → 8.3.36 PHP 8.4 → 8.4.27 PHP 8.5 → 8.5.12 3. Temporary Mitigation (If You Cannot Update Yet) Add this to your php.ini to block one confirmed attack vector: `ini session.upload_progress.enabled = 0 ``
Important: This only blocks the session upload progress attack path for CVE-2026-109619. It does not fully mitigate either vulnerability. Update PHP as soon as possible.
4. Check Your Logs
Look for unusual multipart POST requests, especially to endpoints that do not normally handle file uploads. Look for unexpected memory-related errors in your PHP error logs.
5. Review Your WAF Rules
If you use a Web Application Firewall (Cloudflare, ModSecurity, etc.), check for updated rulesets that address these CVEs. Major WAF providers have been releasing emergency rules.
Why This Matters
Remote Code Execution means an attacker can run any command on your server. That means:
- Data theft — database dumps, user credentials, payment information
- Backdoor installation — persistent access even after patching
- Lateral movement — using your server to attack others on the same network
- Ransomware deployment — encrypting your files and demanding payment
- Supply chain attacks — injecting malicious code into software you distribute
The combination of a massive attack surface (77% of web servers), weaponized exploits already in circulation, and the relatively low complexity of the attack makes this a worst-case scenario for PHP security.
The Bigger Picture
This is not the first time PHP has had critical vulnerabilities, but the speed and scale of the response is notable. When the FBI, NSA, and CISA all issue emergency advisories within hours of each other, it signals intelligence that active exploitation is already happening at scale.
The PHP project has historically been responsive to security issues, and the patches were available within a day of the leak. The challenge now is adoption — getting millions of servers updated before attackers can exploit them.
For those of us who build and maintain web infrastructure, this is a reminder that the software supply chain is only as strong as its weakest link. A language-level vulnerability bypasses every application-level security measure you have in place. Your WAF, your input validation, your parameterized queries — none of it matters if the attacker can execute arbitrary code before your application even runs.
Our Response
At Digitalis Creative, we immediately audited our infrastructure upon learning of these vulnerabilities. Our flat-file CMS architecture means we have a smaller attack surface than database-driven systems like WordPress, but PHP-level vulnerabilities affect every PHP application regardless of architecture.
We have updated our PHP installations and verified our configurations. We encourage every web developer and server administrator to do the same — today, not tomorrow.
Update your PHP. Check your logs. Stay vigilant.
Have questions about securing your PHP infrastructure? Contact us — we are happy to help.