03 · Editor’s Letter
They kept the flaw under embargo. The attack was already running.
An embargo is a promise about time. The people who find a flaw agree to keep quiet until the fix is ready, so defenders get the first move. This week that promise failed in public. Two critical flaws in PHP, the language under WordPress, Drupal and Wikipedia, were found with frontier models, then leaked before the fix was ready. By the time anyone could patch, attackers had been working the flaw for days.
Zvi Mowshowitz opened his week with a sentence nobody wants to write: “It was the probably worst day in cybersecurity history. So far.” Most of Friday’s bag is about what you can still control once the head start is gone, and the answer keeps turning out to be unglamorous. Know where your servers are. Keep a live list of your keys and who owns each one. Write the rules an agent must obey into the systems it touches, not into a prompt. Decide which agents you let through the door before one walks in.
A small email from the publishing platform PublishDrive makes the point at ground level. It took the platform offline as a precaution, installed the official PHP fix, and was back online within a few hours, with no sign that it or customer data had been compromised. No heroics. A plan, a switch, and an owner. That is what the rest of this issue is asking everyone to build.
Skip cover