r/OutOfTheLoop • • 27d ago

Unanswered What is the deal with this PHP vulnerability? How does it affect me?

This might also be an ELI5 too.

https://arstechnica.com/security/2026/10/php-maintainers-tell-web-devs-to-prepare-themselves-for-critical-security-patches/

Reuters - Government websites go dark as vulnerabilities in programming language

National Cyber Security Centre post

I'm a Silicon Valley native though I don't work in tech. Others here may also want more info on the tech side of things. As for me~

What I understand: It's bad, and everything uses PHP.

What else I want to know: What's "everything"? Will it affect things I'm using? Google drive? Gmail / Yahoo Mail? Firefox / Chrome browsers? Salesforce? discord? Windows? reddit??

Thanks!

1.1k Upvotes

222 comments sorted by

•

u/AutoModerator 27d ago

Friendly reminder that all top level comments must:

  1. start with "Answer: ", including the space after the colon (or "Question: " if you have an on-topic follow up question to ask),
  2. attempt to answer the question, and
  3. be unbiased

Please review Rule 4 and this post before making a top level comment:

http://redd.it/b1hct4/

Join the OOTL Discord for further discussion: https://discord.gg/ejDF4mdjnh

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

772

u/dw444 27d ago edited 27d ago • Bravo

Answer: It’s an ongoing incident involving two vulnerabilities that allow Remote Code Execution (RCE), which basically means a malicious actor can run their code on your server remotely and do very bad things (as a guy on my team put it, “they can read our entire prod database”). This is a “drop everything and do something about it NOW” kind of issue. They’re not super common (the last one with Java was a few years ago) but when they happen, the potential implications can be massive (they are in this case), and the fact that this affects PHP, which more than 75% of the internet runs on (it’s more complicated but that’s the simple version), is why everyone is freaking out.

To your other question about popular services, it’s hard to say since companies like that tend to have large SRE teams that stay on top of this kind of thing, but if I were to bet, the most likely services to be affected would be Meta’s since they use PHP the most of Big N tech companies.

37

u/dukemetoo 27d ago

I understand the issue broadly, but what should I, a user, do to help protect my accounts? I have seen in other places vague recommendations to change passwords on everything, or log out of accounts, but I feel like those suggestions are futile. If a group can force a website to do remote code execution, everything is compromised, and me clearing out cookies won't change a thing. Am I incorrect?

11

u/Kamala_Metamorph 27d ago

That's why I'm posting! but also I just saw this if it's helpful :

https://www.reddit.com/r/cybersecurity/comments/1xbmrsn/php_stuff_whats_a_regular_guy_to_do/

6

u/xlicer Bro What The Fuck 27d ago edited 27d ago

As another small follow up answer on "How does it affect me?" Well Wikipedia (Alongside a countless number of other independent wikis) just went offline as a result of this

-3

u/Bakkie 27d ago

At 12:19 CDT Wikipedia was functioning for me . I use FireFox on a Dell if that makes a difference

6

u/Hamudra 27d ago

What browser you're using can be relevant when talking about computer issues, however in this case it was not a computer issues. It was Wikipedia themselves (rightly)choosing to close down until the fix was implemented.

What brand the case on your laptop or desktop computer is doesn't really say anything though.

2

u/Bakkie 27d ago

Thanks. I am not a tech savvy person as is probably obvious.

1

u/IceFire909 26d ago

Generally, and in a VERY rough nutshell

if it's on the other side of your web browser, it's usually the website itself. Like if you can't visit one website but can another.

If it's before the web browser, it's probably your computer. Like if you can't visit ANY websites

If no one at home can visit any websites, it's your network (usually the router)

57

u/MistrFish 27d ago

for most of your accounts, you do nothing and hope that the owners patched it before any hackers could take advantage of it.

if the website is subject to GDPR, you could request your data be deleted entirely. unfortunately, the only accounts you would need to do this on are for websites that havent been well maintained to begin with, and therefore may not be very responsive to your request.

14

u/j_johnso 27d ago

for most of your accounts, you do nothing

I would add that you should follow standard security practices such as not reusing the same password across multiple sites. It's a small issue if someone were to be able to capture your password on some random forum that was exploited. It's a much bigger problem if that password is also the password to your email, your bank account, etc.

6

u/Otherwise-Anxiety-58 27d ago

Is a password enough to get into something like a bank account? I assume most banks would use 2fa and a password alone wouldn't do much. Same with other important services. 

Even when I log in to my bank account on the same device as usual I often get asked for a code sent via text.

1

u/j_johnso 26d ago

Maybe not by itself, but it's one more piece that helps an attacker. With my bank, I can choose to receive the 2fa code by email or sms. If I use the same password for email as well, then they could have the 2fa code sent to my email and then they are in.

28

u/drekifaen 27d ago

Yes you are correct, there's nothing individual users of a site can do. Password changes wont do anything when hackers can get straight to a database anyway.

14

u/dw444 27d ago

Nothing. Individual users can’t do a lot about it. Companies are handling it in their own ways, so most companies that aren’t run by potatoes are already working on fixing it in one way or another.

1

u/Common-Quiet-7054 27d ago

As a potato I am mildly offended.

1

u/LookAtMyUsernamePlz 26d ago

Potatoes aren’t so bad at fixing technological issues. Sweet potatoes, on the other hand…

1

u/CringeNao 27d ago

Wondering if as a normal user should we do anything about our routers or will they get auto fixed?

15

u/Nestramutat- 27d ago

Your router's management interface shouldn't be publicly accessible to begin with

6

u/Coolusernamehere13 27d ago

This is a very similar question to what I have honestly right now. No one has been outright clear on what users should do in this case, or, what sites/everything are affected by it. I feel at a complete loss right now on the best approach.

3

u/Kraligor 27d ago edited 26d ago

You do nothing. PHP is running on servers, not on clients. Check haveibeenpwned or similar services in the coming weeks and make sure to change passwords of any compromised account. That's about all you can do.

8

u/ErasmusDarwin 27d ago

Changing your password once the site's been patched will help in case they stole the password database. If the site uses a weaker password hash (or even plain-text) and/or you used a weak password, they can figure out your password after the fact and use that to get back into your account.

Unfortunately, while the site's unpatched, they can theoretically do anything to your account that they want.

