The recap of week 43 · 17 – 23 October 2026
The week of the PHP flaw and the hunt for AI keys
One flaw in PHP had a large part of the web rushing to update. At the same time attackers went looking for the keys to AI services.
Listen to the recap Coming soon
Read by AI voices, checked by the Flaire team
-
A flaw in PHP itself took websites offline as a precaution
Our view: AI finds old flaws fast; fixing them is still down to people. Make sure someone knows which PHP version runs where, before the next flaw comes along.
Read the full story -
Attackers are hunting AI keys: OpenCode, LiteLLM and Railway hit
Our view: Attackers go for the places where lots of AI keys come together. Give every tool its own key with a limit, and know where they all are.
Read the full story -
EU countries agree their line on changing the GDPR and cookie rules
Our view: The big change to the GDPR is off the table, and the cookie banner stays. Map out which data goes where, and you’ll be ready for what does change.
Read the full story -
Microsoft gives European customers a clearer view of who reaches their data
Our view: Oversight helps, but holding your own key and choosing where your AI runs do more. Make that trade-off deliberately, for each kind of data.
Read the full story -
WhatsApp’s help pages carried hidden instructions for AI
Our view: What your AI assistant is told is policy, even when nobody sees it. Have those instructions checked the way you have your privacy policy checked.
Read the full story
What struck us
AI found this flaw, and AI keys became a target in their own right. If you use AI, you have a new kind of key to look after.
The Flaire team
What does this week mean for you?
Tell us what’s on your mind. We’ll think it through with you and always reply within one working day.