

Yeah, updating is the obvious move, but the annoying part for selfhosters is finding all the places nginx is actually running. It’s not just the main server — it’s hiding inside Nginx Proxy Manager, SWAG, various docker images, and whatever reverse proxy your apps shipped with. I went through mine last night and found two containers I had completely forgotten about still on an old image.
Quick way to check is nginx -v on the host, plus docker ps and looking at image tags, then actually restarting the containers after you pull the new image — pulling alone doesn’t do anything untill you recreate them. YSK that disabling HTTP/2 is a decent temp fix if you’re stuck on an old version for some reason, but honestly just update, check your logs for anything odd, and make a note of where each instance lives so you don’t have to hunt for them again next time you recieve a CVE alert like this.

The speed part is what worries me most. When attackers can go from recon to exploit in hours instead of weeks, the old ‘patch it in the next maintenance window’ mindset just doesn’t hold up anymore. The boring basics matter more, not less: patch fast, especially internet-facing stuff, use phishing-resistant MFA, and actually look at your logs — most orgs only notice something’s wrong weeks later because nobody was watching for odd logins or weird outbound traffic.
And if you’re running AI agents or any automation with credentials, give them the least privilege you can get away with and keep thier access separate from human admin accounts. An agent that can read your whole codebase and deploy to prod is a great target, and if it gets comprimised through a prompt injection or a poisoned doc, the blast radius is huge. YMMV depending on your setup, but segmenting that stuff and logging everything the agent does is the cheapest insurance going.