This is the thirty-second post on LocalPapa Notes. No new tool this time — instead, a security story: on 21 October 2026, PHP shipped an emergency security release for two vulnerabilities that have become known as PHP2Shell.
The short version:
- LocalPapa does not use PHP and is not affected. There is nothing you need to do on this site. Below is how we checked.
- But there is a good chance something around you does run PHP: a WordPress site, the NAS at home, the firewall's admin page at work, an office phone system. That is what this post is really about.
What happened
PHP is a language for writing web servers. WordPress, Drupal, Nextcloud, most hosting control panels and the admin pages of many network appliances are built on it. These two flaws are serious for three reasons:
- No login required. Anyone who can reach the site can try.
- The site does not have to contain a bug. The flaw is in PHP itself, so careful application code does not help.
- They allow remote code execution — in effect, control of the server. Hence the name: from PHP to a shell.
PHP rated both 9.2 out of 10 on CVSS v4.0. Assessments differ somewhat — Red Hat scored them 8.1 — but nobody calls them minor.
| Date (2026) |
Event |
| 17 Oct | AWS reports exploitation attempts, four days before disclosure |
| 20 Oct | Details leak on social media; PHP posts an advance notice |
| 21 Oct | PHP ships 8.5.12, 8.4.27, 8.3.36 and 8.2.35; exploitation and mass scanning seen the same day |
| 23 Oct | PHP announces a related but separate flaw, CVE-2026-115560 (see below) |
| 26 Oct | US CISA adds CVE-2026-109618 to its Known Exploited Vulnerabilities catalog |
| 29 Oct | Palo Alto Networks confirms attackers chaining it with a Linux kernel privilege escalation to get root on internet-exposed firewall management interfaces |
Palo Alto's Unit 42 estimated, from its own telemetry, more than 22.6 million internet-facing PHP instances that are potentially vulnerable.
The two flaws in plain words
CVE-2026-109618: running out of memory leaves half-built data behind. When PHP reads a submitted form ($_POST), it puts each field into an internal table. Researchers found that the table's entry count is incremented before memory for the new entry is allocated. If memory runs out at exactly that point, PHP aborts — but the count already includes an entry that was never set up. Cleanup later treats that entry as real, which gives an attacker a way to steer the program. A form with an extremely long, deeply nested field name is enough to make memory run out at that step on purpose.
CVE-2026-109619: leftovers from one request are used by the next. A PHP worker handles many requests in a row. Some worker-wide records point at memory owned by a single request. If a fatal error interrupts cleanup, those records survive and the next request reads memory that has already been freed. Two paths are confirmed: session upload progress (on by default, and active even if the site never uses sessions), and the fatal-error backtraces added in PHP 8.5.
What they share: both happen before the site's own code runs. Login pages, password protection and security plugins cannot stop them, because they never get a turn.
Why LocalPapa is not affected
Saying "we're not affected" is easy, so here is what can be checked (tested on 1 November 2026):
- There is not a single PHP file in the source. The project is HTML, JavaScript and Markdown, plus Python and Node scripts that generate pages on our machine. The count of
.php files is zero.
- The site is static files on Cloudflare Pages. When you open a tool, you receive a pre-built HTML file; no code runs on a server for you. Requests for
https://localpapa.com/index.php and /wp-login.php return 404 (not found). Posting a form with PHP2Shell-style nested field names to the home page returns 405 (method not allowed). There is no PHP to parse that form.
- The only server-side code is two small JavaScript functions on Cloudflare Workers: one is the feedback form on the home page, which only accepts JSON and requires a Cloudflare Turnstile check first; the other makes the internal
/docs/ path always return 404. Neither is PHP or goes through PHP.
This is not luck. LocalPapa's founding rule is that your files and data stay on your device: image compression, PDF processing, Bazi charts all run in your browser. The server has nothing to do, so there is no server program — and code that does not exist cannot have vulnerabilities.
But "not affected this time" is not "no risk". Our risks sit elsewhere, and we have to watch them just the same:
- Accounts: if the GitHub (source) or Cloudflare (deployment) account were taken over, an attacker could replace the site outright.
- Third-party scripts: Google Analytics, AdSense and a few CDN libraries are other people's code running in your browser.
- Local build tools: Python and Node packages are part of the supply chain.
PHP2Shell has nothing to do with us. The next one might.
Which software is at risk
PHP's own wording: every PHP installation that serves web requests is in scope — Apache mod_php (highest risk), PHP-FPM, php-cgi, LiteSpeed or FrankenPHP. Every release before 8.5.12, 8.4.27, 8.3.36 and 8.2.35 counts as affected, including the long-unsupported PHP 5.
The table below summarises common software. It reflects 28–30 October 2026; vendor status changes daily, so always check the vendor's own advisory.
| Category |
Examples |
Status and what to watch |
| Websites and CMSs | WordPress, Drupal, Joomla, Nextcloud, HumHub, your own PHP site | The flaw is in PHP, so updating WordPress itself does nothing — the server's PHP has to be updated |
| Shared hosting and panels | cPanel, Plesk, DirectAdmin, CyberPanel, CloudLinux | Mostly patched; cPanel and Plesk even shipped fixes for the unsupported PHP 7.4–8.1 |
| Cloud hosting | AWS Elastic Beanstalk, Azure App Service, Heroku, WordPress.com, Kinsta, WP Engine | Platforms mostly fixed; containers you build yourself (e.g. Cloud Run) are yours to rebuild |
| Home / office NAS | QNAP, Synology, TerraMaster, Unraid | QNAP's OS is fixed but some apps (Note Station 3, QuMagie…) are still affected; Synology's end-of-life PHP 7.3 package is affected; TerraMaster TOS 6 with the web server feature must move to TOS 7 |
| Firewall and network admin pages | Palo Alto PAN-OS, Juniper J-Web, Check Point, Cisco Expressway, pfSense, OPNsense | PAN-OS confirmed exploited in the wild; admin interfaces should never be open to the internet |
| Phone systems | FreePBX, PBXact, VitalPBX | FreePBX 17 is fixed; VitalPBX 4.0 still ships an unpatched PHP 8.1 |
| Development setups | XAMPP, WampServer, Laragon, MAMP, Laravel Herd, Docker official PHP images | All have patched builds; with Docker you must pull the new image and rebuild — old containers do not fix themselves |
The Dutch National Cyber Security Centre (NCSC-NL) keeps a tracker on GitHub. On 30 October it listed 929 products: 217 confirmed vulnerable, 165 fixed, 345 still under investigation, 201 not affected. More are "under investigation" than "fixed" — many devices are still waiting for a patch.
By contrast, purely static sites (GitHub Pages, the static part of Cloudflare Pages, Netlify and the like) do not run PHP and are out of scope.
What you should do
If you just browse the web: visiting someone else's site does not infect your computer; the risk is to that site's server and whatever data of yours it holds. What you can do:
- Check your NAS, router and firewall for firmware or app updates.
- Do not expose their admin pages to the internet. Use a VPN for remote management.
If you run WordPress or use shared hosting:
- WordPress shows the PHP version under Tools → Site Health → Info → Server.
- Ask your host directly whether the 21 October PHP security release has been applied. The version number can mislead: vendors like CloudLinux backport the fix, so a patched server may still report an old-looking version.
If you manage your own server or VPS:
- Install the patched PHP packages from your distribution (Ubuntu, Debian, RHEL and others have shipped them), then restart every PHP worker (PHP-FPM, Apache). Updating files without restarting leaves the old code running.
- PHP 8.1 and older no longer get fixes upstream; upgrade or use an LTS vendor. PHP 8.2 itself reaches end of life on 31 December 2026.
- If you cannot update yet, PHP lists settings that reduce exposure but do not replace the update: disable upload progress with
session.upload_progress.enabled=0; on PHP 8.5 also set fatal_error_backtraces=0; limit post_max_size. Put them in php.ini or the FPM config and restart — ini_set() and .user.ini do not work for this.
- WAFs such as Cloudflare's have added blocking rules (even on Cloudflare's free plan), but that is an extra layer, not a fix: an attacker who knows your server's real address can go around the WAF.
- To check for compromise, review logs back to 17 October: several
Allowed memory size ... exhausted errors at Unknown on line 0 (failure before any script ran), Apache segfault entries, and web server processes spawning a shell.
The other one: CVE-2026-115560
On 23 October PHP announced CVE-2026-115560. It also involves upload progress, but the conditions are much narrower: the site stores sessions in the php_binary or php_serialize format, switches to the php format at runtime with ini_set(), and leaves upload progress enabled. The 21 October release does not fix it; PHP will address it in the next regular release. Until then the advice is again session.upload_progress.enabled=0 — if you already turned it off for PHP2Shell, leave it off. As of 26 October no exploitation had been reported.
Finally
This episode confirmed something for us: the safest code is the code you never needed to write.
LocalPapa is not affected because of a design choice, not a fast patch: keeping data on your device means the server never has to handle your things. If you build websites too, it is worth asking: does this feature really need a server? Everything that can be finished in the browser is one less thing to patch.
References