Re:Pre-auth RCE in Nginx HTTP/2 handling
by hosteur on Wednesday November 18, 2026 @10:49AM
(#50547781)
So work around is to disable http/2 and only allow http/1.1?
[ Parent
| on HN ]
Re:Pre-auth RCE in Nginx HTTP/2 handling
by Simber on Wednesday November 18, 2026 @10:57AM
(#50547881)
Yep, that or update to 1.31.9+ or 1.30.7+ if they are available in your distro
Re:Pre-auth RCE in Nginx HTTP/2 handling
by kijin on Wednesday November 18, 2026 @11:39AM
(#50548462)
Nobody seems to notify major distros before publishing their latest vulnerability anymore. Coordinated patches are a thing of the past, now we just hope that somebody at Red Hat and/or Canonical is on HN today.
Re:Pre-auth RCE in Nginx HTTP/2 handling
by baggy_trough on Wednesday November 18, 2026 @12:18PM
(#50549057)
There isn't even a mail about this on oss-security, as of now.
Re:Pre-auth RCE in Nginx HTTP/2 handling
by cm2187 on Wednesday November 18, 2026 @02:01PM
(#50550555)
Unless I am confused, it doesn't look like ubuntu server has made available the fix.
Re:Pre-auth RCE in Nginx HTTP/2 handling
by dannyw on Wednesday November 18, 2026 @02:36PM
(#50551007)
It’s time to switch away from Ubuntu and go upstream to Debian.
Re:Pre-auth RCE in Nginx HTTP/2 handling
by MrDOS on Wednesday November 18, 2026 @02:39PM
(#50551045)
While I wholeheartedly agree with you, Debian hasn't patched yet, either. See my sibling comment: https://news.ycombinator.com/item?id=50551026.
Re:Pre-auth RCE in Nginx HTTP/2 handling
by karel-3d on Wednesday November 18, 2026 @05:39PM
(#50553357)
Lol no
Debian is unfixed too
[dead]
Re:Pre-auth RCE in Nginx HTTP/2 handling
by lousken on Wednesday November 18, 2026 @05:19PM
(#50553075)
https://tracker.debian.org/news/1825662/accepted-nginx-1306-...
it's been only accepted into unstable
Re:Pre-auth RCE in Nginx HTTP/2 handling
by pier25 on Wednesday November 18, 2026 @05:06PM
(#50552888)
Amazing that they don't disclose these CVEs to the major Linux distros before going public
Re:Pre-auth RCE in Nginx HTTP/2 handling
by imhoguy on Wednesday November 18, 2026 @03:23PM
(#50551633)
I wouldn't expect any distro maintainers to react in hours.
Who is sane enough in 2026 to expose distro default services to the Internet?
Start to use Docker/Podman/systemd-nspawn.. and isolate public services to necessary needs (drop capabilities, default drop rule firewall between containers, r/o storage, logs bind mounted as rw file). Container images are patched the quickest.
Re:Pre-auth RCE in Nginx HTTP/2 handling
by dboreham on Wednesday November 18, 2026 @11:06AM
(#50548005)
The AI gods say that http/2 is disabled in a default installation fwiw.
Re:Pre-auth RCE in Nginx HTTP/2 handling
by antiloper on Wednesday November 18, 2026 @11:26AM
(#50548280)
Obviously... the default configuration also doesn't enable TLS, which is a de-facto prerequisite for HTTP 2. How many websites do you (or your "AI gods") think run nginx in its default configuration?
Re:Pre-auth RCE in Nginx HTTP/2 handling
by layer8 on Wednesday November 18, 2026 @01:02PM
(#50549732)
The point is that it must have been deliberately enabled. TLS will generally be enabled out of necessity, whereas the chances for HTTP/2 are much lower, and your NGINX configuration will explicitly indicate if it’s enabled. If you don’t see “http2” in your configuration, then you know you are fine.
Re:Pre-auth RCE in Nginx HTTP/2 handling
by redox99 on Wednesday November 18, 2026 @04:50PM
(#50552671)
Yeah and park is the default gear in cars...
Re:Pre-auth RCE in Nginx HTTP/2 handling
by yread on Wednesday November 18, 2026 @12:07PM
(#50548854)
My Apaches still have http2 disabled from the last cve, now its njinx time
Re:Pre-auth RCE in Nginx HTTP/2 handling
by kijin on Wednesday November 18, 2026 @01:06PM
(#50549795)
And there were a couple of other http2 CVEs in nginx before the Apache one.
Just keep that protocol disabled for now. It's apparently too difficult for any human to write a secure implementation of http2. (As for http3, forget about it, we need AGI for that.)