What happened with PHP?
On October 21, 2026, the PHP project released the fix for two serious flaws, CVE-2026-109618 and CVE-2026-109619, which the project itself rates at 9.2 out of 10 for severity. The patch came out that same day, in versions 8.5.12, 8.4.27, 8.3.36 and 8.2.35. And it's being talked about so much because PHP is behind about seven in ten websites whose server language is known, 69.3% according to W3Techs.
What is PHP and why does it matter?
PHP is a language that a huge number of websites run on behind the scenes: online shops, blogs, websites of small businesses and large companies. You don't see it when you visit them.
Think of it as the plumbing in a building. The website is the building, and its owner is the one who has to check the pipes and replace the faulty part. You, when you visit that website, are the one turning on the tap: you can't fix the plumbing, and it isn't your job to.
That's why this flaw is a matter for whoever owns the website, not for whoever visits it. Even though PHP is in the news a lot these days, neither your computer nor your phone has anything to update because of this particular flaw. What is worth knowing is what you might notice as a visitor and what to do if it happens, which is what comes next.
Should I stop visiting websites?
No. You can keep browsing as usual. The risk lies with the websites that don't install the patch: on those, an outsider could end up taking control, and that can be noticeable from the visitor's side.
How would you notice? A website that suddenly behaves oddly, shows you a strange warning or sends you to another page, or a download you didn't ask for. None of this is new or unique to this flaw, and it's avoided with the same precautions as any other day. Don't install anything you didn't ask for yourself. Be wary of warnings that rush you, like those saying your device has a problem and you must update something right now. And keep your browser up to date. If a website you know behaves strangely, close it and come back later.
What about my data on the websites I use?
It depends on each website, and it's each website that has to tell you if something has gone wrong. As of today, there is no public information confirming that any website has been broken into through this flaw.
If you notice a website you use is under maintenance these days, the most likely reason is that it's being updated. In the Netherlands, several public websites, including the MijnOverheid government services portal, the DigiD login system and the Parliament's website, were taken offline on October 21 as a precaution, according to NOS, not because anyone had broken in.
If a website where you have an account warns you about a security problem, follow its instructions and, if it asks you to change your password, do so by going to its official page yourself, not through a link you receive by email.
What if I have a website, even a small one?
Then yes, you do need to check, but you don't need to know anything about PHP: your hosting company is the one that updates it, and all you have to do is ask. In our guide PHP vulnerability 2026: how to tell if it affects your website and what to ask your hosting provider we show you where to find the version and give you a ready-to-copy email for your hosting provider. And if you'd rather start with the quick option, the free Wakaris analysis tells you whether your website declares an outdated PHP version, explained in plain language.
Have a website? Analyze it for free. We explain it clearly.
Frequently asked questions
Was it caused by artificial intelligence?
No. The flaws were in PHP's code, and artificial intelligence tools were used in the security reviews that helped find them; the PHP project received the reports in August. The attempts to exploit them come from third parties, after information leaked before the patch was published.
Is it fixed?
The fix has been available since October 21, 2026, in PHP versions 8.5.12, 8.4.27, 8.3.36 and 8.2.35. But it doesn't install itself: each website has to be updated, usually with help from its hosting company, and that can take days or weeks.
How long will it last?
It will most likely be talked about for weeks or months, because many websites are slow to update. To give you an idea, in December 2025 cdmon estimated that between 50% and 60% of Spanish websites would be left unprotected from January 2026 for running PHP versions without support.
Sources cited
- php.netPHP News Archive 2026, php.net: notice of October 21, 2026, severity and fixed versions.
- thephp.foundationToday's PHP security release, The PHP Foundation: how the flaws were found, the August reports and the leak before the patch.
- w3techs.comUsage statistics of PHP, W3Techs: PHP usage.
- nos.nlNOS: precautionary shutdowns in the Netherlands.
- ultimahora.esÚltima Hora: cdmon's estimate of Spanish websites running PHP without support.
Authors of this report
Updated: October 22, 2026.


