News for hackers. Stuff that matters.
Re:Pre-auth RCE in Nginx HTTP/2 handling by artooro on Wednesday November 18, 2026 @03:32PM (#50551749)
Thankfully this time there are patches available right away, unlike that PHP bug not too long ago!
Re:Pre-auth RCE in Nginx HTTP/2 handling by Aachen on Wednesday November 18, 2026 @06:12PM (#50553691)
Quite the opposite, it looks like there has been no responsible disclosure here. No update available for anyone running something based on Debian (Ubuntu etc.), only if you go and fetch binaries from the source and do the system integration yourself (easy in this case, but in general that's the point of a distro). For php I could just update at some point that day

Otoh I'm not sure what http2 is good for (I've asked around today, some people said the multiplexing speeds things up on high-latency connections. I'm still working on a realistic benchmark since I couldn't find any but it's not looking great so far) and it's default disabled so comparatively few sites are affected. Getting rid of it is easier than waiting who knows how long for it to get packaged

Re:Pre-auth RCE in Nginx HTTP/2 handling by Jon_Lowtek on Wednesday November 18, 2026 @08:23PM (#50554877)
HTTP1.1 has a fundamental flaw related to request smuggling. Fixing specific variants of that problem is a game of whack a mole, as issues arise most often from larger server composition, not individual parts. Fixing the protocol flaw requires a major version increment and a phase out of the old one. Today the hesitation to do that gives us a mitigation option, but in general an http downgrade is a bad thing.

There are also features on top of http2 that a downgrade may break: gRPC and Server Side Events for example. The later is compatible with HTTP1.1, but could fail due to connection limits, as multiplexing isn't only about speed. Some web apps may handle that so gracefully, it turns into a performance thing again, but others could halt and catch fire.