PHP vulnerability currently being exploited!

I’m subscribed to the Security Now video podcast, and while going over unread email messages, I noticed a Security Alert that Steve Gibson of grc.com considered so urgent that he published this alert in an email message he distributed to his mailing list:

Security Now! FLASH Alert
October 21st, 2026

A Very CRITICAL Flaw Revealed in PHP

PHP versions from v5.4 to Current are
vulnerable to Remote Code Execution!

A critical vulnerability affecting all PHP versions back to 5.4 allows attackers to execute arbitrary commands on the server without authentication. If you are responsible for any public-facing PHP-based system (Wordpress, forums, etc.) you’ll want to take immediate action.

Reports call this one of the most serious security issues PHP has ever faced. Working exploits are publicly available and attacks are underway. Reuters reports that government websites across Europe and elsewhere have been taken offline to prevent their attack. (See the Reuters Story for more.)

Mitigations can be applied to the PHP.INI configuration file for immediate protection, but the PHP binaries should be updated. Patched releases are 8.2.35, 8.3.36, 8.4.27 and 8.5.12.

The PHP project’s home page has all the details and mitigations: https://www.php.net/

I’m SURE that next Tuesday’s podcast will have the whole story once this has all unfolded.

I agree that this issue is serious enough that it warrants the broadest possible distribution, so if you’re a member of any other forums, please post this there for me!

3 Likes

We’ve been scrambling since last week at work. We have almost no PHP, but some third party software we use does. There is also a Node.js vulnerability involving a brotli decompression package too.

4 Likes

I’m glad you already knew about this! Since I just found the Alert from GRC today, I wanted to make sure the word has been spread as far and wide as possible! I’ve also posted it on the Garuda Forum too.

4 Likes

Could these arbitrary commands then become a threat to computers using the server? If yes, then the only safe action is for everyone fo stop browsing.

1 Like

I had to fix it on one server last week… Amazed there was only one…

The confusing thing - was the PHP in the default RHEL repo was the exact same version as the one installed : 8.0.30 (with a build date from 2023).

I installed it anyway - reports the exact same version number - but a build date of 20/10/2026.

Note also - some “developers” will package their application with PHP outside of the operating system packaging system… that’s a hideous thing to do - but I’ve seen similar happen before…

Also note : not just Linux / UNIX - I believe Windows systems running PHP are also vulnerable… I don’t have it installed on MacOS or any of my Linux systems…

Here’s what ANNOYS ME about when so called “security experts” flag these things - 99.999 % of the time - systems are >NOT< vulnerable because THEY’RE NOT INTERNET FACING!

5 Likes

I have no idea, because I haven’t dug into this vulnerability beyond relaying GRCs Security Alert so anyone who uses PHP knows to update ASAP., but if a bad actor gains control over a system, thew belongs to them.y can do anything - essentially, your machine now belongs to them … a great reason for regular backups, right?"

1 Like

But once a vulnerability has been discovered, particularly in something as ubiquitous as PHP, shouldn’t it be widely publicized as possible? And wouldn’t it be true that unless a machine that runs PHP is completely air-gaped, wouldn’t it remain vulnerable?

1 Like

My association website is on a ovh server and uses wordpress 7.1.3
I checked the security logs and we are on the very latest version plus all my extensions are up to date. Yes its using php for the calendrier system and membership details entry.
But I cannot find a mention of the PHP version, the reports I run just say secure and latest versions.
Do I need to be concerned ?

1 Like

Yes. Until you find the version details you just dont know.
Also if your website links to other websites, you could import their issues.

1 Like

Not sure how as all our links are out going with no return path.
So you register membership then go out to pay, or you click a link to go to our national association.
No idea if any other sites link in to us except search engines

1 Like

If you read the alert, Wordpress was mentioned, so I recommend you contact Wordpress to ensure you have the patched release of PHP, and for authotative information Steve provided a couple of links in the alert that you can check out

1 Like

The common practice is called responsible disclosure (or coordinated vulnerability disclosure):

•A researcher privately reports the flaw.

•The vendor develops and releases a fix.

•Security advisories are published.

•Detailed exploit information may be released later, after users have had time to patch.

The idea is to not help the bad guys with too many details too soon. People need time to develop the patch and then get it applied.

4 Likes

And all that happened before Steve Gibson sent out his alert.

4 Likes

I don’t think Steve Gibson did anything wrong. I was just saying there is an accepted method of handling these things. In this case, that was not followed. AI summary below.

Q: Was the PHP vulnerability information released too soon?

A: Yes, that’s essentially true, though the story is a little more nuanced than “the vulnerability was irresponsibly dumped.”

For the recent PHP2Shell vulnerabilities (CVE-2026-109618 and CVE-2026-109619), the PHP Foundation had been coordinating a traditional responsible disclosure process with vendors and distributors under an embargo. The plan was for patches and public details to be released in a coordinated way so defenders could prepare. [infoworld.com], [huntress.com]

What happened is that details began leaking before the planned disclosure date:

  • Information about the vulnerabilities leaked online before the embargo expired. [huntress.com], [abgeo.dev]

  • The PHP Foundation says at least one participant in the coordinated process broke the embargo, and it was forced to release patches and advisories earlier than planned. [infoworld.com]

  • Some reports specifically mention security companies publishing or exposing information ahead of schedule, leading to criticism that the coordinated disclosure process had failed. [infoworld.com], [theverge.com]

However, there is an important twist:

  • Evidence later suggested that attackers may have known about or been probing the vulnerabilities before the public leak occurred. Amazon Threat Intelligence reported exploitation attempts dating back to October 17, several days before public disclosure and before the embargoed release was supposed to happen. [shattered.io], [tenable.com], [theverge.com]

So if you read that the incident was controversial because information became public before proper responsible disclosure, that is accurate. The controversy centered on an embargo leak and whether participants honored the coordinated disclosure process. [infoworld.com], [huntress.com]

But it’s also true that the situation may not have been as simple as “everything was secure until the leak.” There are credible reports that threat actors were already aware of the bugs or had independently discovered them before the embargo was broken. [shattered.io], [theverge.com], [cpomagazine.com]

In other words: yes, there was a premature disclosure/leak that many people criticized as a breakdown of responsible disclosure, but evidence suggests attackers may already have been exploiting or researching the vulnerabilities before that leak occurred. [infoworld.com], [cpomagazine.com], [theverge.com]

4 Likes

Having PHP 8.2.35, 8.3.36, 8.4.27, 8.5.12, or higher fixes the problem. According to the web.

2 Likes

So they have 3 major versions , 8.2, 8.3, 8.5 going at once, and subversions within each of those.
That is getting to be like kernels… and all major versions have the bug.
Looks like they are going to patch every version separately.?

2 Likes

From the AI you included, this instance may have been the proverbial exception to the rule. I’d love to hear from the original leaker regarding motives.

3 Likes

It may have been about enhancing the profile of his security business.?

1 Like

Yes!

I wasn’t arguing against that - I’m talking about people in companies having someone with the big “Security Expert” badge on - all they do is run some scanning software like Qualys daily or periodically - then log a ticket that their scan found something… Some of these “experts” wouldn’t have a clue!

I once had an argument with one of these “experts” about using the telnet client - they just blindly assumed “telnetd” issues (plain text password challenge / response) also meant doing stuff like “telnet localhost 80” to check if there was a HTTPD listener runing was a major security risk… Probably got their “expert” badge out of a cereal box…

4 Likes

Perhaps, but since this person leaked this information early, (s)he should explain his/her self, due to all the potential damage to all the unwitting victims he may have exposed.

1 Like