◆ NOISE IN → SIGNAL OUT◆ READALCHEMIST.COM◆ FREE / NO PAYWALL◆ NOISE IN → SIGNAL OUT◆ READALCHEMIST.COM◆ FREE / NO PAYWALL
THE DIGITAL ALCHEMIST
SecurityIMPACT 92

The One-Man Security Team Running 70% of the Web

Ondřej Surý, a volunteer PHP packager in Czechia, wrote the fixes for two critical use-after-free bugs that hit roughly 70% of websites. The patch worked. The staffing model behind it did not.

2026-10-235 MIN READ#PHP · #vulnerability management · #open source sustainability · #Cloudflare · #CVE-2026-109618 · #CVE-2026-109619 · #Ondřej Surý
The Digital Alchemist
The Digital Alchemist

Here is the sentence that should scare you more than the CVSS score: one person, working in his spare time out of Czechia, is the reason roughly 70 percent of the internet isn't currently running exploitable code.

That's not hyperbole. When The Atlantic's Charlie Warzel went looking for whoever fixed the two critical PHP vulnerabilities disclosed this week, he found Ondřej Surý, a volunteer most of the industry had never heard of. (cite index="18-4,18-5,18-6,18-7,18-8">"70% of the internet was vulnerable yesterday to very bad security flaws inside a coding language. Turns out, one volunteer is mostly responsible for maintaining that code & helping push updates. Yesterday Ondřej Surý saved the internet."

Developer Ian Landsman put it more bluntly: (cite index="18-11,18-12,18-13,18-14">"Explaining to my wife how there's this one guy. And he alone is responsible for most of the world's distribution of PHP. And if anything happens to this guy, that's just it. Everyone is screwed."

The verdict: the patch worked. The system that produced it is held together by one man's goodwill, and nobody has a plan for the day that stops being true.

What Actually Broke

The two bugs, CVE-2026-109618 and CVE-2026-109619, both rated CVSS v4.0 9.2, are use-after-free flaws: PHP frees a chunk of memory during an error, then a later request reads or writes to it as if it were still live.

(cite index="10-8,10-9,10-10,10-11">CVE-2026-109618 discloses server memory on its own. PHP's upload-progress handler can return freed worker memory to the client inside a PHPSESSID response cookie. That memory can contain passwords, session tokens, API keys and TLS private keys from other requests. The handler runs before application code, so the leak works even when the application never calls session_start(). That's not a configuration mistake. That's the runtime handing your secrets to a stranger before your code even starts.

Fixed versions shipped the same day: (cite index="8-6">PHP 8.5.12, 8.4.27, 8.3.36, and 8.2.35. Everything older, including PHP 7.x and 5.x installs still running inside legacy WordPress, Magento, and Joomla sites, got nothing from the official project.

Surý wrote and shipped the backports for those end-of-life branches himself, through the packaging infrastructure he's run as a side project for two decades. (cite index="7-2,7-3">He describes himself as the main Debian packager for PHP and other packages under the DEB.SURY.ORG name, providing Ubuntu PPAs for PHP, Apache2, nginx and others that are widely used as a service to the community.

Cloudflare's telemetry ends the debate about whether this was a near miss. (cite index="10-6">Cloudflare reported early attacks at 07:43 UTC on October 21, before the 14:00 UTC release. Attackers were probing the vulnerability before the fix existed.

(cite index="8-9,8-10,8-11,8-12">Cloudflare's WAF team said: "PHP sites behind Cloudflare already have an initial set of WAF rules deployed for the known exploit vectors in these vulnerabilities. The rules are available to all customers, including free. We are seeing early attacks emerging and are updating mitigations as new vectors show up. This is a STOPGAP only."

Translation: the company with the best real-time view of internet traffic on earth is telling you its firewall rules are a bandage. The actual surgery depends on whether your ops team restarted PHP-FPM.

By the next day, watchTowr moved from no evidence of exploitation to confirming it was happening. (cite index="13-9">watchTowr said at 14:19 UTC on October 21 that it is observing "active exploitation attempts" of both vulnerabilities.

One more detail: (cite index="14-1">OpenAI said its GPT-5.6 Sol model independently found CVE-2026-109618 through its "Patch the Planet" initiative in August 2026, while Wiz Research independently discovered and reported both flaws. A frontier AI lab and a well-funded security vendor both found this bug months before disclosure. Neither maintains the patch pipeline that millions of production servers actually pull from. The guy who does runs a Launchpad PPA.

If your incident response plan assumes PHP security is institutional, it isn't. It's personal.

The Digital Alchemist
The Digital Alchemist

What to Watch

Cloudflare's attack logs over the next 48 to 72 hours will show the real patch-adoption rate. Watch whether any hosting provider running Surý's packages, or Automattic-scale shops sitting on legacy WordPress, forces updates on customers who won't do it themselves. And watch whether this week's viral attention turns into actual funding for PHP's security maintenance, or whether Ondřej Surý goes back to being anonymous until the next CVE forces his name into a headline.

Sources
  1. Techmeme: An interview with Ondřej Surý, a volunteer who maintains PHP
  2. PHP2Shell: PHP RCE (CVE-2026-109618, CVE-2026-109619) — Sansec
  3. php2shell FAQ — Tenable
  4. PHP Issues Emergency Patches for Two Critical PHP2Shell RCE Flaws — The Hacker News
  5. PHP patches critical flaw hitting 70% of websites — Yahoo Finance
  6. Ondřej Surý — Patreon
  7. Techmeme: An interview with Ondřej Surý, a volunteer who maintains PHP and automates its patches, about his role in fixing two critical PHP security vulnerabilities (Charlie Warzel/The Atlantic)
  8. PHP vulnerabilities by @trending.bsky.app
  9. Techmeme
  10. Techmeme River
  11. Ondřej Surý in Launchpad
  12. PHP CVE 2026 109618 Patch For Forge Ubuntu (PHP2Shell) - Dev Problems
  13. PHP2Shell: Fixed PHP Versions and Free Check - Brandefense
  14. PHP2Shell: How to fix PHP RCE with patches and free images
  15. PHP2Shell (CVE-2026-109618/109619): Cloudflare WAF guide
  16. PHP2Shell: Responding to CVE-2026-109618 and CVE-2026-109619
  17. GitHub - eness/php2shell-CVE-2026-109618-CVE-2026-109619-PoC: Proof-of-Concept (PoC) exploit for php2shell (CVE-2026-109618 / CVE-2026-109619), demonstrating remote code execution in vulnerable PHP environments. For security research and educational purposes only. · GitHub
  18. PHP Prepares Emergency Fix as Cloudflare Reports Early Attacks on Critical Flaws
  19. Techmeme: OpenAI suspected the three fired researchers of leaking internal model designs to AI safety researcher Ryan Greenblatt, including via disappearing Signal chats (Wall Street Journal)
← back to the feed
QueryFlow
ASK

Ask your database anything.

Stop writing queries. You don't need to know SQL to get the answer. QueryFlow AI writes it for you.

Native Mac app · by yForest

  • Snowflake
  • Redshift
  • PostgreSQL
  • MySQL
  • BigQuery
  • Databricks
  • Salesforce
  • Google Sheets
  • CSV/Excel
NVDA 150.96 ▼ 2.89%MSFT 508.29 ▲ 0.40%GOOGL 282.44 ▲ 0.80%AMZN 267.74 ▲ 3.82%META 616.38 ▼ 0.40%TSLA 383.72 ▲ 0.95%AMD 530.14 ▲ 5.31%AVGO 354.05 ▲ 3.64%PLTR 156.67 ▲ 0.07%COIN 110.51 ▼ 3.92%MSTR 90.32 ▼ 6.40%NVDA 150.96 ▼ 2.89%MSFT 508.29 ▲ 0.40%GOOGL 282.44 ▲ 0.80%AMZN 267.74 ▲ 3.82%META 616.38 ▼ 0.40%TSLA 383.72 ▲ 0.95%AMD 530.14 ▲ 5.31%AVGO 354.05 ▲ 3.64%PLTR 156.67 ▲ 0.07%COIN 110.51 ▼ 3.92%MSTR 90.32 ▼ 6.40%