Go update now!
Leveraging CVE-2026-123007 for RCE requires a significant amount of network traffic to be transmitted, approximately 128 GB of HTTP/2 data.
Nevertheless, update! Or replace it with Træfik.
Or just disable http2 in the meantime. Keeping just http1.1 for legacy reasons beside http3 is perfectly okay.
That’s it. I’m switching to radio. I’m outta here. Lol
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 -von the host, plusdocker psand 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.If it’s an HTTP/2 protocol level problem and you’re using a reverse proxy, containers behind the reverse proxy probably are not affected.
deleted by creator



