News for hackers. Stuff that matters.
Re:Pre-auth RCE in Nginx HTTP/2 handling by SubiculumCode on Wednesday November 18, 2026 @12:16PM (#50549025)
How bad are these CVEs? Could any of these be related to some of the recent outages (not claiming, asking) in the last week, coinciding with when this bug was fixed in the repo? Monitoring such repos seems a given for nation states.
Re:Pre-auth RCE in Nginx HTTP/2 handling by ryanisnan on Wednesday November 18, 2026 @12:25PM (#50549168)
RCE is about at the top of the stack for severity.
Re:Pre-auth RCE in Nginx HTTP/2 handling by ArcHound on Wednesday November 18, 2026 @12:30PM (#50549252)
While that is true, you should also account for exploitability. These exploits are demonstrated in lab environments which are simple and controlled. Random legit traffic will interfere with the exploit logic, so these are very hard to get in practice. Not impossible, but it's also not immediately broken.
Re:Pre-auth RCE in Nginx HTTP/2 handling by PcChip on Wednesday November 18, 2026 @12:51PM (#50549581)
put up some bitcoin behind an nginx server and tell hackernews to steal it, see how long it takes
Re:Pre-auth RCE in Nginx HTTP/2 handling by wildmXranat on Wednesday November 18, 2026 @02:48PM (#50551168)
:) If the battering ram is 128gb big, it'll be a long time unless someone has reversed those changes in Nginx to get at the exploit. After that, yeah, it's no contest
Re:Pre-auth RCE in Nginx HTTP/2 handling by ryanisnan on Wednesday November 18, 2026 @01:13PM (#50549884)
Great context. Thank you for the add.
Re:Pre-auth RCE in Nginx HTTP/2 handling by pocksuppet on Wednesday November 18, 2026 @02:02PM (#50550565)
This was also true with php2shell but AI got there in the end.
Re:Pre-auth RCE in Nginx HTTP/2 handling by smallerize on Wednesday November 18, 2026 @02:31PM (#50550927)
According to https://www.rapid7.com/blog/post/ve-cve-2026-123007-critical... it requires 128GB to be transferred in a single connection. "a network slower than approximately 300 Mbit/s will take over the one hour connection limit threshold and will not be able to succeed"
Re:Pre-auth RCE in Nginx HTTP/2 handling by mountainro53 on Wednesday November 18, 2026 @03:51PM (#50551959)
Not all of the bugs disclosed today in nginx require that much traffic to trigger, the reverse proxy HTTP/2 bug found by Xint needs just KBs of traffic.
Re:Pre-auth RCE in Nginx HTTP/2 handling by Gigachad on Wednesday November 18, 2026 @08:17PM (#50554802)
Thankfully most of these bugs coming out seem very difficult to exploit (likely why they took so long to find). They usually become dangerous when you can build an entire chain of bugs to exploit.

But doing that requires collecting the whole chain. In the current environment we might be finding and patching these smaller bugs before they can be put in to a chain. As long as you are keeping on top of updates..

Re:Pre-auth RCE in Nginx HTTP/2 handling by lanstin on Wednesday November 18, 2026 @01:17PM (#50549942)
And nginx is so widely used many people will be running it and not really know that. It’s ubiquitous reliable invisible infra for many issues. Like preventing the internet from getting to your RCE riddled application servers, terminating SSL, free software LB, etc. if you have cloud native from the beginning you might not know where AWS uses it but otherwise you have it. Cloud flare I think uses a Rust rewrite.