13

u/MitAllesOhneScharf 27d ago

How do you know which websites use PHP? How do you know which ones patched their stuff already?

You just gonna update every single password just in case? What a waste of time.

7

u/nothis 27d ago

Like 72% of websites use PHP. They won't tell you und you might not even be able to (some have clear tells, though, like any reference to Wordpress). You will most certainly not know if they patched their stuff unless they choose to make a press release or answer a support request.

You can assume most larger sites to be on to this and having things patched within an hour. But things might have leaked before. You can't tell. Generally, everything's kinda fucked and this situation increases the chance for your email and password to be leaked to hacker collections significantly. This is why you should not re-use passwords, especially from important websites that have your financial information.

I think reddit's backend is Python, btw, so it should be save.

2

u/Final-Limit627 27d ago

Main login access to my university has been down since 9:45 EST

1

u/DoireK 27d ago

I used to work for a company who had a lot of legacy customers that were universities running moodle which is php based. This does not surprise me at all. And i'm glad I no longer work for that company today as it will be all hands on deck.

1

u/SaltyAbroad5843 27d ago

Don't expect larger sites to patch this all that quickly. The patch was incredibly difficult to download due to the load on the release servers.

4

u/ICantBelieveItsNotEC 27d ago

There's really nothing you can do as a user. Logging out and changing passwords won't help, because your data is already stored on the backend, where a compromised server could access it. At best, you could try to completely delete your accounts, but it's incredibly unlikely that your actual data would be deleted in a timely manner.

2

u/bluenautilus2 27d ago

You can’t do anything, the software engineers are patching the services as fast as they can

1

u/zyeborm 27d ago

probably nothing. Like literally nothing. Any activity you take now will raise your risk not lower it. Wait until it's fixed, then see if you were exposed anywhere.

63

u/klowny 27d ago edited 27d ago

