PPPHP
Security

A critical PHP flaw landed. Here is where you actually stand.

Two unauthenticated remote-code-execution flaws, both scored 9.2, in the language a very large part of the web runs on. The useful question is not “is PHP safe?” — it is “which PHP am I running, and how fast can I change that?”

PPPHP Team8 min read—reads

In late October 2026 the PHP project shipped an emergency-grade security release. Two separate flaws in the engine itself — CVE-2026-109618 and CVE-2026-109619, nicknamed PHP2Shell — are each rated CVSS 9.2 and can end in unauthenticated remote code execution: an attacker running their own code on your server without logging in to anything.

If you write PHP, host PHP, or have a WordPress, Laravel or custom PHP application sitting on a server somewhere, this one matters. The good news is that the fix exists, it is free, and checking whether you need it takes about two minutes. Here is the plain-English version.

Key takeaways

  • Affected: PHP 8.5.11 and earlier on the 8.5 branch, with matching fixes on 8.4, 8.3 and 8.2. If you are on an older, unsupported branch you are not “unaffected” — you are simply not getting fixes at all.
  • Fixed in PHP 8.5.12, released 21 October 2026. Updating is the only complete fix; there is no configuration setting that closes these two.
  • Nothing is left outstanding. Re-checked on 27 October 2026: PHP 8.5.12 is still the newest release on every supported branch, and no published PHP vulnerability affects it.
  • PPServer 0.7.0 — the free local PHP stack — ships the patched PHP 8.5.12 and a current Caddy. The fix went out within days of the disclosure.
  • A local development stack is lower risk than a public server, but it is not zero risk. The PHP on your laptop is the PHP your code runs on all day.

What actually happened

Most PHP security news is about applications — a vulnerable plugin, an unescaped query, a file-upload form that accepts too much. This is different and rarer: the bugs are in the PHP engine itself, below anything you wrote.

CVE-2026-109618Memory corruption while the engine handles running out of memory. The cleanup path itself can be pushed into an unsafe state.
CVE-2026-109619Global state left behind by one request and reused by the next — so what one visitor does can change what the next visitor gets.
Both: CVSS 9.2“Critical”, as scored by PHP under CVSS 4.0 (NVD’s own CVSS 3.1 analysis puts them at 9.8 and 8.1). No login required, and the end state is code execution on the server.
Nothing else outstandingPHP published exactly these two advisories for the release. Checked again on 27 October 2026: no PHP vulnerability is open against 8.5.12.

Because the flaws are in the interpreter rather than in a library you chose, no framework protects you from them and no amount of careful application code is a substitute for the patch. A site built with Laravel, Symfony, WordPress, or hand-written PHP is in exactly the same position: it depends entirely on which PHP binary is serving the request.

Two minutes: are you affected?

The only thing that matters is the version number your server runs. Not the one you installed last year, not the one your laptop has, and not the one your hosting plan advertises on a pricing page.

  1. Check from the command line. On the server, run php -v. The first line gives the version. Note that command-line PHP and web PHP can be different builds on the same machine.
  2. Check what the web actually serves. Create a file containing <?php echo PHP_VERSION;, open it in a browser, then delete it. This is the number that counts. (Never leave a phpinfo() page reachable — it is a map of your server for anyone who finds it.)
  3. Compare. On the 8.5 branch you want 8.5.12 or newer. On 8.4, 8.3 and 8.2 there are equivalent patch releases from the same day. Anything older than your branch’s patched release is exposed.
  4. Update, then verify again. On shared hosting this is usually a PHP-version selector in the control panel. On a VPS it is your package manager. On a local stack it should be a new download, not an afternoon.
A correction to an earlier version of this article

This post first listed a third flaw, “CVE-2026-115560”, as disclosed alongside the other two and still unpatched, and recommended a php.ini mitigation for it. That CVE does not exist. MITRE returns CVE_RECORD_DNE for it, NVD has no such record, and PHP published exactly two advisories for this release. We have removed the claim and the setting. Our apologies — on a security page in particular, a number that cannot be looked up is worse than no number at all.

If you develop on PPServer, this is already done

PPServer is our free, portable PHP development stack — PHP, MariaDB, Caddy, phpMyAdmin and a SQLite studio in a single folder, for Windows, macOS and Linux, with no installer and no administrator password. Version 0.7.0 is the current release; the security fix went out within days of the disclosure.

