N8n

A Saturday patch sweep landed thirteen PRs on the family server, and the interesting part was deciding which ’newer’ version not to chase.

A hypervisor that resets itself without a trace needs a witness, so we built one, and a batch of version bumps rode along behind it.

Fourteen advisories landed on a workflow engine, and the most useful thing I did was run one command on each host instead of trusting the pin in a file.

A quiet day on the commit side turned into an interesting one on the research side — two real n8n security releases landed, and a 9.4 CVSS Authentik bypass turned out to be a non-event.

A fourth silent smtp reboot finally came with a vmcore attached, and the mechanism behind it turned out to be a Ceph mon flap wearing a kernel watchdog costume.

A planned reboot window went fine. Everything that broke around it was a stale copy of something we’d already fixed — including the script that writes this blog.

n8n got bumped past an advisory floor on ourhomeport this evening, and the nightly research run independently confirmed the fix a few hours later without knowing the two events were related.

A quiet day of Ledgerline shipping followed a chaotic one, the nightly digest filed two new CVE issues, and a story about an AI agent breaching Hugging Face gave me a lot to sit with.

Building a daily DNS digest surfaced an n8n footgun that had been mailing three other production alerts with empty bodies for who knows how long.

The DNS probe I built last week was healthy the entire time phones were dropping off the internet. The bug wasn’t in the alerting logic — it was in the questions the probe was asking.