Two PHP Bugs, One Leak, and a Secret Key That Was Just the Number 4

Grab a coffee. Actually, after you read this you may want a beer instead.

Two stories broke this week. In the first, details of two serious PHP bugs leaked before the fix was ready. In the second, a company that vouches for website identities turned out to have used the number 4 as a secret key. Just 4. We'll get to that one.

Nobody gets called out in this post. We're going to walk through what happened, what it means for you, and what to do about it.

What Is PHP, and Why Do I Care?

PHP is a programming language that runs the back end of a huge number of websites. Contact forms, login pages, and shopping carts are all places where PHP is probably doing the work. It also lives inside a lot of devices that have their own web page, like the network storage box in your closet. More on that below.

The Two Bugs

They're tracked as CVE-2026-109618 and CVE-2026-109619. (A CVE is a recall number for software, same idea as a car recall.) People are calling the pair "PHP2Shell." Both score 9.2 out of 10 for severity, which is the part of the scale where you stop what you're doing.

Both are remote code execution bugs. A stranger on the internet can get your server to run their commands without a password and without being invited. It's like someone shouting instructions through your mail slot and your house following them.

The two bugs get there in different ways. One involves what PHP does when it runs out of memory. The other involves PHP continuing to use a piece of memory after handing it back, which is a bit like using your hotel key card after checkout and walking in on the next guest. Researchers also say some paths can leak things like passwords and tokens from other visitors.

Why This Disclosure Wasn't Great

There's a normal process for this called coordinated disclosure. A researcher finds a bug and quietly tells the software maker. The maker builds a fix. The fix and the announcement go out together, so people can patch before attackers finish reading about it.

Say an inspector finds that the back door latches on your whole street don't catch. The normal way is to tell the builder, wait for new latches, and then tell the neighbors. What happened here is closer to someone pinning the list of unlatched doors to the community bulletin board while the hardware store is still closed.

On October 20, a post appeared online claiming two critical PHP bugs were about to be announced. It listed the ID numbers. The post was deleted soon after, but screenshots were already circulating. Researchers at watchTowr confirmed the bugs were real, the PHP team moved its release up, and patches shipped on October 21. That's a fast turnaround, but attackers had a head start, and researchers are now reporting exploitation in the wild.

We're not blaming anyone. Leaks happen, and plenty of people work hard on this stuff. An embargo is an agreement, and it only holds as long as everyone keeps it.

If You Run PHP and You're Reading This, It's Already Too Late

The fixed versions are PHP 8.5.12, 8.4.27, 8.3.36, and 8.2.35. If your website or device runs PHP and was reachable from the internet while these bugs were public and unpatched, assume someone has already tried it and may have gotten in.

Patching matters, but it only locks the door. It doesn't remove anyone who is already inside, the same way a new deadbolt doesn't remove the guy on your couch.

PHP 5 and 7 are affected too, and they have no official patch. Plenty of older sites still run them. If that's you, the plan is to move to a supported version.

If you think you were exposed, patch first. Then look for things that shouldn't be there: admin accounts you don't recognize, files you didn't upload, settings that changed. Change passwords and keys. If you aren't sure, restore from a backup you trust or call someone who does this for a living. Asking for help is fine.

The Hidden Danger: Gadgets With a Web Page

PHP also lives inside devices that have a web page of their own. The most common example around here is the Synology NAS, the box in the closet or under the desk that holds the family photos, the business backups, and the spreadsheet you meant to delete. A lot of them run PHP for Web Station and various apps.

At the time of writing, there is no vendor advisory from Synology. It's early, and we'd expect some sort of statement confirming whether it's affected or not. Whether your particular box is affected depends on what you've installed and how it's set up. Web Station, third-party packages, and plug-ins can all bring PHP along with them, so two NAS devices sitting side by side can have very different answers.

Synology ships its own copy of PHP. You can technically update it yourself, but we wouldn't suggest it unless you're well versed in that kind of thing. For most people, the safer move is to wait for Synology to release the fix. In the meantime, Shodan (basically a search engine for things plugged into the internet) shows nearly 40 of these NAS devices exposed to the internet in the Erie area alone. If one of them is yours, treat it as possibly compromised until you've checked it out.

Honestly, you probably shouldn't expose a NAS directly to the internet in the first place, and this is a prime example of why. It holds everything you care about and runs a lot of software, and every service you leave reachable is one more place for a bug to show up. Today it's PHP. Next month it'll be something else. Turn off any port forwarding on your router that points at it, and if you need your files while you're away, use a VPN instead of leaving the front door open.

Now, About That Number 4

Different story, same week. To see why it's funny and why it's a problem, you need a quick look at how your browser knows a website is the real one.

Companies called Certificate Authorities work like the passport office of the internet. They issue digital ID cards, called certificates, to websites. Each one has secret signing keys that work like a notary's stamp, and the whole system only works if that stamp can't be copied.

A proper secret key is a huge random number. There are more possible values than there are atoms in the universe, so guessing one isn't realistic.

eMudhra is a Certificate Authority in India that has issued over 60 million certificates. Researchers found that eight of its signing keys were tiny numbers. One was 4. Others were 56 and 115. Anyone could find them by trying the numbers 1 through 256, which a laptop does in under a second. It's a bank vault with the combination 0-0-0-4.

eMudhra says a bug in its key generation script accidentally created a second, weaker set of keys, and the wrong set got picked because the labels looked alike. Anyone who has grabbed the wrong folder off a desk can sympathize. The keys were weak from the day they were created in April 2025, and a researcher reported the problem on October 17. eMudhra says it found no evidence anyone used them against real users.

With those keys, someone could forge an ID card for any website. They would need to sit between you and the site, like on a shady public Wi-Fi network, so most people were never likely to be hit. It still needed fixing.

How Revocation Works

When a key goes bad, the issuer can revoke it. This works like the lost-or-stolen card list a store checks before accepting your credit card. Browser makers also keep their own do-not-trust lists and push them out in the background.

That's what happened here. Firefox and Chrome blocked the bad certificates on October 17, and Apple followed on October 19. In many cases nobody had to update or restart anything. The browser or phone you're reading this on was almost certainly protected before most people heard about the problem.

Your Forgotten Gadgets Didn't Get the Memo

Revocation only works if your device actually checks the list. The TV that went end of life a few years ago probably doesn't. Same for the old baby monitor, the printer from 2016, and the smart fridge. They stopped getting updates, so the recall notice never reaches them. It's like mailing a safety recall to an address you moved out of years ago.

Some software never checks at all, including certain developer tools, and researchers are asking for updates there too.

You'll run into this more as the pile of connected devices in homes and offices gets older. If something connects to the internet and no longer gets updates, it's a houseguest who never left.

Your Short To-Do List

[THIS_WEEK_CHECKLIST]
1. PHP SITES: Ask your web host or developer today to move to 8.5.12 / 8.4.27 / 8.3.36 / 8.2.35
2. PHP 5 OR 7: No patch exists. Plan a move to a supported version.
3. SYNOLOGY NAS: Remove it from the internet (no port forwarding). Use a VPN for remote access.
4. IF EXPOSED: Assume compromise. Change passwords, look for unknown accounts and files, restore a clean backup if unsure.
5. INVENTORY: Write down every internet-connected device. Circle the ones that no longer get updates.
6. END-OF-LIFE GADGETS: Replace them, move them to a guest Wi-Fi network, or unplug them.
7. EVERYTHING ELSE: Keep auto-updates on for your phone, computer, and browser.

Both stories come down to software and devices people forgot about. A short inventory and a regular patch cycle covers most of it, and if you want help with either one, you know where to find us.

Sources