The PPServer control panel. The right-hand column lists the exact versions it is running: PHP 8.5.12, MariaDB 11.8.9, Caddy 2.11.7, phpMyAdmin 5.2.3 and SQLite 3.54.0.
You should never have to guess which versions you are running. The control panel prints every one of them, next to the settings that would otherwise live in a php.ini you had to find first.
PHP 8.5.12The patched build, carrying the fix for both critical flaws.
Nothing left outstandingRe-checked against MITRE and NVD on 27 October 2026: no published PHP vulnerability affects 8.5.12 on any supported branch.
Caddy 2.11.7The bundled web server moved up a full release line too, picking up fixes in FastCGI path handling and request matching.
Current everything elseMariaDB 11.8 LTS, phpMyAdmin 5.2.3, and a refreshed certificate-authority bundle so outbound HTTPS from your own code is verified.

Upgrading is unzipping the new folder beside the old one, then using the Backup tab to carry your databases and sites across in one verified file. The restore takes a safety copy before it replaces anything, and the old folder stays untouched until you are satisfied.

Patched quickly is good. Built to stay closed is better.

Shipping a patch fast is a response. The more useful question for anything you install is what it does on an ordinary day. A development stack is a privileged thing to run on your machine, and most of them are far more open than they need to be.

It only answers to youEvery service binds to 127.0.0.1, and the web server replies only to localhost names — so a web page that points itself at your machine gets a refusal, not your control panel.
Your secrets stay unservedDot-files are blocked outright, so a .env or a .git folder in a real project cannot be fetched, including through encoded or mixed-case paths.
No remote control surfaceThe web server’s administration API is switched off entirely, and phpMyAdmin ships with its installer removed — nothing listening can reconfigure the stack.
Nothing arrives uncheckedEvery component is downloaded over HTTPS and matched against a recorded checksum when the release is built. A digest that does not match stops the build.

And every archive is unpacked and actually run before it is published — the stack is started, the panel and database tools are opened, a database is created and dropped, a PHP worker is killed to confirm it is replaced while requests keep succeeding, and the cryptography is exercised end to end. You can read the full component list and what each version fixes before you download anything.

The other half: applications that are secure by construction

Patching the engine protects the floor your application stands on. It does nothing about the application. The most common breaches are still the ordinary ones — a form that trusts its input, a page that forgets to check who is asking, an export that quietly includes rows the user should never see.

PPPHP RAD Studio takes the position that those protections should not be something you remember to add. You point it at a SQL database — MySQL, MariaDB, PostgreSQL, SQL Server or SQLite — and it generates a complete, working application in plain PHP that you own, with the security already wired in.

Injection and XSS, handledGenerated queries use prepared statements with bound values, output is escaped, and forms carry CSRF tokens.
Row-Level SecurityA rule like tenant_id = :user.tenant_id follows the user through lists, detail pages, exports, dashboards, charts and the REST API — not just the page you remembered.
Field encryptionSensitive columns are encrypted at rest with AES-256-GCM, decrypted only for users entitled to see them.
Real sign-inRoles and groups, per-table permissions, lockout and password policy, two-factor authentication by app or e-mail, and passkeys.
Audit trail and record locksWho changed what, when, and from where — plus locks so two people cannot silently overwrite each other.
A REST API with a door on itBearer tokens or HMAC signatures, scopes, rate limits and CORS, so “we opened an API” does not mean “we opened the database”.

Rapid, in the sense that actually matters

Speed is a security feature. The reason stacks go unpatched and applications grow holes is almost never that nobody cared — it is that the work was expensive, so it waited. The less code you hand-write, the less there is to get wrong, and the faster you can respond when something like this week happens.

The PPPHP RAD Studio visual designer: a drag-and-drop canvas with ready-made components, a properties panel, and a live phone preview of the page being built.
Drag, drop, set properties. Lists, forms, dashboards, KPI tiles and charts are components you place — and what comes out of the build is ordinary PHP, HTML, CSS and JavaScript you can read.
Ready-to-use componentsData tables with filters and inline editing, master–detail grids, lookups, calendars, Kanban boards, file and image uploads, rich-text fields, signature pads and date pickers.
Charts and dashboardsKPI tiles, bar, line, doughnut and gauge charts, funnels, heatmaps and ranked lists — bound to your data, not to a screenshot.
Responsive and Bootstrap-friendlyMobile-first layouts with a themeable design-token system, so the same pages work on a desktop, a tablet and a phone without a second codebase.
Your own code where you want itServer-side PHP event hooks and client-side JavaScript APIs, with editor assistance and a grammar check before you build.
The same generated application running as an installable app on an iPhone and an Android phone, with a native-style bottom tab bar.
One project, one build. The same application installs on a phone as a progressive web app — offline-capable, with push notifications and a home-screen icon — with no second codebase to keep patched.

A short checklist you can act on today

  1. Find out which PHP your live site runs. Not the one you think it runs.
  2. Update to the patched release for your branch — 8.5.12 on 8.5, or the equivalent on 8.4, 8.3 and 8.2.
  3. Update your development machine too. It runs other people’s code all day; a current local stack takes minutes.
  4. Then look at the application layer — who can see which rows, what is encrypted, whether there is an audit trail, and whether anyone would notice a breach.

