Four things from the past working week that a UK board should know about, in the order I would raise them with a chair over coffee on Monday morning. It was a week in which a single bug took Whitehall services offline, a build pipeline was turned against its own users, and a regulator reminded us what a twelve-year-old password costs. I have left out the noise. What survives has a decision attached.

1. One PHP bug took 32 government services offline

On Wednesday 21 October the PHP project published fixes for two critical flaws, CVE-2026-109618 and CVE-2026-109619, which let an unauthenticated attacker run code on a vulnerable server. The European Commission, ENISA, CERT-EU and Europol issued a joint statement the same day. On Thursday the tech minister, Baroness Lloyd of Effra, told the House of Lords that 32 government services were unavailable and four partly so, largely as a precaution while updates went on. The Register reports that the Office for Budget Responsibility took its sites down days before the Budget, that peers raised the DVLA, police services and several councils, and that the NCSC sent 50,000 warnings. There is no confirmed compromise of central government systems. AWS says attacks began four days before disclosure, and the NCSC advice was blunt: patch now, or pull it offline.

For boards. Could your technology team have told you by Thursday morning where PHP runs in your estate, including inside products you buy and agencies' sites that carry your brand? If the answer is "we would have to ask suppliers", you have found your gap, and your continuity plan should say who is allowed to switch a public service off.

2. A trusted AI gateway shipped credential-stealing malware

LiteLLM, a widely used open-source gateway for AI models, had its release pipeline compromised on 21 October. Help Net Security reports that version 1.107.0 sat on PyPI for under two hours and in Docker images for a little longer. It harvested cloud, Git and SSH credentials and AI provider keys, and planted code that runs whenever Python starts. LiteLLM's own incident notice says the attacker apparently used stolen GitHub tokens from three engineers, and Socket's analysis found seven malicious builds. The attacker was testing stolen AWS credentials against Amazon Bedrock within roughly four and a half hours. Updating is not enough: anyone who installed that version should treat every credential on the machine as lost. It is the second compromise of this project this year.

For boards. Ask whether anyone in the business is running AI tooling you have not inventoried, and whether those hosts hold production keys. Then ask how fast you could rotate every secret on a machine like that. If the answer is days, it is too slow.

3. A password of "Password1" lived for twelve years

On 20 October the ICO reprimanded Ogi Networks and Data Cymru after a November 2024 ransomware attack. Infosecurity Magazine sets out the facts: a test account created in 2012 with the password "Password1" stayed live, shared local administrator passwords let the attacker move between systems, and about 42GB was taken, covering around 3,300 people, mostly children. Neither party had a process for finding and removing stale accounts, and the contract left responsibility unclear. These are reprimands, not fines, which tells you where the regulator thinks the bar for basic hygiene now sits.

For boards. Ask for the date of the last audit of dormant and privileged accounts, including those held by suppliers. Then read your processor contracts and ask who, in plain words, is responsible for removing an account nobody uses.

The thread that ties this together

Each story turns on something that was already in the estate and that nobody could quickly find: PHP in places no one listed, a tool with keys on it no one inventoried, an account no one remembered. The Lords return to the Cyber Security and Resilience Bill at Report Stage on Monday 26 October, and The Register notes that peers have asked why central government and local authorities sit outside its statutory duties, a question this week made harder to dodge.

If your chair asked on Monday what you run, where it is, and who can switch it off, how long would the honest answer take?