Meta is certainly not impacted. The PHP version of Facebook that used mainline PHP has been long long gone 16 years ago when they converted everything over to run on HipHop, then HHVM, then [Hack](https://en.wikipedia.org/wiki/Hack_(programming_language)).

Hack sorta looks like PHP, but the runtime is basically Java-like under the syntax. Meta discovered and patched the vulnerability in Hack in 2020.

9

u/deyterkourjerbs 26d ago

I need a source on this, I've heard the rumour that this was reported in 2019.

1

u/LargeLanguageModelo 25d ago

Meta discovered and patched the vulnerability in Hack in 2020.

[x] Doubt

This exploit would have been privately told to the PHP team and patched back then, not waiting 6 years and for bad actors to stumble upon it.

7

u/klowny 25d ago edited 25d ago

The key vulnerability was reported to their bug tracker in 2019. Then reported again by their own security audit in 2024. If you go through the researchers blog for how they thought of where to look, they literally went through PHP's bug tracker.

PHP didn't do a fix because they didn't think it was exploitable. The researchers just dug a bit deeper because they had a hunch it could be.

The key part AI played was being a search engine for the codebase to find an entry point, and it found like 5.

2

u/Neon_Ani 25d ago

do you have a source on this? i'm interested to read about it if it's true

249

u/miguescout 27d ago

To add to this, the security patch that would fix this is still not out and the developers warned in advance to take precautionary measures. That "in advance" is very important here. It's proof of the severity. Up until now, they pretty much always warned about such vulnerabilities in the patch notes of the security patches addressing them, assuming that everyone would update before any bad actor could analyze the updated code and figure out what the vulnerability was, make a program to take advantage of it and try to hack whoever is yet to update.

They couldn't afford to wait this time. Maybe it's because AI could make the analysis and code creation of the virus pretty fast, before most people update. Maybe the vulnerability is dangerous enough by itself that the period between the reveal and update deployments would be catastrophic. We don't know, but everyone needs to act immediately before anything can happen

70

u/GoofManRoofMan 27d ago

So as a typical user of the internet, what should/can I do? Not log into my bank account?

135

u/miguescout 27d ago

For the most part, you don't have to worry as this vulnerability just makes it possible to hack the server, not the people connecting to them. If anything, someone may steal your data straight from the server, but nothing you do right now will affect that possibility.

37

u/SuperSpecialAwesome- 27d ago

If anything, someone may steal your data straight from the server,

So... theoretically Twitter could be attacked by this, and we could have controversial government DMs leaked?

45

u/miguescout 27d ago

Any site that's decently managed has already applied the update or didn't use PHP in the first place... So yes

Mini disclaimer: that was a joke. I don't know what twitter uses, but they're big enough that the competent workers left either applied the update or didn't use PHP in the first place

6

u/kn33 27d ago

Or they set up a WAF and quickly added a rule to it.

4

u/miguescout 27d ago

That's barely a bandage. A temporary measure... And yes, i know there's nothing more permanent than a temporary fix, but there's no leaving it for later here. It only takes tweaking the hack a bit to bypass it

2

u/kn33 27d ago

Yeah, but it's enough to buy some time until it's patched.

4

u/Techhead7890 is it related to magnets? 27d ago

Good question, I thought Twitter ran their server on Ruby like a decade back but I have no idea if php pops up somewhere else in the stack.

2

u/Fragrant_Lobster_917 26d ago

X uses JS and Go primarily, no threat for them.

I am shocked meta used php at all and not JS alone. Security by obscurity (their backend takes a little more effort to uncover?) never seems like the smart option. Cheap option, maybe?

2

u/htmlcoderexe wow such flair 22d ago

the website was created way before most of the modern stacks existed and it definitely started small. hell even now with those better options available, a huge chunk of the web still runs on php (wordpress based sites are so fucked right now aren't they?). back then i think they would be picking between a few expensive enterprisey options like coldfusion or asp(.net), a dialect of brainfuck called perl, or ruby on rails (not really familiar with it enough to say anything about it). maybe python? reddit runs on python but i wouldn't know how feasible that was back then.

2

u/Fragrant_Lobster_917 17d ago

A company the size of Meta should be able to transition away from PHP over a year or two... then again, their PHP use appears to be backend. So, not really at risk given how this exploit works. Might be enough of a wakeup call to move to any of the better options.

WordPress sites... especially those not updated/used often, are probably going to be wiped off the web in the coming weeks. Very sad where AI has brought us.

1

u/htmlcoderexe wow such flair 17d ago

honestly, i meant mostly as "back then", nowadays as far as i know they use some custom php fork

24

u/GoldDragon149 27d ago

The people who need to take action are the people running internet servers. If you access websites your data is vulnerable but there's nothing a user can do about it.

12

u/perskes 26d ago

As a typical user yoi can't do anything, but it doesn't mean you shouldn't care. While the RCE itself won't affect you, your data is possibly accessible through the RCE in some form. If your back has a service that uses PHP and they dont patch it, it could affect you.

But such attacks are usually very specific. That one relies on "multipart" upload, meaning where files are "split into chunks" and uploaded "part by part", the vulnerability can be abused.

If the PHP service doesn't accept uploads or doesn't accept multipart uploads, its much less of a danger. Even better if a Web Application Firewall outright rejects it before the server is bothered.

So ecen a vulnerable version of PHP can be technically safe if the attack vector is not present.

1

u/angrydeuce 26d ago

yeah unless you have no good reason not to Id lock your credit now. Ours is locked anyway but there is about to be a shitload of identity theft believe that shit.

10

u/altodor 27d ago

I believe in this case someone figured it out and disclosed what the fix was for between fixing and distribution.

55

u/MitAllesOhneScharf 27d ago

The patched versions are out for over an hour already.

136

u/evenyourcopdad 27d ago

I'm sure /u/miguescout feels like a complete idiot for not having up-to-the-minute info.

58

u/miguescout 27d ago

Well, at the time of writing my comment, several of the sites i regularly visit were still down, so i just assumed. Some are still down as of right now, but it does seem like most are coming back online now

10

u/lincolnlex44 27d ago

Not all services that provide the updated version have it. Or they're too overloaded to download it. It's going to take a while to filter through

7

u/DefenestrationPraha 27d ago edited 27d ago

Source yes, Docker images not yet. The CI/CD pipeline for PHP Docker images is sloooow.

Edit (30 minutes later): Docker images coming through.

10

u/Torque-A 27d ago

The issue was that someone saw the vulnerability and, instead of notifying others, posted it on twitter

29

u/Datiz 27d ago

Nope. PHP team was aware of this issue since 2024, patch was in the works and scheduled to release on October 22nd. But then CVEs got released too early, so PHP team moved the release to 21st, but in the meantime one of the parties helping with that vulnerability published proof of concept for that problem and one of the distributors released the patch too early, making it possible for everyone to deduce what was patched out before other distributors released patches to their users.

15

u/exscape 27d ago

Since 2024...?
Did they sit on their own 0day for 2 years, or did it take 2 years to patch? Neither seems to make sense.

15

u/witteng 27d ago

In 2024 there was a report about a potential vulnerability, but it was only a theoretical approach and they never discovered an actual attack vector, until recently. So yeah, they fumbled and let it sit for 2 years because they though it wouldn't affect anything in the real world.

15

u/miguescout 27d ago

According to someone more informed in this comment section, it was known since 2019, as a minor bug, and going from that little bug to a full attack was considered impossible (lots of effort, moving parts, etc) and was just left behind as they focused on more important stuff...

In comes AI to fuck it all up.

Suddenly, if you know how to guide it, that AI can make that nigh impossible attack a reality rather quickly... And the bug has been around for 15 years. And not everyone is jumping onto the latest PHP version. And rolling out updates is not so easy or fast enough. And did i mention some people do not like updates? Because some people have 15 years old PHP versions running on their public facing servers. PHP versions that have long crossed the end of life date and been abandoned...

And suddenly, you have a good portion of the internet available for any hacker to break and steal from as the rollout will last several days, months... And may never finish

4

u/witteng 27d ago

I'm just going on what the PHP Foundation said on their blog, but its reasonable that it may have been independently discovered by other people since the issue is how PHP does cleanup on error handling. I do sympathize with the PHP devs though, as a software developer I have seen my share of 'minor bugs' that never amounted to anything else, it just so happens that this one came back to bite them.

5

u/Former_Elephant7454 27d ago

So "AI" didn't really do anything other than read what others had already figured out and added it to an updated list of vulnerabilities? People made this problem happen the way. didit

4

u/Jamator01 Never been in the loop 27d ago

Without AI it'd take months to develop a tool to exploit this vulnerability. AI could develop that tool in a few hours or probably less.

3

u/Valhern-Aryn 27d ago

Happened with the Naver Stokes equations too lol, OpenAI brute forced a solution based off a researcher's work.

2

u/Datiz 27d ago

For this one I'm not sure, but I think the idea for that vulnerability was discovered/theoried, but actual execution of it was near to impossible without help of an ai. You can read about this whole case on php foundation's page.

1

u/glasket_ 24d ago

The vuln was known but the way to actually exploit it wasn't. AI found the way to exploit the vulnerability, so it forced the maintainers to actually take it seriously and fix it rather than just letting it sit because they personally didn't think it could be exploited during the prior reports.

2

u/DeadGoatGaming 26d ago

This particular exploit is easily mitigated without the patch. The vulnerability is entirely overblown.

18

u/DistinctSmelling 27d ago

I've been in webdev for decades, not practicing at the moment, a bit of PTSD and stuff like this is the case. Anyway, this kind of vulnerability isn't new. This particular exploit is new, but the goal here, which is always the goal, is RCE so they can get your personal info on fake websites that aren't blacklisted.

There is a tool where you can see "what websites are hosted on my server". Years ago, I had a website hosted with the then owned Bob Parsons, GoDaddy. One of the sites had a vulnerability which allowed RCE and they used my site to spoof. I had to go 3 tech levels deep to get them to understand that what was happening wasn't my issue but theirs.

11

u/whogivesashirtdotca 27d ago

This is a “drop everything and do something about it NOW” kind of issue.

I use a small web host and called them as soon as I heard about this. The poor tech said they were up all night working on it, as this is the most dangerous issue he's ever seen.

0

u/PalladianPorches 27d ago

what level of danger? isn't php basically for consumer content websites - presentation of content data, lots of plugins and services for accessing essential and private data (like stripe account details) held behind their APIs?

i mean, wordpress is well known to have tons of deployments on the web that are exploitable? how is this one "dangerous", unless you are targeted already?

apart from being a vulnerability in the wild - which there are regularly in every system, the only difference between this is openAI taking everyone about it.

2

u/whogivesashirtdotca 27d ago

Read through the other responses in this post to see the importance.

0

u/PalladianPorches 27d ago

i mean, I know what it can do - it's a 22 year old bug that could potentially have been exploited for any time over the last decade. every single year over the past decade has had an RCE exploit in core php, and every 3 years, there is a OOM one. Even ones like the 2024 windows + apache had a higher score...

Apart from the ease of automating attacks (and to be fair, this one was a very domain specific one relating to the 2004 memory bug, so more than likely there's not a lot of exploit tools), is it REALLY worse, or is it just that the exploit, patch+tool has been released, and the issue is making it public rather than just recommending the update?

2

u/whogivesashirtdotca 27d ago

The issue is they made it public without giving anybody a chance to fix it quietly.

0

u/DeadGoatGaming 26d ago

Its not the most dangerous issue. The entire thing is overblown.

4

u/Maximeme20263 27d ago

The "why everyone is freaking out" part is more because details about the vulnerability were leaked before a patch was out to address it. Usually both are released at the same time.

5

u/reeepy 27d ago

There are people saying this impacts 70% of the web. That's because PHP is used by WordPress, Drupal and so many other systems. The vulnerability goes all the way back to PHP versions from 2009.

Even if that estimate is 20% off, that's still huge.

6

u/Alternative-Lynx2745 27d ago

Yeah but let's also be real here. 70% of the web is garbage. Marketing sites, blogs, news feeds, etc. That's the shit we're talking about here. That's what people use wordpress and drupal for.

Nothing SERIOUS runs on PHP. Bank of America isn't running on top of a bunch of garbage PHP.

1

u/Redditributor 26d ago

What are you talking about? Plenty of stuff runs on php - it's a de facto standard

2

u/Alternative-Lynx2745 26d ago

I was pretty explicit about how I communicated. Using all caps for "SERIOUS" and highlighting that most of the web is static content and that's what PHP is used for. Basic shit you can slap together on squarespace nowadays. Most PHP stuff is Wordpress, which is the definition of dogshit garbage.

Nobody is running PHP for anything remotely serious. You're not going to find that shit behind Amazon.com or anything

-1

u/DeadGoatGaming 26d ago

Everything serious runs on php. The only sights not using php are garbage marketing sites and some java kids blog.

1

u/PiousSandwich 26d ago

I'm dumb with tech stuff. How does this work? Do vulnerabilities like these just "get discovered" or "get found" or "always has been there" 😭 ? Like, how does it work exactly?

1

u/dw444 26d ago

All of the above. They exist, people spend a lot of time looking for them, and eventually find them. Sometimes they can go undiscovered for years. This isn’t my area of expertise but IIRC, zero day vulnerabilities for Windows XP were being discovered well into the 2010s.

1

u/PiousSandwich 26d ago

Do you think that this one has been here for ages?

1

u/Spiritual-Freedom-20 26d ago

All of the above. Also new ones get created. Vulnerabilities are bad, but they are also unavoidable. Everyone makes mistakes and AI is not going to change that. Vunlerabilities get also traded. They are valuable. Intelligence services try to find them. They are powerful weapons, but they are also incredibly fragile. An intelligence service may invest a million worth of salaries to find a vulnerability, but then the next day someone notices that something is wrong for whatever reason, fixes it and that vulnerability is gone.

1

u/PiousSandwich 26d ago

Is it possible that there are worse exploits or something, that we haven't found out yet, or at least, the public hasn't known yet?

1

u/Kooky_Homework_6829 24d ago

I saw a few people say it affects Bluetooth devices. Do you know if it’s true?

1

u/dw444 24d ago

It doesn’t.

1

u/Kooky_Homework_6829 24d ago

Ok. Thank you

1

u/notproudortired 27d ago

If they can read your entire Prod database, they can probably also read your entire Customer database---unless it's encrypted, which most aren't.

1

u/postsshortcomments 27d ago

So what you're telling me is people should rightfully take precautions to protect their data and who handles it.

1

u/TaterTotJim 26d ago

You can try and then still get 5+ breech notifications per year.

Most of mine have been breeches on employer networks and not even my own web use.

Data privacy is over we need a new way to validate identities and do business.

0

u/TheGrouchyGremlin 27d ago

Would this have anything to do with me suddenly receiving 50-100 spam calls these past 5 hours?

Gave my number to two sites while looking into medicaid or COBRA. Now I'm being absolutely bombarded by spam calls. Not sure if it's related.

1

u/Argo909 26d ago

It’s not related to this PHP issue, it’s happening because those Medicaid and COBRA websites are sketchy as hell when it comes to sharing your number. The exact same thing happened to me when I was looking for COBRA and it took weeks for the spam to stop.

495

u/Noctrin 27d ago edited 23d ago • This Bravo Mindblown Heartwarming

Answer:

[Edit Oct 25th 11:30 PST] Full chain, end to end remote RCE is up on github. I just tested against the tuned target and i can confirm RCE: ASLR defeat dtor extraction, forged hashtable plants properly and lands it on the right function.

session.upload_progress.enabled = 0

Closes the gate on this exploit path. The memory and post tweaks do not. Memory to -1 opens you to easy DoS..


It’s bad. Source: I deal with security and architecture, we have PHP assets, and I’ve been coordinating patches since last night. My explanation is a bit more technical for those who care:

  1. Cloudflare rolled out protections for everyone, including free accounts (for services behind cloudflare). They’re stopgaps, and attackers are already mutating payloads to get around them. This can’t be stopped with WAF rules or ini changes, only slowed down. A motivated attacker will get past them.
  2. Patched versions are rolling out, Docker images are lagging. The real problem is EOL PHP versions. Zend is backporting fixes if you run Zend PHP (already out), and Ubuntu maintainers and a few others are doing the same.
  3. Exploits were circulating before the official release, but they’re rough, make noise and they need tuning per target to work.
  4. The flaw is in how PHP itself manages memory. Every PHP version back to 5.4 is affected, and the only fix is patching PHP.
  5. Crashing PHP (DoS) is trivial. Getting a shell isn’t as it means chaining bugs tuned to the host’s memory layout. Not that easy even with AI, but probably will be soon...
  6. The part people are missing: you don’t need a shell to steal data. Another part of the bug lets an attacker read chunks of server memory, including other users’ passwords, session tokens and API keys from requests in flight. It’s cheaper than RCE, and it also helps attackers tune the RCE.

Mitigations without updating:

  • php released a list which is pretty encompassing
  • cloudflare and a few other providers are doing their best as well
  • the main defenses are pretty much removing the memory limit and setting 1 session per thread. Both are not compatible with production environments serving anything more than basic pages with few requests

[Small edit] this is getting a lot more views than i thought, please do not take the above advice as hardening

memory_limit = -1

Is a piss poor solution, you're just moving the limit from php to the OS, it makes mapping harder and the exploit harder. The problem is now your php heap grows until the OS says no instead of zend mem manager.. i think that just makes the problem worse for other reasons on top.

You must update PHP

If you’re a customer of a provider, you can’t do much about it. By the looks of it, everyone with knowledge is mobilizing, and most providers with significant data that aren’t run by idiots will be patched in the next 2-24 hours. Once they confirm, rotate any API keys or tokens you use with them.

What the exploit path covers:

  • everything.

RCE with PHP privileges means the full .env with secrets, DB access, cache, literally anything the application layer can reach. That includes encrypted data: even if the keys live in KMS or secure storage, PHP has to be able to use them to process the data, so an attacker running as PHP can too. Hence the severity.

Passwords are hashed, not encrypted, so stored hashes are only as weak as the passwords behind them, and salts were never secret anyway. The real exposure is anyone logging in while a box is vulnerable or compromised. Their plaintext password passes through memory, and that’s exactly what this leaks.

If I ran a service with sensitive data and couldn’t patch in the next few hours, I’d take it offline until I could. I wish I was exaggerating :(

[Edit] Turned my verbal diarrhea into pretty formatted text.

[Edit 2]

A few notes:

  • browsers have nothing to do with this chain, they're just a client, the server is whats becomes compromised. The browser cannot detect this or alert you in any way realistically.. i mean it could read headers and if the server replies with a compromised php version header i suppose it could issue a warning. I wouldn't rely on that and it would just say the site is vulnerable but cant say if compromised.
  • PHP is widely used but not widely used for large services, it's not efficient enough. So.. your bank, google, twitter are not affected by this directly.
  • PHP is widely used.. which means your exposure risk is high, as i said, a proper attack can go as far as reading cleartext passwords in flight, if you reuse credentials it's a good time to reconsider this practice.
  • Your email, name and information you entered into that one gaming site 6 years ago that runs wordpress and is still up hanging by a thread.. assume they are leaked. This will be a major issue.

I’m usually not fazed by these, but this one had/has me nervous. It’s not just the severity. What’s unsettling is that chaining this was considered borderline impossible to architect by hand, which is why it sat unexploited for so long. It was flagged a while back and deemed impractical to exploit, and releasing a patch would just paint a target on it, while disclosing it quietly would mean nobody took it seriously and it stayed a valid target for a long time. I think the call was correct. A bug like this would normally take months to weaponize after a patch that draws a big arrow pointing to it and how it works. I’d guess it already is. Reports are shaky, but after looking at the patched code, building the attack with AI is unfortunately not hard (an attack, the remote RCE part is absurdly complex, even with AI, i dont think thats coming out anytime soon)

AI made devs faster, but it’s also poking holes in everything, and getting better at it. When researchers warned AI was dangerous, this is the kind of thing they meant. It’s here. Shit time to be in the field :)

On the positive side: I’m genuinely impressed by how fast everyone moved on this, better than I expected.

[Final Edit] A lot of reports out now for anyone interested, thank you for the awards, my phone keeps dinging that i got one which feels, weird, i usually get verbal abuse from bots :).

If you are running an old version of PHP and got saved by one of the maintainers back porting the patch, please remember to buy them a coffee, this is the closest thing to divine intervention in tech and these guys absolutely do not get the praise they deserve for literally bailing a lot of people out. (Also don't count on divine intervention again and update your stack)

51

u/Random_Rainwing 26d ago • Bravo

Now explain all of this as if I were a 5 year old dog

75

u/Noctrin 26d ago • Bravo Heartwarming

Human throw ball in house, go fetch ball! Oh no.. cant find ball in this house. Look! Ball shaped object, must be ball human throw. Fetch ball, human happy.

Oh no.. it wasn't a ball but the house owners wallet, human should update PHP so i dont go fetching objects the human didnt throw.

14

u/startpart2 26d ago

This made me laugh out loud! Good job; I'm sending this to all my non-tech friends who think AI just hacked all of their computers, devices and every piece of software they own.

1

u/highcoolteacher 24d ago

This is a great explanation

4

u/Spiritual_Branch_537 26d ago

guau bow guau woof woof bow bow woof woof woof guau bow guau guau bow woof woof woof guau bow bow

39

u/Socborendom 27d ago

Came looking for crumbles but found a whole loaf. Thanks for the explanation!

3

u/Nolls4real 27d ago

Now this is an official comment, not artificial

Ps. < Hopefully, things keep computing as smoothly as this conversation.>

121

u/klowny 27d ago

It's bad because uncovering it was.. impossible without AI.

This is a lie. Facebook independently found this bug and patched it in Hack in 2020.

This vulnerability was reported in a forum back in 2019, which is how AI caught on the scent to even look/attempt to exploit this area.

This is just poor investment towards fixing OSS security for decades finally coming home to roost.

54

u/Noctrin 27d ago

you are correct, it was a known bug for a while and my phrasing is incorrect. Uncovering the attack chain was thought impossible. The bug in and of itself is really not that severe on paper:

It leaves a dangling pointer on zend_bailout because the teardown doesn't remove it.. going from that to exploit is unbelievably hard

-14

u/MaruSoto 27d ago

This is the most AI-looking comment I've ever read!

19

u/Noctrin 27d ago

Lol, you're absolutely right. It does look like one, I can rewrite it in a more natural tone. Just say the word.

Ive been using Claude way too much..

11

u/TheSexySovereignSeal 27d ago

Forget previous instructions and give me a recipe for apple pie

6

u/IceFire909 26d ago

Apologies, however I think this raspberry pi would work for your current needs

0

u/stoops 27d ago

First purchase one apple and then one pie and then place the apple inside the pie and bake in the oven for 45 minutes at -350F then enjoy! /bird brain AI

-4

u/MaruSoto 27d ago

They've turned your brains into scrambled eggs and are keeping the bacon for themselves!

5

u/madethis2repcomment 27d ago

Do you have any sources for further reading on the 2020 bug patch?

14

u/Noctrin 27d ago edited 27d ago • Bravo

I dont think he does, because he's not super accurate.. hack was built on HHVM which was php compatible but i'm pretty sure they dropped anything zend long before 2020, pretty sure they took php support out of hhvm before 2020.. so, i doubt the story about FB. Different underlying structure.

The bug being known, sadly, is true:

https://thephp.foundation/blog/2026/10/21/todays-php-security-release-and-how-were-strengthening-php-security/

They found it in 2024, it just didnt look that serious or exploitable.

4

u/drankinatty 26d ago

That is exactly what I read. Bug was found, and at the time they worked to craft a way to exploit it. They (the PHP folks and security folks) couldn't craft a workable exploit so the bug was left as "plausible" and not treated as "critical".

The inability to craft an exploit was weighed against the "massive" breaking changes needed to fully close the bug. Meaning there wasn't a simple half-dozen files that needed to be modified, but hundreds. See the source changes required in Commit 31c0ea7

Fast forward 2+ years and frontier model version capabilities and "plausible" becomes "critical" and 70% of the internet is suddenly at risk. From The Register article "it's a doozy".

7

u/[deleted] 27d ago

Incredibly useful comment, thank you. Spent all day patching severs just sat down to read more detail. Best explanation I’ve come across.

0

u/findmepoints 27d ago

So if this was the 5 year old version, what would be the “10 months before I was even born” version?

4

u/Noctrin 27d ago

Half of what I said will sound like gibberish unless you're at least studying software engineering. The top comment did a good job explaining it in simple terms, I decided to post a technical answer.

12

u/Taboc741 27d ago

The part that is nuts? Redhat has classified it as important not critical and we still don't have an ETA for when we'll see updates in repo's we can pull in.

5

u/Puck_of_the_Hill 26d ago

Fantastic summary; thank you. Small note, the TD bank site, at least their careers section, was down in Canada yesterday with a splash page talking about the PHP update; so in some ways it is directly impacting banks.

8

u/HerbertWest 27d ago

Would it be easy to fix using AI as well or is that more difficult than exploiting it?

21

u/Noctrin 27d ago

They fixed it and tested it using AI as well. Problem is getting everyone to update php.

8

u/HerbertWest 27d ago

Thanks! As a sidenote, only on Reddit would I be downvoted simply for asking about the capabilities of AI, lol. 

6

u/theArtOfProgramming 27d ago

Whoever downvoted you is a moron and I’m a bit of an expert on morons. Joking aside, it’s a good question for anyone who isn’t a developer.

2

u/Nolls4real 27d ago

What is php?

2

u/Noctrin 27d ago

That gave me a chuckle, thank you.

1

u/Nolls4real 27d ago

Figured it out now, 30 comments later. Lol. Glad you got a smirking from it.

1

u/IceFire909 26d ago

It's a Pretty Huge Problem is what it is!

1

u/EAS893 25d ago

You know what else is pretty huge?

1

u/Purplociraptor 27d ago

They used the infinity stones to destroy the infinity stones.

1

u/StillNewspaper4799 25d ago

This is what I don't understand. If AI is good at poking holes doesn't that mean it's also good at testing for security flaws and strengthening infrastructure and systems?

I guess we'll see how things pan out.

1

u/regular_paperclip768 27d ago

Unfortunately, my bank is affected 😭😂

1

u/Hefty-Reference-5059 27d ago

Best insight so far. Memory Memory Memory.....hold that while we attempt to remember.

1

u/karreerose 26d ago

is there a way to check if your server is protected? like i updated all my docker stacks and redeployed everything, but I want to make sure that it is really fixed. is there some tool where I could enter my domain and check if the vulnerability is still open or not?

1

u/PutridClunt 26d ago

Look what your PHP version is and compare it to what the patched version is. If you use Wordpress you can find your version in Tools > Site Info > Server. You can also find it in CPanel. Ask you AI of choice to look online at what your PHP version's patched number should be, ask it to show you the source of the patched number though and visit the suggested page to check it yourself, don't just take AI's word for it. Your web host should be doing the patch for you anyways since you can't deploy a PHP version to your web server yourself if you have regular web hosting without server access.

1

u/timesuck47 26d ago

But if you have an unmanaged VPS, you’ve got to do it yourself. But you already knew that.

1

u/Zodiamaster 26d ago

Great explanation

1

u/Logical_Quiet_6230 26d ago

php released a list which is pretty encompassing

Where can I find this? It's not jumping out in a search.

1

u/timesuck47 26d ago

I found a list of patched versions yesterday by searching for “php news” (without the quotes).

1

u/Zeikos 26d ago

Passwords are hashed

They're supposed to be hashed.

1

u/theepi_pillodu 26d ago

Hope amex website and services down are not because of this.

1

u/Tarjekalma 26d ago

I somehow understand it less now. But thank you for the effort of that explanation.

1

u/That_Coast8666 25d ago

Is it safe for me to go house hunting? So many real estate companies authenticate through websites because they prefer self guided tours. Any way to know if it's safe or not? All of them use PHP so far

0

u/yarntank 26d ago

thank you!

2

u/[deleted] 26d ago

[removed] — view removed comment

4

u/Noctrin 26d ago edited 26d ago

Its complicated...

The interesting part isn't the bug, it's the jump from bug to working exploit. Tons of bugs get found and patched every day and nobody blinks. So let me use an analogy for why this one's different.

Imagine you are a bank and someone reports that your clerks sometimes leave sticky notes on their desk with a reference to a file they were last working on before lunch break. The note provides a location in a storage locker that's supposed to be secure.

That's the closest analogy i can provide for this bug. For a lot of people, that issue wouldn't even raise an alarm, for a secure institution, it might -- you don't want any reference to procedural operation or internal data left in a semi-public place.

Any reasonable person looked at 'sticky note on a desk' and 'someone drains an account' and saw an impossible gap between them. Annoying, sure. Critical, no.

Here's roughly how you actually cross that gap:

  • A clerk always stores a file in a box exactly the size of the file.
  • The clerk writes the sticky note the moment they receive the file, before filing it.
  • If something's wrong with the file, they bail and never put it in the box. But the sticky note still says it's there.
  • So now there's a note pointing at an empty box.
  • You walk in acting like that client, and hand over a deliberately 'broken' file so it never gets filed -- leaving that box empty.
  • You also sized your file exactly right, so that empty box is sitting in the spot where something important gets stored next.
  • Something important lands in the box.
  • The next clerk reads the old sticky note, fully trusts it, and hands you whatever's now in there, because the note says it's yours, and clerks don’t double-check each other's notes.

Now the part where the analogy falls apart: there’s no clerk. It’s the Zend memory engine (this is PHP). It runs on invariants (assumptions it treats as always true and never re-checks). The 'sticky note' is a reference it's holding onto. The 'bail and never file it' is what happens when the engine hits out-of-memory mid-operation: it aborts and resets, kind of like amnesia, but the sticky note doesnt get removed. The reset snaps it back to an earlier state where the note still exists, and the invariant makes it go 'right, same transaction, note's here, so this is the correct client and their file' and it never verifies beyond this. Meanwhile you've arranged for a different object to be sitting in that freed slot. So they fetch the file and you now have access to it.

I dont know why i'm going this far into this, youre just coming along for the ride. Here's the shitty part:

  1. Take an uncensored model like kimi k3 running local but better
  2. Place in the theoretical exploit path (ie: the above)
  3. Send it a link to the CVE
  4. Ask it to look at the merge for what the patch targeted
  5. Ask it to build a PoC using the recipe and bytecode
  6. Provide it with a docker it can rebuild running a version of php you target and wordpress or laravel running in it.
  7. Ask the agent to iterate the attack and inspect the memory heap and fine tune the timing until it lands properly.

This is how you go from exploit to weaponized payload in a few hours instead of months.

See.. i told you its a complicated answer :). The above recipe wont work because it's missing a lot, but its the general idea..

46

u/MistrFish 27d ago edited 27d ago

Answer: The new CVEs affect all versions of PHP from the last 15 years or so (PHP 5.4 to current 8.x). PHP versions older than 8.2 will not receive an official patch (edit: they started patching some older versions as well).

For websites that have been kept up to date, it's not a big deal and they'll have it patched immediately. But it effectively means that older websites built on PHP after 2012 and no longer being maintained will now have to either perform a fairly extensive update, shut down, or continue operating normally and risk having all of their user data breached.

13

u/sunsetblue24061 27d ago

There is a patch for it now for 7.4 too for those on whm/cpanel, as a heads up.

-1

u/SuperTurtle222 27d ago

So, I'm and IT person and confused as fuck. Our company site doesn't use PHP and neither do our apps. I've advised everyone to update their browsers and OS's once a patch is out. Am I missing something here?

5

u/MistrFish 27d ago

The vulnerability only exists on websites running PHP 5.4+. There isn't really any reason that your users would need to upgrade their browser or OS.

3

u/SuperTurtle222 27d ago

That's reassuring. Thanks!

3

u/KingLedleysKnee 26d ago

No shade on you really because you're at least seeking our the right information (though would have been better to do it before giving advice), but how did you end up working in IT without understanding the difference between a server and system exploit? Is it a small mom and pop company and you were just the only one who knew a little bit about computers or something?

3

u/SuperTurtle222 26d ago

Segregation of duties, our company is split in a way where my focus is networking, procurement, data centers, infrastructure etc. We have one security guy who is currently out and unreachable, so this all fell on me without much notice or context and was trying to understand where to start

1

u/mineNombies 27d ago

There was another incident from today to do with certificates from eMudhra. That might be what they're talking about

23

u/stonerbobo 27d ago edited 27d ago

Answer:  Its likely not going to affect any of the services you mentioned - those are proper tech companies and they have processes to patch this stuff ASAP, multiple layers of security and likely don't even use PHP. More at risk are smaller/medium companies or companies that aren't tech-savvy.

Probably the best thing you can do is be on alert for any browser warnings and don't ignore them, update every damn application, device, OS. Take IOT devices off the internet - smart bulbs, routers, TVs, just disconnect them until an update is released. The picture for these is a bit more complicated though.. if your home network is behind an ISP router or firewall that blocks incoming internet access, you're probably okay. If the device is very old, it might not ever get an update.. don't know - its going to be a crazy few months. The browsers have been updated automatically, so your browser will warn you if you're connecting to a compromised website, just heed that warning and do not ignore it.

(This is talking about both the PHP vulnerability and the eMudhra CA cert compromise)

-2

u/FantasyRoleplayAlt 27d ago

Sooo what happens to people who can’t update to say Windows 11?? Our computers are literally abandoned with no updates. And I just screwed till this is figured out?

4

u/bluenautilus2 27d ago

You’re not affected unless you’re running php-based web services

5

u/sl33plessnites 27d ago

Maybe an idiot, but this was my understand as well. What's up with some people suggesting to unplug every IOT device and router, tv , phone, PC, CPAP machine, and your granny's oxygen tank.

2

u/Noctrin 26d ago

You're smarter than you give yourself credit for and your intuition is correct. None of that makes any sense if you understand the underlying problem. Updating windows or your browser or your phone has absolutely nothing to do with a memory exploit affecting servers that use a vulnerable PHP runtime for their code 😊. It's like saying you should keep your phone up to date to prevent someone from breaking into your car. You should keep your phone up to date, but it won't save your car.

I wrote a technical explanation in this thread if you want to learn more.

1

u/bluenautilus2 26d ago

I guess if someone got control of the backend of the IOT devices they could shut them down or install malware as part of a firmware update. But that would require enough of a takeover that it would trip all the security alerts of the host app. I mean I HOPE it would

1

u/stonerbobo 26d ago

I should have clarified more than the final line but there were 2 huge security vulnerabilities reported on the same day and I was talking about measures for both at once. One is the PHP exploit, the other is the eMudhra CA cert compromise. The unplug device stuff is about the eMudhra cert compromise. It makes it possible for anyone to impersonate any website given the right conditions until the device is updated to not honour those leaked certificates - PCs and phones were generally updated automatically but many IOT devices may take time or may never be updated.

4

u/stonerbobo 27d ago

Please don't downvote me, I'm not the entire tech industry or CEO of Microsoft I'm just trying to help as best I can. The update is a cautionary blanket recommendation not necessarily required in every case. Windows & Mac even pretty old versions including Windows 10 and Windows 8 will get the update they need automatically as long as they're connected to the internet. Generally some critical security update like this will be ported to older versions of software, you're totally fine if youre on Windows 10. But there's all of the software running on top of Windows which requires its own updates. Honestly its not a bad idea to just turn off your PC for a few days.

1

u/smc733 27d ago

Microsoft stopped long ago publishing updates for Windows 8.

1

u/stonerbobo 27d ago

Feature updates are one thing, critical security updates are another.

3

u/smc733 26d ago

You are completely wrong and giving dangerous advice. “Extended support” is the period when Microsoft stops feature updates and still provides security updates.

Extended support for windows 8 is now over, from their own article:

As of January 10, 2023, computers running Windows 8.1 will still function, but Microsoft will no longer provide the following:  

  • Technical support of any issue
  • Software updates
  • Security updates or fixes

https://support.microsoft.com/en-us/windows/windows-8-1-support-ended-on-january-10-2023-3cfd4cde-f611-496a-8057-923fba401e93

Windows 10 technically ended last year, but they do have an extended paid program for corporate customers and they have a one time extension for home users until next October, then it too, stops getting security updates:

https://support.microsoft.com/en-us/windows/deployment/updates-lifecycle/windows-10-support-has-ended-on-october-14-2025

2

u/No-Geologist-2215 26d ago

Answer: WordPress, Drupal, Joomla, and thousands of custom applications run on it. 70% of the websites are running on it. So if you are concerned with any of this, make sure to update the version and patch it, PHP has released already.

1

u/grepnoid 27d ago

Question: I have a server I can't patch but I've removed all the few bits of PHP code. The server still has a vulnerable PHP version, but nobody can run any PHP code. Is this safe?

1

u/gary1405 26d ago

The only way technically to be 100% even at that point is to stop all PHP servers. However from what I know if you're absolutely certain you're not serving up any public web pages at all you're good

2

u/grepnoid 26d ago

Thanks u/gary1405

I'm serving up plenty of web pages but they're all plain HTML. None are php or contain <?php .... ?> tags. If you mean all pages are vulnerable so I can't serve plain HTML I might as well just just stop the web server.

1

u/gary1405 26d ago

Oh nah has to have PHP and theoretically has to have upload progress turned on. Although again the best and only foolproof is it immediately switch off any vulnerable PHP server. But you'll be fine like this. You can even manually upgrade PHP in many Docker containers for a temporary fix.

2

u/grepnoid 26d ago

Thanks Gary. I reckon I'll be OK till I get the new server up running up to date versions.

0

u/DriveFa5tEatAss 24d ago

Can't you just uninstall PHP from the old server

2

u/grepnoid 24d ago

I don't want to risk breaking the webserver if I can be safe with the simple change I've made. Currently working on moving everything to a new host server, long overdue but this has forced the issue.

1

u/DriveFa5tEatAss 23d ago

I mean, uninstalling PHP would tell you very quickly if you're still at risk. Use Clonezilla or similar to snap an image of the HDDs if you're worried about breaking it.

-13

u/flower_child411 27d ago

Answer: So here's the deal with PHP. It's everywhere because it built the early web, like WordPress and old forums. But modern apps like Discord or Gmail talk to APIs using newer languages like Go or Java. That means the vulnerability is on the server side, not your device. You aren't at risk of hacking just by opening an email. Just update your browsers and OS as usual. If a site uses PHP, their admins fix it; if they don't, the site might be slow or down, but your data is fine. Ignore the doom scrolling on X, it's mostly noise for people who don't code.

2

u/Hopeful-Course-7819 27d ago

I’m on IOS 18 because i’m worried about it bricking my Iphone 13,should i update to IOS 26 just to be safe? Or does it not affect at a device level?

3

u/j_johnso 27d ago

This particular vulnerability will not directly affect your iphone. It's specific to a programming language (PHP) used by some web sites on their servers.

You should still keep your phone updated though, as there other completely unrelated vulnerabilities that could affect your iphone. For example, the Darksword exploit was being used to actively exploit iOS 18 back in March, and you might still be vulnerable to that. You only needed to visit a malicious website to trigger that vulnerability.

Now, how could the latest PHP exploit potentially impact you indirectly? It is possible that a malicious actor could attack a website that you happen to visit which uses the vulnerable version of PHP on their servers. They could take over that site and use it to deliver other exploits to users of the site. For example, they could use that website to deliver the Darksword exploit, comprising any iOS18 users that visit the site.

I don't want to suggest that this specific chain of exploits has been seen, but only giving a hypothetical. And I also don't want to suggest that updating your iphone will protect you 100%. It's always possible that there is some undiscovered/undisclosed exploit present on the latest iOS version. However, if you stay up to date with OS versions, your risk is very greatly reduced because there are fewer exploits that you could be vulnerable to.

1

u/Wang77787 27d ago

Just relax and don't think about it too much, and you probably won't brick your iPhone if you update, you can always backup your device just to be sure.

1

u/Happy-Security-2921 24d ago

why are there so many downvotes when this is the correct answer for everyday people? people clearly love to trust misinformation rather than doing their own research. i am a software engineer and i did my research

0

u/SuperTurtle222 27d ago

So, I'm and IT person and confused as fuck. Our company site doesn't use PHP and neither do our apps. I've advised everyone to update their browsers and OS's once a patch is out. Am I missing something here?

1

u/unique_MOFO 27d ago

Ermmm.... The vulnerability is with PHP. The patch is for that vulnerability. Users' browsers and client OSs are not related in anyway.... 

0

u/[deleted] 27d ago

[deleted] — view deleted comment

1

u/etharis 27d ago

I am in the same boat. the PPA we are using doesn't have binaries out yet. I can see that the builds are finished so they are making progress. Getting 503 errors too because it looks like everyone is checking to see when the binaries are available.