In one line: on 21 October 2026 the PHP project announced two critical vulnerabilities in PHP — the language most of the web runs on. Both are rated 9.2 out of 10. The fix ships today at 14:00 UTC (17:00 Moscow time). Until it ships and until your server is updated, an outsider can, in principle, run their own commands on your machine — no login, no password.
What happened
On Monday evening the PHP security team did something unusual: it published an advance notice. "Prepare now — on Wednesday we ship an emergency release fixing two critical vulnerabilities, both 9.2 out of 10." Security releases normally appear without warning.
Within hours the details that were supposed to stay under embargo leaked. CVE numbers surfaced (CVE-2026-109618 and CVE-2026-109619), along with screenshots of an exploit tool called PHP2Shell and write-ups from several security firms. watchTowr confirmed the bugs are real and reproduced one of them. Huntress noted it had not yet seen exploitation in the wild.
So this is not a "we'll read about it tomorrow" situation. It is a "the fix lands in a few hours, be ready" situation.
What is actually broken, in plain terms
Every program keeps its working data in memory. When data is no longer needed, the memory is released — like an apartment whose tenants have moved out. A use-after-free bug is when the program still holds the old key to that apartment and keeps walking in, even though it is supposed to be empty.
If an attacker manages to move into that freed space first — placing their own data there — the program walks in with the old key and starts executing whatever they left behind. In PHP's case that ends with the web server running arbitrary code on command from outside.
According to the leaked material, at least one of the two bugs lives in the mechanism that tracks file upload progress (session.upload_progress in PHP). That code path is entered whenever someone posts a form containing a file — and it is entered regardless of whether the site has any progress bar. Some researchers place the second bug in the multipart form parser, independent of that setting.
The important part: this is a bug in PHP itself, not in WordPress, not in a plugin, not in your site's code. Updating plugins or patching application code will not help. The fix is a new PHP build on the server.
Who is exposed
In principle, any PHP site: shops, forums, WordPress blogs, CRMs, admin panels, forgotten internal tools. The official list of affected versions will be published together with the release.
The leaked claim is everything from PHP 5.4 onwards — effectively all PHP running in production anywhere. That is not yet officially confirmed, but planning for the worst case is the sane move.
There is a second problem: PHP only maintains branches 8.2 and newer. Versions 5.x, 7.x, 8.0 and 8.1 will receive no upstream fix at all. If a site still runs one of those, the choices are a distribution backport, a migration, or taking it off the public internet.
What to do right now
If you own a website but are not technical, there is exactly one question to ask your host or admin: "Which PHP version are we on, and when are you applying the 21 October update?" Nothing else is required from you. Do not change passwords — this is a server-side vulnerability, not a data breach.
If you are responsible for servers, the order matters:
Update as soon as the release lands — 14:00 UTC today. Expected fixed versions are 8.5.12, 8.4.27, 8.3.36 and 8.2.35; the exact numbers come with the announcement. On Linux the fix usually arrives through your distribution's repository, where the version string may not change at all — so check the package changelog, not just the number.
Restart PHP. This is the most common mistake: the patched package sits on disk while the old worker processes keep running in memory. Until PHP-FPM or Apache is restarted, you are still vulnerable.
Until the patch, disable upload progress tracking. Add session.upload_progress.enabled = Off to the PHP configuration and restart PHP. File uploads keep working; only the progress indicator stops. Honest caveat: several researchers say this closes only one of the two bugs, so treat it as a stopgap, not a fix.
Verify it actually applied — through a web-served phpinfo() page (and delete that page immediately afterwards). The command-line php -i output is irrelevant: the web server has its own configuration.
For legacy PHP (8.1 and older) — a distribution backport, a WAF, a VPN, or removal from the public internet. No official patch is coming.
Do not spot-check one machine. Cover the whole estate: a second PHP version on the same host, containers, old VMs, staging boxes. That is where the forgotten vulnerable build always hides.
What to expect next
Once the release is out, the diff between old and new source becomes public — which shows attackers exactly where to aim. Mass scanning and exploitation typically start within hours, occasionally within a day. "We'll patch at the weekend" is not a plan here; the window is measured in hours.
Написать Join — чтобы участвовать в обсуждении.
Good to know, Glad the Torn Market Place doesn't use PHP at all
Ответы · 1
don't assume other vulnerabilities are not existing. rust and cargo also have their loads
Ответы · 1
this is very true and to be taken seriously
security is a constant job
Ответы · 1
Positive sir ! Keep it up !
Ответы · 1
thx!
Показать ответы: 15
a prime example of every system has a flaw. php has existed for " stone ages " and still there's flaws in their systems. Cheers to whoever spent days if not months finding it though!
PHP is an ancient system, why someone should use PHP in 2026???
Показать ответы: 17
probe comment from security test - ignore.
identity probe A
wl probe conclave34rnuanwio3slphw73z6jtfp6ptwn6m6azbi3krpmxs2cpqd.onion https://conclave34rnuanwio3slphw73z6jtfp6ptwn6m6azbi3krpmxs2cpqd.onion/x