Re:Pre-auth RCE in Nginx HTTP/2 handling
by brocklobsta on Wednesday November 18, 2026 @05:28PM
(#50553213)
Running a homelab is quickly turning into a bigger and bigger liability. Just disabled http/2 on my cluster.
[ Parent
| on HN ]
Re:Pre-auth RCE in Nginx HTTP/2 handling
by tripleee on Wednesday November 18, 2026 @05:36PM
(#50553311)
Isn't the point of a homelab to not expose it to the internet?
Re:Pre-auth RCE in Nginx HTTP/2 handling
by nsarrazin on Wednesday November 18, 2026 @05:37PM
(#50553324)
On the other hand I've never been so proactive about maintaining security on my homelab! I did a full audit of my self-hosted services with claude code, strengthened the isolation of all my docker services, I'm running coding agents in sandboxed microVMs now, my firewall settings are better, I set up separate VLAN for IoT, I get security notifications on my dependencies, etc. etc.
A lot of stuff that I avoided for years I finally feel like I really need to do now but it also has never been easier to do.
Re:Pre-auth RCE in Nginx HTTP/2 handling
by viccis on Wednesday November 18, 2026 @05:39PM
(#50553348)
Yeah I'm having to do attack surface review and threat modeling like I'm a full enterprise now...
Fortunately with Tailscale making it super easy to keep stuff out of the open internet, I don't have much, but even then I'm thinking of taking what I do have down. We see these big CVEs coming across, but I guarantee there's a large number of 0 days sitting around in peoples' stashes all over the world that we don't see.
Re:Pre-auth RCE in Nginx HTTP/2 handling
by throooooo on Wednesday November 18, 2026 @05:39PM
(#50553351)
The only port I expose is Wireguard.
Re:Pre-auth RCE in Nginx HTTP/2 handling
by prism56 on Wednesday November 18, 2026 @06:38PM
(#50553915)
Annoyingly I've switched to strict IP address whitelists for anyone I share services with. Slight hassle but massively reduced the attack service.
My box got hammered daily with port scans etc before.