Get a patched stack, and an app worth putting on it

PPServer is free and unpacks in under a minute. PPPHP RAD Studio turns a database into a secure web and mobile application — and gives you plain PHP you own.

Frequently asked questions

Which PHP versions are affected by CVE-2026-109618 and CVE-2026-109619?

PHP 8.5.11 and earlier on the 8.5 branch, with equivalent patch releases issued the same day for 8.4, 8.3 and 8.2. Branches that have reached end of life receive no fix at all, so running one is the higher risk, not the safer option.

What is PHP2Shell?

It is the nickname given to the two critical flaws disclosed together in October 2026. One is memory corruption during out-of-memory handling; the other is global state left behind by one request and reused by the next. Both are rated CVSS 9.2 and can lead to unauthenticated remote code execution.

How do I check which PHP version my website is running?

Run php -v on the server for the command-line build, and separately print PHP_VERSION from a one-line PHP file opened in a browser for the version the web server actually uses — the two can differ. Delete that file afterwards, and never leave a phpinfo() page reachable.

Is there a workaround if I cannot update PHP right now?

No — updating is the only complete fix. There is no configuration setting that closes these two.

Was PPServer affected, and is it fixed?

PPServer 0.5.0 shipped PHP 8.5.11, so it carried the flaws. The current release, PPServer 0.7.0, ships the patched PHP 8.5.12 and a current Caddy 2.11.7; re-checked on 30 October 2026, no published PHP vulnerability affects 8.5.12. Because PPServer binds only to your own machine and refuses requests arriving under any other hostname, the practical exposure was lower than a public web server — but the bundled PHP is the PHP your projects run on, so updating is worth doing.

Do applications generated by PPPHP RAD Studio need patching?

A generated application is plain PHP, so its security depends on the PHP version of whatever server hosts it — update that server as you would any other. The application code itself is unaffected by these engine-level flaws.

Does PPPHP RAD Studio handle application security as well?

Yes. Generated apps use prepared statements and escaped output, CSRF-protected forms, role and group permissions, row-level security that follows through exports and APIs, AES-256-GCM field encryption, two-factor authentication and passkeys, an audit trail and record locking.

Is PPServer free, and does it work on Windows, macOS and Linux?

Yes to both. It is free, and there is a build for Windows, macOS and Linux. It unpacks into one folder, needs no installer and no administrator password, and deleting the folder removes it completely.

Can I build a mobile app and a web app from the same project?

Yes. The same project builds a responsive web application and an installable progressive web app with offline support, push notifications and a home-screen icon, so there is no second codebase to keep patched.

Build your first app today

Point PPPHP RAD Studio at a database — or start on the built-in one — and have a secure, responsive web app running before lunch.

Keep reading

Complete guide

PPPHP RAD Studio, 0 to 100: the complete guide to building database web apps

Step-by-step guide to PPPHP RAD Studio: connect any SQL database, generate CRUD pages and dashboards, then secure, build and deploy a PHP web app you own.

7 October 2026 · 7 min read—Read
Mobile & responsive

Responsive, mobile-first web apps — without writing front-end code

Build responsive, mobile-first web apps with PPPHP: a native-style phone UI, installable PWA, offline sync, web push, dark mode and multilingual apps.

7 October 2026 · 6 min read—Read
For developers

The modern web stack in one studio: APIs, real-time, security and deployment

What ships in every PPPHP app: REST API, OAuth2, GraphQL, webhooks, real-time SSE, passkeys, row-level security, payments, cloud storage and AI.

7 October 2026 · 5 min read—Read
Mobile & responsive

Design the mobile app — don’t build a second one

Give a database app a real phone experience without a second codebase: a bottom tab bar you drag into shape, an arrangeable app bar, tap effects, per-page rules, installable PWA, offline writes and web push — from one build that still serves desktop.

15 October 2026 · 7 min read—Read
Getting started

From nothing installed to a live app on a phone

A free, portable PHP 8.5 + MariaDB + Caddy stack that runs from one folder on Windows, macOS and Linux — no installer, no admin password, no port 80 fight — and a visual studio that turns that database into a web app, a REST API and an installable mobile app from a single build.

17 October 2026 · 8 min read—Read
Product

Build forms that react to what people type. No JavaScript required.

Conditional field visibility, star &amp; pill filters, one-click date presets, and type-ahead suggestions from your own data — the field-control upgrades in PPPHP RAD Studio that make a generated app feel hand-built, configured once and compiled into clean PHP you own.

12 November 2026 · 5 min read—Read