← Back to Blog

When the Pipes Burst and the Landlord Locks the Doors

What this week's PHP flaw and the Railway breach teach us about protecting data

Picture a street where most of the houses share the same plumbing. You never think about it. The water runs, the lights stay on, and life goes on. Then one morning the city announces that the pipes in nearly every house have a hidden crack, one that's been there for years, and anyone who knows where to look can get inside.

That's roughly what happened on the internet this week.

The plumbing: PHP

PHP is a programming language most people have never heard of, yet it runs behind a huge share of the websites they visit, including sites built on WordPress, Drupal, and Joomla. On October 21, the PHP project released fixes for critical flaws in PHP itself. Researchers at the security firms Wiz and Calif found them with the help of advanced AI tools.1 Wiz estimates that roughly 70% of websites run on PHP.1 The BBC noted that it couldn't verify that figure independently, but no one disputes that the footprint is enormous.3

The flaws had gone unnoticed for more than a decade. Wiz says they affect PHP versions going back to 5.4. In the worst case, an attacker could take control of a web server without logging in, or read passwords, tokens, and API keys straight out of the server's memory.12

Governments took the warning seriously. Cybersecurity agencies in the United States, the United Kingdom, and Europe told organizations to patch right away, or to take their sites offline if they couldn't.24 Finland temporarily shut down public government web services, and the Wikimedia Foundation took some systems offline as a precaution while it patched.3

The building: Railway

The same day, a different kind of trouble hit Railway, a cloud platform where developers host their apps and databases. Railway says it detected suspicious activity in the systems that store its customers' environment variables. Those are the settings where apps keep their secrets: API keys, database passwords, and similar credentials. The company says an unauthorized party may have accessed those encrypted values and, for some of them, obtained the decrypted contents.6

Railway paused all deployments while it investigated, invalidated API tokens, and urged every user to change every secret stored on the platform.679 Builds came back in stages over the following day. BleepingComputer reports that the platform has about 4.8 million users.8

Think of a landlord who discovers that someone got into the office where the master keys are kept. The landlord does the right thing: freezes move-ins, changes the locks, and tells every tenant to re-key their own doors. Still, for a day or two, every tenant is wondering what was taken.

What the two stories have in common

In both cases, the people affected didn't do anything wrong. They trusted the plumbing and they trusted the landlord, which is what everyone does. Most of our security still works the same way: we protect the building, the network, or the server, and assume whatever sits inside is safe as long as the walls hold.

This week showed how quickly the walls can fail, and how one crack can reach millions of people at once. It also showed that AI tools are making old cracks easier to find. Wiz says a single researcher using frontier AI models did in about a week what once would have taken a world-class team months.1

Protection that travels with the data

There's another way to think about it. Instead of relying only on the building, protect each thing inside it. Picture every important document sealed in its own locked envelope. Only the right people can open it, no matter whose house it's sitting in, whose pipes it travels through, or which landlord holds the keys this week.

That's the idea behind zero trust data protection and object-level encryption. Each file carries its own protection and its own rules about who can open it; if a server is compromised or a hosting provider has a bad week, the files that leak are still sealed.

It won't fix a cracked pipe and patching still matters. Nothing replaces updating PHP, changing exposed credentials, and watching for intruders. But it changes what an attacker gets out of a break-in: sealed envelopes instead of open filing cabinets.

The plumbing will crack again and someday another internet landlord will have a bad day. The question worth asking is simple: if the walls fail, does your data still protect itself?

At Cyber Sphere, that question is the reason we built SafePouch, which brings object-level encryption to the files you already use. If you want to talk through what it would look like for your data, we'd be glad to hear from you.

Book a Demo