Like any blog post at New Year’s, we’ll be looking to the future. We’ll also check our assumptions and we’ve got some security content before looking at a website to destroy all websites. I did like this piece on The Register which looks at four potentially game changing technologies without mentioning AI. The oxygen of publicity this year has mostly been consumed by our two-lettered friend, AI. There’s no reason to think this will change in 2026.

To those who celebrate the festivals either end of the last 7 days of the year: Happy <insert here>! This time round, there’s not one, but two bleeding fails in security, some interesting protections, how slowing down is not only speeding up, but also making things more enjoyable. So without further ado, and much less waffle, let’s jump right in: GPG fail Our first fail is from the 39th Chaos Computer Congress gathering, which provided a rather bountiful set of vulnerabilities and weaknesses around GPG - the GNU Privacy Guard to give it its full title.

This week we’re looking through a mix of security and AI once more. Because tech is nothing but those two topics, right? Right? Anyway, I am often travelling on the train or stay in hotels these days, I find myself working on public wifis. Of course, one look on LinkedIn will immediately warn you of the dangers of public wifi. Seemingly, as soon as you connect a hacker will automatically steal your credit cards.

Let’s start this week with many happy returns for Let’s Encrypt! It’s been 10 years since free TLS certificates made it much more common that things go via HTTPS rather than HTTP. When anyone and everyone was able get a cert, it certainly reduced the barriers to adoption. These days it is almost unimaginable to have some web traffic that doesn’t use TLS. Now, if only we could convince some “security experts” to stop going on about how connecting to a public wifi will allow h4x0rs to steal all your data.

This week, we’re talking about React4shell. The latest in the 4shell family of vulnerabilities. What does 4shell mean? Usually that it’s possible to do RCE (Remote Code Execution) based on an application vulnerability and typically, attackers will leverage that to get a remote shell. And now, for something completely different My first link is not related to react4shell, but it’s yet another way of how guardrails in LLM models can be subverted.

This week is an odd mixture about sandworms, supply chains and basically how everything is broken anyway. And then (after all the naughtiness) let’s end on something nice. Thumped by a Sandworm Sha1 Hulud came back for another go at supply chain attacks. Patient zero of this wave appears to have been Posthog - an analytics platform a bit like Mixpanel. According to their postmortem, their build pipeline was compromised by a simple pull request.