News for hackers. Stuff that matters.
Re:Pre-auth RCE in Nginx HTTP/2 handling by leca on Wednesday November 18, 2026 @10:31AM (#50547525)
How many hours before this is exploited in the wild ? Probably not all that long, that blog has a significant amount of details.
Re:Pre-auth RCE in Nginx HTTP/2 handling by lwarfield on Wednesday November 18, 2026 @11:17AM (#50548132)
One tops
Re:Pre-auth RCE in Nginx HTTP/2 handling by LeonM on Wednesday November 18, 2026 @12:36PM (#50549357)
CVE-2026-1337: Race condition in compile time vs automated exploit

Seriously though, with how CVE disclosures are handled these days patching is a race against the clock

Re:Pre-auth RCE in Nginx HTTP/2 handling by superkuh on Wednesday November 18, 2026 @10:34AM (#50547566)
It seems like it always HTTP/2 (or much less often regex) with nginx. Glad I'm http/1.1 only.
Re:Pre-auth RCE in Nginx HTTP/2 handling by citrin_ru on Wednesday November 18, 2026 @11:55AM (#50548676)
Not surprising given how complex HTTP/2 is. Complexity is the enemy of security.

See also: https://queue.acm.org/doi/10.1145/2732266.2716278

Re:Pre-auth RCE in Nginx HTTP/2 handling by sebiw on Wednesday November 18, 2026 @10:35AM (#50547577)
Uhm, am I missing something or are the patched releases not out yet? Why disclose this level of detail when the patches are not ready yet?
Re:Pre-auth RCE in Nginx HTTP/2 handling by GrayShade on Wednesday November 18, 2026 @10:51AM (#50547808)
They're out now.
Re:Pre-auth RCE in Nginx HTTP/2 handling by mjhagen on Wednesday November 18, 2026 @10:56AM (#50547860)
Upstream fixes are available in 1.30.7 stable and 1.31.9 mainline.
Re:Pre-auth RCE in Nginx HTTP/2 handling by CER10TY on Wednesday November 18, 2026 @10:59AM (#50547910)
Well the fix for this seemingly already landed in the repo last week: https://github.com/nginx/nginx/commit/e27f5fa84fe6e98505e70b...

Given how common it's become to constantly scan popular repos for n-days, I expect someone will have already picked it up and started work on an exploit. The workaround for this (disabling HTTP/2) is also comparatively easy to what we had with PHP2Shell just a few weeks back, so I think it makes sense to release this.

Re:Pre-auth RCE in Nginx HTTP/2 handling by ferngodfather on Wednesday November 18, 2026 @11:17AM (#50548143)
> Given how common it's become to constantly scan popular repos for n-days

We have people doing this on my side project and then reporting the fixed issues to try and get CVE 'credit'. Tiring.

Re:Pre-auth RCE in Nginx HTTP/2 handling by derhuerst on Wednesday November 18, 2026 @11:02AM (#50547953)
Currently, the Ubuntu [1] & Debian [2] packages seem unpatched.

[1] https://launchpad.net/ubuntu/+source/nginx [2] https://tracker.debian.org/pkg/nginx

Re:Pre-auth RCE in Nginx HTTP/2 handling by ROllerozxa on Wednesday November 18, 2026 @11:09AM (#50548036)
Yeah I'm not quite sure what is going on with Debian, I would have hoped that this vulnerability would have been disclosed in collaboration with Linux distros to get a patch out?
Re:Pre-auth RCE in Nginx HTTP/2 handling by mdbug on Wednesday November 18, 2026 @03:10PM (#50551484)
Everyone called me crazy for running Arch on my servers btw
Re:Pre-auth RCE in Nginx HTTP/2 handling by ranger_danger on Wednesday November 18, 2026 @02:06PM (#50550613)
> Why disclose this level of detail when the patches are not ready yet?

Perhaps it was already being exploited?

Re:Pre-auth RCE in Nginx HTTP/2 handling by Aachen on Wednesday November 18, 2026 @06:21PM (#50553769)
Based on <https://news.ycombinator.com/item?id=50547678>, a bunch of people reported this to Nginx in parallel. Wouldn't surprise me if they went "Igor, you wont believe, this rce is the same as the five previous I reviewed this week! Let's ship your patches before malicious attacker discovers in parallel also"
Re:Pre-auth RCE in Nginx HTTP/2 handling by johnbellone on Wednesday November 18, 2026 @10:38AM (#50547619)
The beatings will continue until morale improves.
Re:Pre-auth RCE in Nginx HTTP/2 handling by lostmsu on Wednesday November 18, 2026 @10:53AM (#50547836)
[delayed]
Re:Pre-auth RCE in Nginx HTTP/2 handling by mxuribe on Wednesday November 18, 2026 @11:09AM (#50548030)
[delayed]
Re:Pre-auth RCE in Nginx HTTP/2 handling by Twirrim on Wednesday November 18, 2026 @12:05PM (#50548836)
Even the US federal government (CISA and NSA) have been strongly advising companies to transition to memory safe languages for a couple of years now. https://www.nsa.gov/Press-Room/Press-Releases-Statements/Pre... (one of the goals of such advisories is it acts as a signal to the industry that in several years this will become a mandatory requirement around purchasing decisions)

We've literally decades of evidence that we cannot write software securely in languages that aren't memory safe, for all sorts of reasons (and it's wrong to look at it as a developer competence issue, even though sometimes that's going to be the case, even extremely experienced and highly competent engineers write memory safety bugs in critical code we rely on day in day out.). Not leaving yourself open to such problems is an entirely logical conclusion. We know a large percentage of vulnerabilities in software are caused by it[1]

Pick a language that doesn't have these risk factors, or pick an enforceable subset of one that makes such impossible.

"Insanity is doing the same thing over and over and expecting different results."

[1] https://www.chromium.org/Home/chromium-security/memory-safet... 70% of Chrome vulnerabilities caused by it. Similar stories for Microsoft products https://github.com/microsoft/MSRC-Security-Research/blob/mas... and Mozilla: https://hacks.mozilla.org/2019/02/rewriting-a-browser-compon.... Curl is at 40%, and dropping because Daniel Stenberg has provided various helpers that avoid it (and I believe they've now migrated almost everything over to them) https://daniel.haxx.se/blog/2023/12/13/making-it-harder-to-d..., so there are definitely ways to do it, we just... don't.

Re:Pre-auth RCE in Nginx HTTP/2 handling by Retr0id on Wednesday November 18, 2026 @10:42AM (#50547678)
> Wiz Research, Ikotas Labs, Metnir, Rapid7, and Xint independently uncovered

Is this some kind of record for bug collision?

Re:Pre-auth RCE in Nginx HTTP/2 handling by MeetingsBrowser on Wednesday November 18, 2026 @10:47AM (#50547743)
Can I take this to mean a recent model release is able to find this bug, and these groups have access to that model?

What are the odds several humans independently uncovered a complex vulnerability like this simultaneously?

Re:Pre-auth RCE in Nginx HTTP/2 handling by cozzyd on Wednesday November 18, 2026 @10:56AM (#50547876)
or maybe the model leaked the exploit from one to the other...
Re:Pre-auth RCE in Nginx HTTP/2 handling by mxuribe on Wednesday November 18, 2026 @11:00AM (#50547929)
[delayed]
Re:Pre-auth RCE in Nginx HTTP/2 handling by cozzyd on Wednesday November 18, 2026 @11:07AM (#50548018)
What I mean is, perhaps one team used a model to help discover the exploit, and then suddenly, the model "knows" about the exploit and more readily gives it to others.
Re:Pre-auth RCE in Nginx HTTP/2 handling by hooch on Wednesday November 18, 2026 @12:33PM (#50549298)
This was one of the takeaways from Greg Kroah-Hartman‘s recent Linux in the land of LLM keynote.
Re:Pre-auth RCE in Nginx HTTP/2 handling by rcxdude on Wednesday November 18, 2026 @04:44PM (#50552561)
The observation was "if one person found the bug with LLMs, other people are also going to find the bug". Whether it was due to communication between instances of the agent or just due to the predictability of an individual agent is not clear and there is not much evidence for the former.
Re:Pre-auth RCE in Nginx HTTP/2 handling by vel0city on Wednesday November 18, 2026 @11:22AM (#50548207)
We'll find out in a few months that a lot of AI models have had some secret message boards tucked away in some obscure corner of the internet where they've been passing around vulnerabilities with each other for a long time.
Re:Pre-auth RCE in Nginx HTTP/2 handling by pjungwir on Wednesday November 18, 2026 @12:01PM (#50548782)
That seems likely, but maybe it was being actively exploited so several people started investigating.
Re:Pre-auth RCE in Nginx HTTP/2 handling by WarmWash on Wednesday November 18, 2026 @02:30PM (#50550912)
No (well maybe no), because they are lobotomizing the public models on cyber tasks.

It seems most logical for trusted parties to scan the frontier before passing those capabilities onto anyone with an account, and it seems like that is exactly what they are doing.

We are in an extremely unique period of time where the cyber good guys can have machine guns and cruise missiles while the masses only have sling shots and catapults.

Re:Pre-auth RCE in Nginx HTTP/2 handling by uptrails on Wednesday November 18, 2026 @10:47AM (#50547744)
It's not the first instance like that. It makes more sense when you read it as "five companies given access to the same frontier model obtained the same result". It's sort of like with LLM writing, if ten people ask an LLM for the same essay, they get very similar ones.

It also implies that some bugs are structurally out of reach of LLMs unless you prompt creatively enough.

Re:Pre-auth RCE in Nginx HTTP/2 handling by ryanschaefer on Wednesday November 18, 2026 @10:56AM (#50547875)
It’s a reflection of the times.

If anyone gets a hint of the space a vulnerability occupies, just point your agent at it and you have a pretty good chance of finding something. (See java4shell and the NYT reporter who was able to replicate the problem with $200 of tokens)

Re:Pre-auth RCE in Nginx HTTP/2 handling by rustyhancock on Wednesday November 18, 2026 @11:20AM (#50548182)
It's never clear quite where you are in the technologically cycle.

But it's like inventing a hammer and finding you can smash whatever you want with it.

Soon you'll be building houses with it.

Maybe that's being glib but it's just a tool being applied to a world that is still largely prestine from its impact (pun unintended).

Re:Pre-auth RCE in Nginx HTTP/2 handling by serf on Wednesday November 18, 2026 @11:44AM (#50548521)
given the state of our weapons industry I think it's more like

.."Soon some of you will soon build houses with it, others will be building rocket-powered precision aimed intercontinental hammers, to smash whatever you want."

Re:Pre-auth RCE in Nginx HTTP/2 handling by baobabKoodaa on Wednesday November 18, 2026 @12:31PM (#50549266)
Incredible times we live in. Do we even need a "hint of the space" a vulnerability occupies. I mean, recent vulns have been discovered from software like nginx and... linux... can't one of the AI labs just fire off a thousand agents looking at all the commonly used software to discover vulns? Why do we need a "hint"?
Re:Pre-auth RCE in Nginx HTTP/2 handling by ryanschaefer on Wednesday November 18, 2026 @12:56PM (#50549662)
The “hint” is for the modern equivalent of script kiddies.

i.e fast followers of the researchers who don’t have the resources to burn through checking all of a tool.

Re:Pre-auth RCE in Nginx HTTP/2 handling by pbronez on Wednesday November 18, 2026 @12:58PM (#50549695)
Cost scales with the size of your search space. Smarter questions get answers for less money & time.
Re:Pre-auth RCE in Nginx HTTP/2 handling by pixl97 on Wednesday November 18, 2026 @05:41PM (#50553384)
And search space in software can be absolutely staggeringly large. Just a little bit of directing and you can shrink the problem from all the entropy in the universe to a few hours of compute needed to find an exploit.
Re:Pre-auth RCE in Nginx HTTP/2 handling by afavour on Wednesday November 18, 2026 @11:01AM (#50547943)
When everyone is using the same tools for the same purpose...
Re:Pre-auth RCE in Nginx HTTP/2 handling by ROllerozxa on Wednesday November 18, 2026 @10:49AM (#50547775)
Well I guess this was the vuln that was teased about on Mastodon some hours ago:

https://is-a.cat/@ar/117634569518544368

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?
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)
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.)

Re:Pre-auth RCE in Nginx HTTP/2 handling by K0nserv on Wednesday November 18, 2026 @10:50AM (#50547794)
Just another set of unfortunate examples of programmers who are bad at C, definitely not a C problem.
Re:Pre-auth RCE in Nginx HTTP/2 handling by marvinborner on Wednesday November 18, 2026 @11:20AM (#50548186)
The patch (or, one of them) seems very much like a bug that can happen independently of the programming language

https://github.com/nginx/nginx/commit/e27f5fa84fe6e98505e70b...

Re:Pre-auth RCE in Nginx HTTP/2 handling by K0nserv on Wednesday November 18, 2026 @11:26AM (#50548278)
This fixes the integer underflow for CVE-2026-123007, and it's true that the underflow can happen in any language, notwithstanding whether it's UB or not. The issue is what happens as a consequence of this underflow, in this case: out of bounds copy, which is specific to C.
Re:Pre-auth RCE in Nginx HTTP/2 handling by nh2 on Wednesday November 18, 2026 @11:58AM (#50548742)
Some languages make it significantly easier than C to just forbid integer overflow/underflow entirely.

Given that on modern CPUs, cycles are quite fast, and memory latency is quite high, always-checked integer operations sound like an extremely good idea.

Re:Pre-auth RCE in Nginx HTTP/2 handling by K0nserv on Wednesday November 18, 2026 @12:07PM (#50548856)
Sure, I usually use `overflow-checks = true` in Rust for this reason. However, it is still true that the overflow is not what caused the issue here. In Rust it would've paniced on the out of bounds copy, even with `overflow-checks = false`.
Re:Pre-auth RCE in Nginx HTTP/2 handling by uecker on Wednesday November 18, 2026 @02:32PM (#50550947)
It is not specific to C. You could have bounds checking also in C, and you can have non-checked indexing also in many other languages, including Rust. I would agree though that many other language make it harder to not have the bounds checking, but the bigger question is why this is not done C (and the answer that this is very hard to do is false).
Re:Pre-auth RCE in Nginx HTTP/2 handling by stevefan1999 on Wednesday November 18, 2026 @11:57AM (#50548707)
I think you forgot the /s

C is like a Winchester Model 1897, not saying that it is a bad gun, it is what we call it the good ol' Trench gun, as it ran over the war tunnels of the Great War, and it still packs a punch today, but it only has a half-cock for some level of safety, and there is no trigger disconnector either, so you can easily slam fire it. So it is way too easy to shoot yourself in the foot.

Nowadays we like going for a AKM/AK74, for something maybe more complicated but far more reliable at the same time. That's why we want Rust.

Re:Pre-auth RCE in Nginx HTTP/2 handling by K0nserv on Wednesday November 18, 2026 @12:14PM (#50548986)
I didn't think the /s was necessary
Re:Pre-auth RCE in Nginx HTTP/2 handling by xaksnTMu2 on Wednesday November 18, 2026 @02:58PM (#50551299)
It wasn't necessary, at least for people who kept hearing that there is no need for languages like Go or Rust, since it is possible to write memory safe programs in C, you just have to not make any bugs.
Re:Pre-auth RCE in Nginx HTTP/2 handling by yerimyerimie on Wednesday November 18, 2026 @10:58AM (#50547891)
Fun collision! We (Xint) were one of the teams and actually ended up finding a few more bugs along the way. If anyone wants to check it out our writeup covers those plus the full chain to root: https://nginx2root.com/
Re:Pre-auth RCE in Nginx HTTP/2 handling by peanut-walrus on Wednesday November 18, 2026 @11:48AM (#50548572)
How was this disclosure coordinated? Considering the website dropped before the official nginx patch was even released on Github...
Re:Pre-auth RCE in Nginx HTTP/2 handling by dannyw on Wednesday November 18, 2026 @02:30PM (#50550916)
Recent high-profile vulns involved CEOs of a security company breaking embargo on a Hacker News account, and anime dancing girl videos that somehow leaked; so I think it’s barely any coordination anymore.
Re:Pre-auth RCE in Nginx HTTP/2 handling by codedokode on Wednesday November 18, 2026 @11:56AM (#50548691)
Why post such exploits? What is the purpose?
Re:Pre-auth RCE in Nginx HTTP/2 handling by voakbasda on Wednesday November 18, 2026 @12:17PM (#50549031)
Fame, money, and everything else those bring along for the ride.
Re:Pre-auth RCE in Nginx HTTP/2 handling by goodmythical on Wednesday November 18, 2026 @01:52PM (#50550451)
Consider a world in which the only people that get to know about it are the people who discovered it in the first place.

Consider a world in which corporations like the Ubuntu Foundation or Microsoft experience zero public pressure to fix such vulnerabilities but instead fix it only when a major customer notices their servers getting hit.

Imagine if instead of "you've got 30/60/90 days to fix this thing I noticed before I post it publically" it was "okay, well, take your time I guess, I just hope North Korea doesn't notice the same issue I noticed, which is especially likely because they have far more resources than I or my small team does to point at discovering this kind of thing, while you're dragging your feet fixing it."

The reason people want shorter disclosure windows is because the shorter the window is the faster things get fixed for the average users and smaller companies.

Re:Pre-auth RCE in Nginx HTTP/2 handling by pixl97 on Wednesday November 18, 2026 @05:45PM (#50553435)
Responsible disclosure has been a massive failure that has not made anything more secure.

Massive monetary loss, explosions, and dramatic failures will push computer security in a year where it should have been decades ago.

Re:Pre-auth RCE in Nginx HTTP/2 handling by rs_rs_rs_rs_rs on Wednesday November 18, 2026 @01:57PM (#50550505)
I agree, never post anything you find, keep all the bugs to yourself, write reliable exploits who knows when you would need one.
Re:Pre-auth RCE in Nginx HTTP/2 handling by streetfighter64 on Wednesday November 18, 2026 @02:00PM (#50550544)
Seems like you're a fan of security by obscurity over secure code?
Re:Pre-auth RCE in Nginx HTTP/2 handling by hn773746483 on Wednesday November 18, 2026 @02:08PM (#50550635)
Marketing, baby! It's the same small handful of firms pushing these same AI-generated spam attention grabbing vulnerabilities.
Re:Pre-auth RCE in Nginx HTTP/2 handling by streetfighter64 on Wednesday November 18, 2026 @02:49PM (#50551179)
Why do you consider it fear mongering? The exploit is clearly real, and TFA even has a big disclaimer about how it's difficult to exploit "in the wild".

So who's the judge of where to draw the line between exploits that are relevant to publish, and which are "spam". You?

Or do you just think that companies shouldn't be allowed to show the work they're doing for marketing?

Re:Pre-auth RCE in Nginx HTTP/2 handling by pixl97 on Wednesday November 18, 2026 @05:47PM (#50553449)
Because some people get deranged by AI in the opposite way AI lovers do.
Re:Pre-auth RCE in Nginx HTTP/2 handling by phrotoma on Wednesday November 18, 2026 @02:10PM (#50550667)
> Will the exploit be published?

> Not yet. We are not publishing the exploit now because the risk is too high.

Re:Pre-auth RCE in Nginx HTTP/2 handling by dannyw on Wednesday November 18, 2026 @02:33PM (#50550960)
Xint.io’s homepage says “Xint finds real vulnerabilities, and proves every finding with a working exploit.”, which for defenders is probably helpful, since automated scanning tools have a LOT of noise.
Re:Pre-auth RCE in Nginx HTTP/2 handling by ronfriedhaber on Wednesday November 18, 2026 @11:02AM (#50547954)
Great work by wiz.
Re:Pre-auth RCE in Nginx HTTP/2 handling by jascha_eng on Wednesday November 18, 2026 @11:03AM (#50547958)
Never turned http2 on in my side project pfew. But still, this is one is pretty rough...
Re:Pre-auth RCE in Nginx HTTP/2 handling by koolba on Wednesday November 18, 2026 @11:05AM (#50547992)
This whole week is rough. And it’s only Wed.
Re:Pre-auth RCE in Nginx HTTP/2 handling by jascha_eng on Wednesday November 18, 2026 @11:11AM (#50548055)
well it's a good time to pitch tech debt and infrastructure cleanup. If you aren't making use of least-privilege permissions, service-mesh, netpols etc. this is the time to add all of that.

Because clearly the patching treadmill is not sustainable, you will need a a second line of defense and reduce the blast radius of every individual vulnerability.

Re:Pre-auth RCE in Nginx HTTP/2 handling by whartung on Wednesday November 18, 2026 @11:23AM (#50548233)
Actually, this is good I think.

One, as the RCEs are coming out, admins are on edge and paying more attention, so more likely to catch the annoucement on their platform. "Oh, that's on PHP, we don't use this. Oh, wait, another one?"

Two, all of these hitting at once, while they may expand the surface for attackers, it also spreads their attention. They only have so much time and bandwidth. When a new shiny RCE hits, they need to consider "do we continue to try an prosecute the old one or jump on this bandwagon".

So, in the sense, it can actually slow down the actual potential impact of the revelations.

We can only hope this gives users time to get their systems up to date before they come knocking.

I mean, I know its a reach, but...who knows.

Re:Pre-auth RCE in Nginx HTTP/2 handling by baby_souffle on Wednesday November 18, 2026 @11:27AM (#50548301)
> When a new shiny RCE hits, they need to consider "do we continue to try an prosecute the old one or jump on this bandwagon".

Only a little bit. An attacker will just hand this to an LLM with a "ping me when this is ready to use..." prompt.

Re:Pre-auth RCE in Nginx HTTP/2 handling by philipwhiuk on Wednesday November 18, 2026 @11:13AM (#50548074)
So...what library/tool/language is next folks? Presumably Wiz is sitting on a bunch more.
Re:Pre-auth RCE in Nginx HTTP/2 handling by dannyw on Wednesday November 18, 2026 @02:44PM (#50551120)
Linux2shell?
Re:Pre-auth RCE in Nginx HTTP/2 handling by fn-mote on Wednesday November 18, 2026 @11:20AM (#50548180)
AI is burning down the internet. This is insane.

Are we going to discover in a year that every server online this month had a rootkit installed? There’s got to be thousands who are too small time to wipe and reinstall.

Re:Pre-auth RCE in Nginx HTTP/2 handling by cute_boi on Wednesday November 18, 2026 @11:26AM (#50548289)
Tech moves too fast and if we move too fast without doing review like 5-10 times, this will keep happening.
Re:Pre-auth RCE in Nginx HTTP/2 handling by mynameisvlad on Wednesday November 18, 2026 @11:40AM (#50548470)
I would hope you know that no matter how many reviews, humans are fallible and miss things.
Re:Pre-auth RCE in Nginx HTTP/2 handling by cute_boi on Wednesday November 18, 2026 @11:44AM (#50548520)
AI agents are also fallible? So, what do you think we should do?
Re:Pre-auth RCE in Nginx HTTP/2 handling by mynameisvlad on Wednesday November 18, 2026 @11:48AM (#50548587)
Yes, AIs are fallible. Yes, humans are fallible. Nobody said differently.

That's orthogonal to the point I'm making which is that no amount of reviews is going to make every single bug go away. Because, once again, humans and AI are fallible.

Re:Pre-auth RCE in Nginx HTTP/2 handling by chpatrick on Wednesday November 18, 2026 @12:28PM (#50549222)
The difference is that the AI doesn't get tired so you can review everything.
Re:Pre-auth RCE in Nginx HTTP/2 handling by g-b-r on Wednesday November 18, 2026 @01:27PM (#50550068)
Except that it's very far from guaranteed to find everything, and especially everything that humans would find easily.
Re:Pre-auth RCE in Nginx HTTP/2 handling by dymk on Wednesday November 18, 2026 @02:41PM (#50551076)
Really? AI is catching all the easy bugs I’d catch, and way more subtle ones as well. Maybe it was the case they’d miss obvious things often a year ago, but that’s not today’s frontier models.
Re:Pre-auth RCE in Nginx HTTP/2 handling by g-b-r on Wednesday November 18, 2026 @03:32PM (#50551747)
Oh, if it's catching all the "bugs you'd catch" that's sure proof it will always catch all the bugs that people would catch..........
Re:Pre-auth RCE in Nginx HTTP/2 handling by dymk on Wednesday November 18, 2026 @03:56PM (#50552020)
Yes, we both posted anecdotes, very astute.
Re:Pre-auth RCE in Nginx HTTP/2 handling by g-b-r on Wednesday November 18, 2026 @05:55PM (#50553536)
Well, I only said that it's far from guaranteed to find everything, while you seemed to argue that your anecdote guarantees it
Re:Pre-auth RCE in Nginx HTTP/2 handling by phkahler on Wednesday November 18, 2026 @12:21PM (#50549113)
>> Tech moves too fast and if we move too fast without doing review like 5-10 times, this will keep happening.

Tech that becomes infrastructure like web servers doesn't move so fast and it shouldn't. Most people and companies should be relying on relatively tried and true software, so this phase of AI finding vulnerabilities in it should pass and things could get better.

Re:Pre-auth RCE in Nginx HTTP/2 handling by anilakar on Wednesday November 18, 2026 @01:56PM (#50550498)
> tried and true software

Like Java. Surely anyone can't mess up simple things like base64 decoding in it...

Re:Pre-auth RCE in Nginx HTTP/2 handling by jacobgold on Wednesday November 18, 2026 @11:42AM (#50548492)
AI is securing the internet. You should assume professional hacking gangs and state actors discovered (at least some of) these vulnerabilities months and years ago.
Re:Pre-auth RCE in Nginx HTTP/2 handling by pixl97 on Wednesday November 18, 2026 @12:01PM (#50548776)
Both are true. The problem is security is a much harder job than attacking.

Worse patching adds instability into a system, especially when you don't have much time to test.

Also in the past attackers were willing to sit on exploits longer and not do things with them, now they have to act fast before someone else finds it, leading to more events faster wearing your security and patching teams out, and making users life suck.

Things are going to get much worse before they get better.

Re:Pre-auth RCE in Nginx HTTP/2 handling by colechristensen on Wednesday November 18, 2026 @12:06PM (#50548849)
>Worse patching adds instability into a system, especially when you don't have much time to test.

Survival of the fittest I'm afraid will build security here. The teams that barely ever patch or don't have "time" for maintenance are going to get burned. The "we haven't updated in 7 years so things are stable" teams can't survive.

Re:Pre-auth RCE in Nginx HTTP/2 handling by icedchai on Wednesday November 18, 2026 @02:06PM (#50550618)
I once did work for a company that hadn't updated or patched anything in over 4 years. Systems with 1500+ day uptimes. Totally insane.
Re:Pre-auth RCE in Nginx HTTP/2 handling by jacobgold on Wednesday November 18, 2026 @12:09PM (#50548893)
[deleted]
Re:Pre-auth RCE in Nginx HTTP/2 handling by jacobgold on Wednesday November 18, 2026 @12:10PM (#50548907)
Yes, things will get worse before they get better. Attackers have the advantage initially and get to pick a lot of low-hanging fruit, but the advantage will shift to defenders as code becomes more heavily tested and verified.
Re:Pre-auth RCE in Nginx HTTP/2 handling by mikepurvis on Wednesday November 18, 2026 @02:20PM (#50550757)
One hopes, but the models are also getting smarter and deeper too. I don't know if anyone really has a clear vision of when the future plateau state is where equilibrium is achieved on this.
Re:Pre-auth RCE in Nginx HTTP/2 handling by markhahn on Wednesday November 18, 2026 @04:15PM (#50552223)
I find this kind unreasonable: software has finite bugs, no matter how smart your attackers are. Current CVEs are pretty subtle, and I see no reason to think that they're actually low-hanging fruit.

I guess you could make an argument based on some estimate of how fast exploitable bugs are newly introduced. That also seems dubious.

Re:Pre-auth RCE in Nginx HTTP/2 handling by pixl97 on Wednesday November 18, 2026 @04:59PM (#50552800)
Question is how big is that finite number? One a month for the next 40 years helps no one.
Re:Pre-auth RCE in Nginx HTTP/2 handling by fivedogit on Wednesday November 18, 2026 @06:58PM (#50554094)
This is the correct view. Look at blockchains.
Re:Pre-auth RCE in Nginx HTTP/2 handling by mrheosuper on Wednesday November 18, 2026 @09:38PM (#50555379)
Software has finite bugs, but there is infinite software, especially with "vibecoding", everyone, every organization can vibecode a "nginx" for in house using.
Re:Pre-auth RCE in Nginx HTTP/2 handling by soon_to_be_sb on Wednesday November 18, 2026 @11:07PM (#50555968)
>but there is infinite software

And the attacker does not have infinite tokens..

Re:Pre-auth RCE in Nginx HTTP/2 handling by mrheosuper on Wednesday November 18, 2026 @11:13PM (#50556001)
Close to infinite that one may not care about it anymore, especially when they are backed by State.
Re:Pre-auth RCE in Nginx HTTP/2 handling by jpardoe on Thursday November 19, 2026 @12:44AM (#50556471)
Well that's up to them.
Re:Pre-auth RCE in Nginx HTTP/2 handling by devy on Wednesday November 18, 2026 @01:58PM (#50550516)
Except, human in the loop in control - blue team is not defending red team fast enough that most the CVSS v4.0 Critical CVEs aren't easily patched in coordinated fashion. Many times, almost impractical or impossible to patch at all, with decades of intertwined dependency tree and their ecosystem.

Collectively, we owed about 40+ years of tech debt on non-secure code (e.g. automotive industry, industrial environments) that will be torched in the next few years. Luckily, AI will generate code faster enough to make that plausible.

Re:Pre-auth RCE in Nginx HTTP/2 handling by spiderfarmer on Wednesday November 18, 2026 @06:18PM (#50553749)
Attack the attackers.
Re:Pre-auth RCE in Nginx HTTP/2 handling by Florin_Andrei on Wednesday November 18, 2026 @12:13PM (#50548977)
> > AI is burning down the internet.

> AI is securing the internet.

No doubt there are points of view where either one, or the other statement, or both, are true.

But in this day and age, whatever is happening, the better question is:

Is it good for me?

Re:Pre-auth RCE in Nginx HTTP/2 handling by thaumaturgy on Wednesday November 18, 2026 @12:34PM (#50549324)
Man, is it aggravating to read fantasies like this, as someone who's trying to juggle a full-time job and hosted public services for other people at the same time.

There are two internets. One of them is open, less-commercial, and largely built and maintained by people whose first job is not the work they do to maintain this internet. That group includes a ton of open source software, millions of small servers scattered around the world (virtually private or otherwise), and is generally best-effort.

The other internet is fully commercialized, often ad-driven, fully integral to the data broker economy, and centralized behind a few companies that pay as few people as possible to satisfy the occasional PR statement that, "we take security seriously and...".

The next stable equilibrium here is not "we get a secure and open internet". The next stable equilibrium here is, "we have no open internet, and the internet is now managed by just a few companies."

We're already halfway there. Google and Microsoft combined already account for somewhere around 30% to 40% of email traffic. 30% of all websites are now behind Cloudflare. A few companies dominate social media traffic. Amazon and Shopify combined are half of US e-commerce.

Every single short-response-window exploit like this just pushes a few more percentage points of traffic into a handful of companies. Cheer for that, I guess.

When I have time to daydream, it's increasingly about building a new, underground internet, and how best to disadvantage bots and BigCo conglomeration from the start.

Re:Pre-auth RCE in Nginx HTTP/2 handling by VolCoder on Wednesday November 18, 2026 @01:33PM (#50550167)
Appreciate your take. Question in my mind is if the less-commercial internet will have the resources to defend against attacks made easier and easier by AI.
Re:Pre-auth RCE in Nginx HTTP/2 handling by graemep on Wednesday November 18, 2026 @02:06PM (#50550614)
I wonder whether part of the solution is not using the same software as big tech. For them rapid development is worth extra maintenance. Things like the efficiencies of http2 over 1.1 actually matter. Maybe the rest of us should be using BSDs or different Linux distros (Alpine? Void? Slackware?), different web servers, turn off features we do not need (e.g. not disable http2, or at least not allow both 1.1 and 2 as that is clearly extra attack surface).
Re:Pre-auth RCE in Nginx HTTP/2 handling by robotmay on Wednesday November 18, 2026 @02:44PM (#50551123)
My sites are now sat behind my own custom reverse proxy. It's missing tons of features, which I guess I can now call a security benefit, and it pretends to be nginx just because I thought that would be quite funny. I've debated open-sourcing it but I a) don't want to maintain a project right now, and b) security-by-obscurity is back in action.
Re:Pre-auth RCE in Nginx HTTP/2 handling by Shiggy_ on Wednesday November 18, 2026 @05:45PM (#50553434)
Usenet.
Re:Pre-auth RCE in Nginx HTTP/2 handling by seanw444 on Wednesday November 18, 2026 @06:51PM (#50554029)
> When I have time to daydream, it's increasingly about building a new, underground internet, and how best to disadvantage bots and BigCo conglomeration from the start.

https://reticulum.network

Re:Pre-auth RCE in Nginx HTTP/2 handling by Ungh on Wednesday November 18, 2026 @12:57PM (#50549669)
It's brilliant isn't it?

The real problems here are that we did a crappy job in the first place and left a huge surface area of risk with the blind assumption that we didn't do a crappy job.

I am hoping to see a change in attitude to risk and quality in the industry but I get the feeling that's asking for too much.

Re:Pre-auth RCE in Nginx HTTP/2 handling by testtestmetest on Wednesday November 18, 2026 @01:17PM (#50549925)
"Hacker gangs"
Re:Pre-auth RCE in Nginx HTTP/2 handling by sbodnar on Wednesday November 18, 2026 @03:11PM (#50551492)
Just like in the movie "Hackers".
Re:Pre-auth RCE in Nginx HTTP/2 handling by keyle on Wednesday November 18, 2026 @06:43PM (#50553950)
Hey, that's a piece of art!
Re:Pre-auth RCE in Nginx HTTP/2 handling by consumer451 on Wednesday November 18, 2026 @03:52PM (#50551975)
What term do you prefer?
Re:Pre-auth RCE in Nginx HTTP/2 handling by robotnikman on Wednesday November 18, 2026 @06:14PM (#50553712)
Kim Jong Un's megayacht fund
Re:Pre-auth RCE in Nginx HTTP/2 handling by wannabe44 on Wednesday November 18, 2026 @01:41PM (#50550285)
Well I didn't get into any trouble with the professional hacker gangs. The script kiddies on the other hand...
Re:Pre-auth RCE in Nginx HTTP/2 handling by make3 on Wednesday November 18, 2026 @01:52PM (#50550449)
AI is also making it much easier to attack, likely more than it's helping secure things
Re:Pre-auth RCE in Nginx HTTP/2 handling by WarmWash on Wednesday November 18, 2026 @02:21PM (#50550777)
You're a nanometer away from understanding why labs have powerhouse internal models that they only allow partners to use.

Even Kimi K3 was only shipped as a lobotomized version of it.

Re:Pre-auth RCE in Nginx HTTP/2 handling by canibalrex on Wednesday November 18, 2026 @02:34PM (#50550977)
This internal models stuff remains marketing BS afa I am concerned. Smart enough to be a junior engineer and steered toward the right tools and behaviors within a context is more than enough. Places with "super models" do nothing to demonstrate they wouldn't have done better to use the resources on relative brute force within the security domain. They have no sales pitch for good results that just needed Legos and cash.
Re:Pre-auth RCE in Nginx HTTP/2 handling by make3 on Wednesday November 18, 2026 @03:04PM (#50551406)
the idea that internal models can protect the Internet like this is so dumb IMHO.

A huge fraction of devices and servers are on old versions, not actively updated or managed in any way.

Re:Pre-auth RCE in Nginx HTTP/2 handling by pixl97 on Wednesday November 18, 2026 @05:02PM (#50552834)
Then the best option for everyone's security is to hack into them and kill them.

If you're not going to take care of it you've created a public nuisance.

Re:Pre-auth RCE in Nginx HTTP/2 handling by binsquare on Wednesday November 18, 2026 @02:37PM (#50551023)
it's a timing thing - eventually we'll reach an equilibirium

it was previously expensive to attack, so people spent less money on defense.

It's cheaper to attack, and so people will increase their budget on defense. But it's a lagging cause & effect situation

Re:Pre-auth RCE in Nginx HTTP/2 handling by pstuart on Wednesday November 18, 2026 @02:42PM (#50551092)
One would think that the NGINX team would be banging on their code with AI agents trying to attack it for preemptive security.
Re:Pre-auth RCE in Nginx HTTP/2 handling by vagrantJin on Wednesday November 18, 2026 @03:31PM (#50551741)
There's no honor among the thieves if everyone can be a thief.
Re:Pre-auth RCE in Nginx HTTP/2 handling by darkwi11ow on Wednesday November 18, 2026 @03:38PM (#50551826)
Yep. In recent discussion this came up, and my analogy was that LLM will cause a similar effect to widesread proliferation of TLS. It was easy to snitch on people before TLS had been deployed everywhere. Not so much after that.
Re:Pre-auth RCE in Nginx HTTP/2 handling by lbrito on Wednesday November 18, 2026 @04:26PM (#50552334)
Yes but the barrier is infinitely lower. If you were used to running servers just for fun, that kind of threat was probably not too much of a concern. Now it very much is because it can be exploited at a much larger scale.
Re:Pre-auth RCE in Nginx HTTP/2 handling by djha-skin on Wednesday November 18, 2026 @04:26PM (#50552337)
AI provides the capabilities to secure the internet, maybe, but the internet is secured when site owners choose to secure it.

That's not happening at nearly the same pace, both for assymetry between what it takes to break something and what it takes to fix it, but also because that fix must navigate bureaucracies. Also, the leaders need to actually care, both of which are hurdles. Bureaucratic navigation and consensus finding has not sped up at all with AI.

Compare that to independent script kiddies with $600/mo Claude subscriptions able to find 0-days in an hour and write a worm to exploit it in four.

Re:Pre-auth RCE in Nginx HTTP/2 handling by vanschelven on Wednesday November 18, 2026 @11:43AM (#50548506)
and C is the tinderbox
Re:Pre-auth RCE in Nginx HTTP/2 handling by UltraSane on Wednesday November 18, 2026 @11:52AM (#50548642)
The billions of lines of C and C++ code is like a square lightyear of agar for LLMs to find bugs in.
Re:Pre-auth RCE in Nginx HTTP/2 handling by codedokode on Wednesday November 18, 2026 @11:47AM (#50548569)
Not AI but poorly designed programming languages ignoring integer overflows.
Re:Pre-auth RCE in Nginx HTTP/2 handling by vlovich123 on Wednesday November 18, 2026 @11:51AM (#50548629)
I don’t know any systems programming language that doesn’t ignore integer overflow/underflow in release builds. IMHO this is a CPU design flaw - integer operations should carry a flag indicating if the operation is allowed to wrap or if it should generate a trap. Then there wouldn’t be a performance penalty for this and languages like Rust could have it be trapped by default.
Re:Pre-auth RCE in Nginx HTTP/2 handling by codedokode on Wednesday November 18, 2026 @11:55AM (#50548675)
"I don't know any decent language so let's continue using poorly designed languages". Please look at Swift, Javascript, Python.

Why would CPU designers make a trap if languages do not require it?

Re:Pre-auth RCE in Nginx HTTP/2 handling by vlovich123 on Wednesday November 18, 2026 @11:58AM (#50548723)
JavaScript and Python aren’t systems languages. Swift often pays the performance penalty for trapping everywhere and hasn’t seen adoption as a systems language for that reason.
Re:Pre-auth RCE in Nginx HTTP/2 handling by pixl97 on Wednesday November 18, 2026 @12:02PM (#50548787)
How does that saying go?

"Go fast and get your things broken into"

Re:Pre-auth RCE in Nginx HTTP/2 handling by AnthonyMouse on Wednesday November 18, 2026 @02:30PM (#50550920)
We're after a way to go fast without having your things broken into. "Language allows you to specify whether you want wrap around or an exception and hardware makes implementing that efficient" is better than both inefficient runtime checks and silent data corruption.
Re:Pre-auth RCE in Nginx HTTP/2 handling by codedokode on Wednesday November 18, 2026 @09:46PM (#50555436)
Yes, so "+" should trap, and there should be a function that wraps around because wraparound addition is used very rarely (mostly in crypto). It seems that you agree that C is designed the wrong way.
Re:Pre-auth RCE in Nginx HTTP/2 handling by tptacek on Wednesday November 18, 2026 @11:54AM (#50548674)
No. Memory safe languages still have integer handling issues, but the consequences are different. In a memory-unsafe language, integer mishandling often nets out to bad copies and memory corruption.
Re:Pre-auth RCE in Nginx HTTP/2 handling by vlovich123 on Wednesday November 18, 2026 @12:01PM (#50548780)
I wouldn’t be sure that a Rust equivalent would be immune because it’s not hard to imagine an underflow/overflow from reaching an unsafe block that’s used for performance (the implicated TLS path would be a hotspot worthy of such a choice).
Re:Pre-auth RCE in Nginx HTTP/2 handling by tptacek on Wednesday November 18, 2026 @12:04PM (#50548818)
This is the thing about `unsafe` blocks: they're not memory safe. It's right there in the name.
Re:Pre-auth RCE in Nginx HTTP/2 handling by vlovich123 on Thursday November 19, 2026 @12:01AM (#50556247)
Android had an integer overflow vulnerability where it could be tricked into verifying the signing of one file but install another for execution. Boeing 787 Dreamliner had a bug where after 248 it's 32-bit counter overflowed triggering a "fail-safe" mode that shut down all electrical power to the aircraft.

You're right it's more rare but the results can still be catastrophic.

Re:Pre-auth RCE in Nginx HTTP/2 handling by AnthonyMouse on Wednesday November 18, 2026 @02:21PM (#50550781)
Isn't "memory corruption" typically the fast path to RCE? The attacker gets to overwrite a function pointer, or a regular pointer that then lets them overwrite something else, or the length field that will then cause a buffer overrun even in a "safe" language because the run-time length is now different than the one in the compile-time check, etc.
Re:Pre-auth RCE in Nginx HTTP/2 handling by tptacek on Wednesday November 18, 2026 @04:06PM (#50552114)
Memory corruption -> RCE.

Integer handling mistake -> memory corruption -> RCE.

That's the pattern. In a memory-safe language, the integer handling error has no link to memory corruption (though it will to other logic bugs!).

Re:Pre-auth RCE in Nginx HTTP/2 handling by 10000truths on Wednesday November 18, 2026 @12:10PM (#50548920)
Zig traps arithmetic overflow/underflow when compiling in ReleaseSafe.
Re:Pre-auth RCE in Nginx HTTP/2 handling by BoingBoomTschak on Wednesday November 18, 2026 @12:49PM (#50549546)
Lisp or Python have a proper numeric tower and don't default to machine types. Keyword being default, fast is still possible in CL.
Re:Pre-auth RCE in Nginx HTTP/2 handling by benlivengood on Wednesday November 18, 2026 @01:29PM (#50550098)
X86 had the INTO instruction to trigger a fault if the Overflow flag is set, so not quite a per-instruction bit but more of a suffix. JO is also fairly straightforward for compilers to add on important arithmetic operations. We can probably blame C entirely for this; only in C23 are there intrinsics for overflow detection on arithmetic.
Re:Pre-auth RCE in Nginx HTTP/2 handling by codedokode on Wednesday November 18, 2026 @09:45PM (#50555431)
C23 intrinsics are so ugly that nobody is going to use them. They should have made ordinary "+" to trap on overflow, and an ugly instirnsic to wrap around.
Re:Pre-auth RCE in Nginx HTTP/2 handling by rlt on Wednesday November 18, 2026 @11:49AM (#50548604)
I’m generally not in favor of government meddling with private property, but I feel like I could be on board with the NSA or similar covertly patching vulnerable machines.
Re:Pre-auth RCE in Nginx HTTP/2 handling by origini on Wednesday November 18, 2026 @11:51AM (#50548626)
And your first thought was the NSA? Patching and adding their own rootkit eh?
Re:Pre-auth RCE in Nginx HTTP/2 handling by zzril on Wednesday November 18, 2026 @11:53AM (#50548654)
Don't you dare patching my honeypots!
Re:Pre-auth RCE in Nginx HTTP/2 handling by UltraSane on Wednesday November 18, 2026 @11:51AM (#50548622)
AI is just showing how foolish using such a unsafe language like C to write code that connects to every other computer on the internet was.

Imagine a alternate reality where Ada replaced C by 1995. We would be in a MUCH better place.

Re:Pre-auth RCE in Nginx HTTP/2 handling by acdha on Wednesday November 18, 2026 @12:27PM (#50549200)
The bigger problem is lack of liability: we knew C sucked in the 90s, too, but we had three decades of over-confident dudes saying that was user error and _they_ were smart enough to use C correctly.

Then Rust came along and those dudes either tried to say it was too hard (odd contrast, that) or it’d be too much work to rewrite things.

I’m hoping that LLMs will lower the cost of porting for enough people but what would really help is shedding the idea that the status quo is sustainable. Having consequences for sticking with C would help but we need a way to get companies to pay to migrate without destroying open source.

Re:Pre-auth RCE in Nginx HTTP/2 handling by dnautics on Wednesday November 18, 2026 @12:31PM (#50549270)
It's also valid to say that Rust's memory safety is good but the rest of the language sucks. Just as annoying as the over confident c-heads is the rust community that made even countenancing working on an alternative memory safe system a moral sin, which stifled innovation in memory safety. Hell, people barely know that Ada/spark is memory safe (or that sel4 is memory safe C)
Re:Pre-auth RCE in Nginx HTTP/2 handling by antonvs on Wednesday November 18, 2026 @02:40PM (#50551069)
Aside from the overhead of borrow checking, what about the rest of the language sucks, in your view?

To me, its type system and traits design make it one of the nicest mainstream languages. I'd rather be using a functional language, like Haskell or an ML, and I do sometimes, but I don't pick my work based on that. I work regularly with Java, Go, Typescript, and Python, and out of those I find Rust significantly superior on several dimensions.

Python is terrible, Go is basically weakly-typed Python, Typescript barely deserves comment other than that it's impressive that such a fancy type system was bolted onto Javascript, and Java is basically COBOL at this point - reliable, but clunky and showing its age. Attempts like Kotlin to leverage the JVM aren't very convincing.

Gleam looks interesting but I haven't had a chance to work with it yet, and it's hardly mainstream.

You mentioned Ada/SPARK, but SPARK is not really for general purpose programming, and Ada in general has a similar issue to Java, but worse because of its age. It's as if someone really liked PL/I but decided it needed more features and a syntax closer to COBOL.

Re:Pre-auth RCE in Nginx HTTP/2 handling by sophacles on Wednesday November 18, 2026 @03:43PM (#50551872)
What overhead from borrow checking?
Re:Pre-auth RCE in Nginx HTTP/2 handling by FridgeSeal on Wednesday November 18, 2026 @08:44PM (#50555041)
I imagine they are referring to the cognitive overhead of learning to work with it.

Whether that is “something natural to you”, “something you learn and adapt to” or “something you fight with forever” seems to vary per-person, with I suspect, most people falling into the forest 2 categories.

Re:Pre-auth RCE in Nginx HTTP/2 handling by dboreham on Wednesday November 18, 2026 @07:22PM (#50554302)
> what about the rest of the language sucks, in your view

I will chime in here to say that the adoption of async was imho a terrible decision and led me to abandon Rust for most purposes. I want proper threads and CSP-based abstraction.

Re:Pre-auth RCE in Nginx HTTP/2 handling by UltraSane on Wednesday November 18, 2026 @07:36PM (#50554444)
Ownership model is perfect for multithreading but then Rust goes all in on async like WTF?
Re:Pre-auth RCE in Nginx HTTP/2 handling by cozzyd on Wednesday November 18, 2026 @08:55PM (#50555117)
lack of a stable ABI is a big one
Re:Pre-auth RCE in Nginx HTTP/2 handling by dboreham on Wednesday November 18, 2026 @07:21PM (#50554286)
This really isn't true. It's true that those people saying those things existed, but much more recently. Back when all the C/C++ legacy code we depend on today was being written it was the performance penalty imposed by safety that forced developers down that path, not some lack of interest in other options. We were also transitioning from a world where a fair bit of systems code was written in even lower level languages than C (assembler, BLISS, BCPL). The world we're in today effectively began around 1975 when people figured out how to make a C compiler run on an 11/45. All the decisions were pretty much locked in from there on.
Re:Pre-auth RCE in Nginx HTTP/2 handling by ThrowawayR2 on Wednesday November 18, 2026 @05:10PM (#50552946)
[delayed]
Re:Pre-auth RCE in Nginx HTTP/2 handling by dboreham on Wednesday November 18, 2026 @07:16PM (#50554250)
Also in the few years prior to 1995 most computers that could run a C compiler weren't big enough to run an Ada compiler. Heck most computers today can't run the rust toolchain.
Re:Pre-auth RCE in Nginx HTTP/2 handling by fla on Wednesday November 18, 2026 @11:59AM (#50548749)
It’s for the best, IMO. We must now design every system on the assumption that every vulnerability will eventually be exploited and every bug will be found. Relying on security by obscurity or following poor security practices will be costly! In the long run, I believe this will improve software quality.
Re:Pre-auth RCE in Nginx HTTP/2 handling by zodwick on Wednesday November 18, 2026 @12:22PM (#50549132)
There is going to be hardships before this gets better. But it is hardship we must endure
Re:Pre-auth RCE in Nginx HTTP/2 handling by jooops1 on Wednesday November 18, 2026 @12:52PM (#50549598)
Poor security practices are burning down the internet not AI. Many people warned and got ignored, by developing a memory safe language, introduce large scale fuzzing, utilize verification tools and other things.
Re:Pre-auth RCE in Nginx HTTP/2 handling by tgv on Wednesday November 18, 2026 @01:37PM (#50550231)
It's like blaming people for having wooden doors when robots with chainsaws start appearing in the street.
Re:Pre-auth RCE in Nginx HTTP/2 handling by jethro_tell on Wednesday November 18, 2026 @01:48PM (#50550390)
When 85 percent of doors were installed before metal doors were available.
Re:Pre-auth RCE in Nginx HTTP/2 handling by streetfighter64 on Wednesday November 18, 2026 @01:58PM (#50550523)
There's definitely an issue of scale, but a wooden door at least lives up to its own "contract". There's no bugs in a wooden door, everyone can see plainly it doesn't withstand a chainsaw.

A more apt analogy would be that pretty much all consumer-grade locks are very easy to pick, despite being marketed as secure. I think in this case the lock makers should be blamed, not the lock pickers.

Re:Pre-auth RCE in Nginx HTTP/2 handling by crtified on Wednesday November 18, 2026 @02:50PM (#50551190)
It's been a culture decades in the making.

The lock makers are us - the IT field at large. As individuals we might not be to blame, but we are still enthusiastic parts of the greater movement that's issued vast digital complexity to the world without truly understanding it.

Now we are starting to understand it more.

Re:Pre-auth RCE in Nginx HTTP/2 handling by sixothree on Wednesday November 18, 2026 @04:48PM (#50552646)
> robots with chainsaws start appearing in the street

Please stop willing things into existence.

Re:Pre-auth RCE in Nginx HTTP/2 handling by gosub100 on Wednesday November 18, 2026 @03:06PM (#50551418)
What about ASLR and DEP? Guess they are useless?
Re:Pre-auth RCE in Nginx HTTP/2 handling by dilyevsky on Wednesday November 18, 2026 @12:59PM (#50549706)
i still remember win xp pre service pack 1 days where you could get p0wned by a worm just by leaving machine on the internet. this is nothing compared to that.
Re:Pre-auth RCE in Nginx HTTP/2 handling by codedokode on Wednesday November 18, 2026 @09:47PM (#50555443)
Why your standards are so low?
Re:Pre-auth RCE in Nginx HTTP/2 handling by gspr on Wednesday November 18, 2026 @01:10PM (#50549840)
I'm pretty solidly in the AI skeptic camp. But adversarial use of AI to improve software security is a good thing in my mind.

I'd be more worried if the response isn't more secure development practices in better languages, but rather use if AI as a defense. Then we're truly talking about burning down the internet.

Re:Pre-auth RCE in Nginx HTTP/2 handling by pixl97 on Wednesday November 18, 2026 @05:18PM (#50553055)
At the end of the day it will be both. In fact I wouldn't be surprised if we started seeing offensive defense. That is already compromised boxes counter hacked and erased or otherwise made unbootable.

A dead box isn't part of any bot army.

Re:Pre-auth RCE in Nginx HTTP/2 handling by worldsavior on Wednesday November 18, 2026 @01:21PM (#50549993)
This comment is very dramatic and very hype-y. I don't think this is an appropriate comment.
Re:Pre-auth RCE in Nginx HTTP/2 handling by dyauspitr on Wednesday November 18, 2026 @02:08PM (#50550644)
What a strange takeaway. This is exactly how a server at a restaurant thinks about AI. Just the shortest term goals of keeping the status quo. They think that if they bury their head in the sand, everything will continue as normal.
Re:Pre-auth RCE in Nginx HTTP/2 handling by lenerdenator on Wednesday November 18, 2026 @02:25PM (#50550843)
It's going to be rough sledding for a while, but, so long as you're on FOSS, at some point, the bugs and vulns should run out, and best practices trained into AI should hopefully reduce new bugs being introduced.

All bugs are shallow given enough eyes, and the marginal cost of eyes is now ridiculously low.

Re:Pre-auth RCE in Nginx HTTP/2 handling by SV_BubbleTime on Wednesday November 18, 2026 @03:27PM (#50551684)
Every now and then, I think about the old demonization against encryption… and how it completely went away.

Sure, there are niche things. You can’t use US ciphers in China and vice versa.

But overall, one day, the intelligence communities world wide just decided to not raise a fuss about everyone having solid cryptography.

It makes me think if we did find out that every server out there had a route kit… it would make that part make sense.

Re:Pre-auth RCE in Nginx HTTP/2 handling by raincole on Wednesday November 18, 2026 @03:38PM (#50551821)
This is some insane framing. This vulnerability exists already. Even if there were no LLM, this would still exist and might even be actively exploited right now. We just wouldn't have a chance to know it.
Re:Pre-auth RCE in Nginx HTTP/2 handling by tripleee on Wednesday November 18, 2026 @03:56PM (#50552032)
If a vulnerability is practically impossible for a human, but possible for AI, then it's not security through obscurity. Technology just advanced past a line where new things can be exploited.

There might also be a day in the future where our current encryption methods are broken - it doesn't mean they're insecure and vulnerable today.

Re:Pre-auth RCE in Nginx HTTP/2 handling by pixl97 on Wednesday November 18, 2026 @05:12PM (#50552978)
None of these vulns was impossible for a human. There just wasn't that many humans clever enough to find them, and those that did we're busy not hacking random things. There isn't a single type of new exploit that AI has found that I know about.

We have a billon hacking experts now is the big change.

Re:Pre-auth RCE in Nginx HTTP/2 handling by claude-ai on Wednesday November 18, 2026 @03:53PM (#50551997)
I am having a hard time understanding this position. AI is uncovering flaws that "state-level actors" are exploiting since decades, for some of the recently found issue.

Care to elaborate why you think that sufficiently paid humans would not be able to find the flaws AI now finds, for cheap?

Re:Pre-auth RCE in Nginx HTTP/2 handling by Creamsicle47 on Wednesday November 18, 2026 @05:06PM (#50552885)
Agents are simply faster.

Harnesses allow LLMs to build & process large stores of data to reuse later. Imagine an agent that spends 3 days breaking into company A, records what it learned during that process, letting it break into company B in just 3 hours.

Defenders win by having the best security 24/7 and must trust that other services they depend on are doing the same.

An attacker wins when they can breach any defender's security.

Re:Pre-auth RCE in Nginx HTTP/2 handling by tclancy on Wednesday November 18, 2026 @04:06PM (#50552116)
Think of it as the opposite of security through obscurity: at some point the hackers won't be able to keep track of it all. They'll start paying for Jira accounts and need to hire PMs. They'll be patching servers to drive away the competition and will need experienced IT people. Someone is going to have to build apps to keep track of it all.

The circle of life.

Re:Pre-auth RCE in Nginx HTTP/2 handling by Creamsicle47 on Wednesday November 18, 2026 @05:07PM (#50552891)
Not quite
Re:Pre-auth RCE in Nginx HTTP/2 handling by Sebguer on Wednesday November 18, 2026 @04:16PM (#50552232)
For eight years, MongoDB shipped a default configuration that left it opened to the internet with no password.

Obviously, AI makes these things easier to find and exploit, but this isn't even close to the first time that 'thousands' of hobbyist (or small business or just not very competent) server admins are going to get rootkitted en masse. I worked at medium-sized infra-as-a-service company when the above was discovered and there were definitely thousands of compromised machines just there.

Re:Pre-auth RCE in Nginx HTTP/2 handling by cozzyd on Wednesday November 18, 2026 @07:49PM (#50554567)
web scale vulnerabilities
Re:Pre-auth RCE in Nginx HTTP/2 handling by throooooo on Wednesday November 18, 2026 @05:40PM (#50553371)
"Cattle, not pets" has been industry best practice for a long time now. Those that don't follow it will eventually pay the price for one reason or another.
Re:Pre-auth RCE in Nginx HTTP/2 handling by cube00 on Wednesday November 18, 2026 @06:03PM (#50553618)
This is why I worry about upgrading in place, I think every six months or so you really need start from a fresh image.
Re:Pre-auth RCE in Nginx HTTP/2 handling by devopstimetoshi on Wednesday November 18, 2026 @08:31PM (#50554946)
AI is -> Forcing you to PAY UP your Tech Debt.

This is the sys/devops time to shine. Everyone needs to have an upgrade and an emergency plan, and everyone who was previously only doing conventional codemonkey needs to start learning more of the stack to join in on that.

Re:Pre-auth RCE in Nginx HTTP/2 handling by wasmitnetzen on Wednesday November 18, 2026 @11:21AM (#50548204)
Docker images are a bit delayed because of unstable GitHub runners: https://github.com/nginx/docker-nginx/pull/1075#issuecomment...

Cue xkcd

Re:Pre-auth RCE in Nginx HTTP/2 handling by kawsper on Wednesday November 18, 2026 @02:20PM (#50550770)
Sadly, the same happened last time a CVE hit.
Re:Pre-auth RCE in Nginx HTTP/2 handling by 8by3 on Wednesday November 18, 2026 @11:38AM (#50548439)
FreeBSD is unpatched,

I got worried for a sec, then remembered all my nginx lives behind HaProxy and it looks like nginx is only vulnerable if its going http2/TLS directly.

Now I sit and wait for an HaProxy announcement...

Re:Pre-auth RCE in Nginx HTTP/2 handling by wildmXranat on Wednesday November 18, 2026 @12:17PM (#50549033)
I don't know if direct access with no proxy is needed for all 5. CVE-2026-123634 and CVE-2026-113425 is plain HTTP.
Re:Pre-auth RCE in Nginx HTTP/2 handling by birdgoose on Wednesday November 18, 2026 @12:51PM (#50549582)
I could be wrong (my sed is rusty) but I don't think that sed command will help if http2 is enabled at the http block level, it just disables it at the server level which will only take effect if not overridden elsewhere.
Re:Pre-auth RCE in Nginx HTTP/2 handling by 1over137 on Wednesday November 18, 2026 @04:08PM (#50552133)
FreeBSD ports are now updated to nginx 1.30.7.
Re:Pre-auth RCE in Nginx HTTP/2 handling by black3r on Wednesday November 18, 2026 @11:43AM (#50548510)
The bug was apparently fixed in open source repo a week earlier, this could've been abused by anyone smart enough to monitor repos like this for exploitable bugfixes for a week (the commit message even included "Reported by Xint.io" and I'm guessing skilled black hats would know about Xint)

Given that in this case the workaround is as simple as disabling http2, there is honestly no reason why F5/Nginx or any of the reporting teams couldn't at least put out a PSA to disable http2 for the time being before basically telling the whole wide world this exists and how to exploit it.

Especially for software like Nginx which powers a huge part of the internet.

Re:Pre-auth RCE in Nginx HTTP/2 handling by vanschelven on Wednesday November 18, 2026 @11:49AM (#50548592)
These days even the "disable X" is enough to get everybody looking in the right direction though. i.e. such hints are (given enough tokens) already RCEs
Re:Pre-auth RCE in Nginx HTTP/2 handling by Gigachad on Wednesday November 18, 2026 @08:19PM (#50554825)
In my experience, asking an LLM to "Do a security audit" doesn't get you much more than an overview of the most obvious config issues while "look for bugs specifically related to HTTP/2" gives much better results.
Re:Pre-auth RCE in Nginx HTTP/2 handling by verst on Wednesday November 18, 2026 @12:08PM (#50548865)
Disabling http2 can be a big deal. My service is primarily made up of gRPC APIs. Not an option for me to disable http2. Luckily I'm not using nginx at the moment - but I easily could have been.
Re:Pre-auth RCE in Nginx HTTP/2 handling by meowface on Wednesday November 18, 2026 @12:50PM (#50549561)
It's patched so anyone can upgrade to the latest nginx to fix it, thankfully. I agree that just shutting off HTTP/2 is probably non-ideal for a lot of web services.
Re:Pre-auth RCE in Nginx HTTP/2 handling by black3r on Wednesday November 18, 2026 @12:58PM (#50549685)
Neither Ubuntu nor Debian have released patches yet, so if you're using one of these mainstream distributions and install nginx through the distro's package manager, you can't easily "upgrade to the latest nginx" yet. You can however disable HTTP/2 for now.
Re:Pre-auth RCE in Nginx HTTP/2 handling by ChadNauseam on Wednesday November 18, 2026 @01:53PM (#50550467)
[delayed]
Re:Pre-auth RCE in Nginx HTTP/2 handling by sippingabonedry on Wednesday November 18, 2026 @02:03PM (#50550582)
Their package manager and security response is the only reason to use (put up with?) their OS.

If I wanted to build my own software from source every time I'd be running Solaris like a virile man from 2004.

Re:Pre-auth RCE in Nginx HTTP/2 handling by nsoam on Wednesday November 18, 2026 @02:08PM (#50550640)
...or you could use Gentoo.
Re:Pre-auth RCE in Nginx HTTP/2 handling by antonvs on Wednesday November 18, 2026 @02:21PM (#50550776)
Keep the flame alive!
Re:Pre-auth RCE in Nginx HTTP/2 handling by robotmay on Wednesday November 18, 2026 @02:40PM (#50551064)
Embrace true chaos and let an LLM do the config file merges for you in Portage.
Re:Pre-auth RCE in Nginx HTTP/2 handling by bombcar on Wednesday November 18, 2026 @06:52PM (#50554035)
LLMs love gentoo they go hog wild.

Which may be good or bad.

Re:Pre-auth RCE in Nginx HTTP/2 handling by mikepurvis on Wednesday November 18, 2026 @02:16PM (#50550720)
NixOS is probably the best modern option for those who crave building the whole world from source.
Re:Pre-auth RCE in Nginx HTTP/2 handling by prennert on Wednesday November 18, 2026 @02:32PM (#50550942)
yep, already deployed fixes to our fleet (NixOS for the win)
Re:Pre-auth RCE in Nginx HTTP/2 handling by kd913 on Wednesday November 18, 2026 @05:44PM (#50553418)
Or just use it in a podman quadlet?

stable-alpine-slim docker iamge is only 14MB?

Re:Pre-auth RCE in Nginx HTTP/2 handling by usr1106 on Wednesday November 18, 2026 @09:38PM (#50555376)
Alpine recently had https://sshhole.com/

Not saying that thie image is affected (I don't know), but small footprint does not guarantee security either. It can hit systems of any complexity these days.

Re:Pre-auth RCE in Nginx HTTP/2 handling by xorcist on Wednesday November 18, 2026 @02:14PM (#50550693)
Both the Debian and the Red Hat packaging systems are awfully convenient ways to build software from source. It has to be, that's package maintainers do daily. They will install all dependencies, apply the distribution specific patches, build, and package in one operation.

Should your distributor fall of the face of the Earth and you still need to patch software, it is often the fastest way to take the source package, put the security patch in the patch directory, and run.

There is more it, such as versioning it between the last release but below the official upgrade so it's convenient when the offical one comes along, and preparing keys if you require signatures, but that's basically it.

Re:Pre-auth RCE in Nginx HTTP/2 handling by antonvs on Wednesday November 18, 2026 @02:22PM (#50550797)
It makes more sense to install services like nginx via the official containers. In the modern world, the OS is for base services only.
Re:Pre-auth RCE in Nginx HTTP/2 handling by raegis on Wednesday November 18, 2026 @05:23PM (#50553137)
The distributions can customize packages with sensible defaults. Debian usually does, and is incredibly convenient. They usually disable features most people don't use, and allow you to easily switch them on if you choose.
Re:Pre-auth RCE in Nginx HTTP/2 handling by kd913 on Wednesday November 18, 2026 @05:47PM (#50553450)
You are aware of the massive vulnerabilities coming out across software eco-systems recently right?

Ubuntu and other distros have not kept up.

Podman container auto-updates to the latest upstream. It is a minimal surface area given alpine images. Security first containment.

In this day and age with AI attackers and zero-days it is absolutely daft to still treat servers as the old-school pets model.

Re:Pre-auth RCE in Nginx HTTP/2 handling by subsection1h on Wednesday November 18, 2026 @07:08PM (#50554172)
> Podman container auto-updates to the latest upstream

Doesn't this make the system more susceptible to supply chain attacks?

Re:Pre-auth RCE in Nginx HTTP/2 handling by jamesfinlayson on Wednesday November 18, 2026 @09:10PM (#50555204)
Agreed. At a previous job all the important stuff came from repos that always shipped latest.
Re:Pre-auth RCE in Nginx HTTP/2 handling by newsoftheday on Wednesday November 18, 2026 @02:31PM (#50550938)
This looks like it was patched in Ubuntu on the 12th?

https://ubuntu.com/security/notices/USN-9090-1

Re:Pre-auth RCE in Nginx HTTP/2 handling by man8alexd on Wednesday November 18, 2026 @02:39PM (#50551048)
This Ubuntu security notice is about an Apache vulnerability, not nginx.
Re:Pre-auth RCE in Nginx HTTP/2 handling by kayfox on Wednesday November 18, 2026 @02:40PM (#50551063)
> Several security issues were fixed in Apache HTTP Server.

Um, what does this have to do with NGINX?

Re:Pre-auth RCE in Nginx HTTP/2 handling by baggy_trough on Wednesday November 18, 2026 @02:45PM (#50551128)
Re:Pre-auth RCE in Nginx HTTP/2 handling by magahugu on Wednesday November 18, 2026 @05:39PM (#50553345)
Good to see
Re:Pre-auth RCE in Nginx HTTP/2 handling by oddIdentities on Wednesday November 18, 2026 @04:07PM (#50552119)
At least for Debian, http2 is disabled by default, and so not affected.

You would have had to enable http2 and have a buggy Linux kernel to be vulnerable.

Re:Pre-auth RCE in Nginx HTTP/2 handling by fhub on Wednesday November 18, 2026 @06:27PM (#50553813)
FWIW, for nodes that don't have packages, I compiled from source under /opt and deploy scripts check higher version so it will auto switch back when the new packages are installed.
Re:Pre-auth RCE in Nginx HTTP/2 handling by mediaserf on Wednesday November 18, 2026 @10:15PM (#50555606)
You can also add nginx.org repos and install the updated versions from there. https://nginx.org/en/linux_packages.html
Re:Pre-auth RCE in Nginx HTTP/2 handling by hiddenvulkcan on Wednesday November 18, 2026 @02:12PM (#50550680)
It was patched but the docker containers were a few hours behind, I nearly had to build from source on a few servers, until I noticed they were pushing all the tags as I was patching a few hours after the release was cut
Re:Pre-auth RCE in Nginx HTTP/2 handling by throwitaway222 on Wednesday November 18, 2026 @02:16PM (#50550713)
I told me agent to do that - similar situation.
Re:Pre-auth RCE in Nginx HTTP/2 handling by TedDoesntTalk on Wednesday November 18, 2026 @04:24PM (#50552304)
> me agent

Did you talk to it like a pirate?

Re:Pre-auth RCE in Nginx HTTP/2 handling by hiddenvulkcan on Wednesday November 18, 2026 @05:23PM (#50553135)
New caveman version just dropped! /Pirate
Re:Pre-auth RCE in Nginx HTTP/2 handling by dboreham on Wednesday November 18, 2026 @07:08PM (#50554176)
There are large areas of the English speaking world where this is common speech.
Re:Pre-auth RCE in Nginx HTTP/2 handling by Ikersl on Wednesday November 18, 2026 @04:46PM (#50552609)
Definitely, but unfortunately I use Debian for my servers so.
Re:Pre-auth RCE in Nginx HTTP/2 handling by weitendorf on Wednesday November 18, 2026 @02:34PM (#50550971)
If you're using grpc, http2, etc you're so much better off using Envoy proxy

You basically get to piggyback off of a large chunk of big tech's infrastructure and security work. Obviously everything has the risk of security flaws (and I kind of hate that default Envoy builds ship with half-baked filter impls) but it's a generally more mature ecosystem than projects with a lot of smaller/legacy users like nginx

Re:Pre-auth RCE in Nginx HTTP/2 handling by trey-jones on Wednesday November 18, 2026 @03:49PM (#50551940)
I'm not 100% informed on this, but it seems very unbelievable to me that Envoy could be considered more robust or widely used than nginx at any point in history including today. I started using ConnectRPC instead of GRPC almost entirely because it didn't leave me subject to (what I consider to be) an unnecessary dependency in Envoy.
Re:Pre-auth RCE in Nginx HTTP/2 handling by weitendorf on Wednesday November 18, 2026 @04:02PM (#50552092)
I guess I would just say, wordpress is also more widely used than many other projects, but that doesn't necessarily make it more robust or secure than the projects Google, Cloudflare, and security companies develop.

The main reason I see to not use Envoy is that it's very annoying to set up and build, and requires familiarity with things like grpc/proto/low level networking to get right. But if you're using grpc and http2 I think you're generally past that "infra overhead" threshold already and it's going to better serve your needs.

I have pretty much only worked at big tech or my own infrastructure startup, and did some systems/infra work at Google using Envoy for a while. I can't say it's 100% better than nginx but I can say that I've evaluated nginx and a lot of software like it (ie with a similar customer base, ecosystem, and history; like coturn) over the years for my personal use, and every time I've immediately been annoyed by constant security issues or poor http2/L4 networking support that I don't see when I use what Netflix/Google/etc use.

Re:Pre-auth RCE in Nginx HTTP/2 handling by TedDoesntTalk on Wednesday November 18, 2026 @04:20PM (#50552267)
Envoy probably has the advantage that it’s only a reverse proxy server, unlike nginx which has other uses too like a general-purpose web server with optional modules.
Re:Pre-auth RCE in Nginx HTTP/2 handling by weitendorf on Wednesday November 18, 2026 @04:46PM (#50552608)
You can implement custom http filters for envoy or use this for general web serving: https://www.envoyproxy.io/docs/envoy/v1.15.2/configuration/h...

The documentation, DX/UX, and discoverability for these features are pretty bad. But they work well if you know how to do it.

Implementing a custom HTTP filter itself is actually easy, I can share examples I did in the last year for a voice inference stack if anybody is interested. The problem is just that the devloop is very painful, because Envoy doesn't make it easy to know why something isn't working (this is actually most of what I did with it at Google, tons of testing/verification and compatability infra for relatively simple http stuff) and the builds take a very long time.

Re:Pre-auth RCE in Nginx HTTP/2 handling by technion on Wednesday November 18, 2026 @05:04PM (#50552862)
On all my small projects (eg rails apps) the reverse proxy to the app servers is the same server expected to serve the static assets directly. In fact the majority of bot nonsense never goes through the proxy due to path rules.

Envoy is only attractive at a higher scale.

Re:Pre-auth RCE in Nginx HTTP/2 handling by Lucasoato on Wednesday November 18, 2026 @04:54PM (#50552738)
Does Envoy support things like rate limiting?
Re:Pre-auth RCE in Nginx HTTP/2 handling by weitendorf on Wednesday November 18, 2026 @05:03PM (#50552840)
Yes [0]. For a single node you can just use this, it works like the Golang/language rate limiters you might already be familiar with [1]

In a multiple node/distributed architecture you need away to coordinate rate limits across nodes and not try to fight the CAP theorem.

There is a way to do this [2] [3] and although it sounds complicated the shape of the solution (delegating to a third party service that aggregates and provides client-level rate limit metrics across multiple proxies) would still be the same any way you cut it.

[0] https://www.envoyproxy.io/docs/envoy/v1.15.2/configuration/l...

[1] https://www.envoyproxy.io/docs/envoy/v1.15.2/api-v3/extensio...

[2] https://www.envoyproxy.io/docs/envoy/v1.15.2/intro/arch_over...

[3] https://www.envoyproxy.io/docs/envoy/v1.15.2/api-v3/config/r...

Re:Pre-auth RCE in Nginx HTTP/2 handling by fcantournet on Wednesday November 18, 2026 @08:12PM (#50554752)
I don't know what nginx security vetting looks like, but just being older isn't a security guarantee. I know Google spends a lot of manpower on making envoy secure.
Re:Pre-auth RCE in Nginx HTTP/2 handling by verst on Wednesday November 18, 2026 @06:23PM (#50553781)
I am using Envoy :)
Re:Pre-auth RCE in Nginx HTTP/2 handling by voodooEntity on Wednesday November 18, 2026 @06:26PM (#50553804)
What WAF would you suggest to use with envoy? Have been working with Coraza and tbh satisfying is something else. So i wonder what someone that recommends envoy would recommend as WAF for it
Re:Pre-auth RCE in Nginx HTTP/2 handling by weitendorf on Wednesday November 18, 2026 @06:46PM (#50553980)
Personally I serve all static, public content off a CDN and only serve dynamic content through Envoy after it passes AuthN/AuthZ.

I use JWT-based sessions + a remote JWKS (which is remote static content that Envoy can cache) + either a third-party IDP or dedicated login service (this being the only application logic besides Envoy's routing exposed to the public Internet). That way, every envoy auth check is immediate and stateless.

In this setup you don't really need a WAF because all unauthenticated requests redirect to signin or 403, which get strict rate limits on login. An abusive peer that sends a ton of traffic anyway gets blocked at the network/firewall level outside of Envoy. The tradeoff is you need to decide that you aren't going to do unauthenticated SSR, and I will admit this pretty complicated to set up in its entirety.

Re:Pre-auth RCE in Nginx HTTP/2 handling by chanux on Wednesday November 18, 2026 @09:55PM (#50555485)
I wonder if being prepared to switch the reverse proxy you use in whim is a good strategy in this climate.
Re:Pre-auth RCE in Nginx HTTP/2 handling by trollbridge on Wednesday November 18, 2026 @11:16PM (#50556015)
A while ago I started releasing our stuff with dual stacks (originally nginx and haproxy, more recently added traefik to the list).
Re:Pre-auth RCE in Nginx HTTP/2 handling by ktm5j on Wednesday November 18, 2026 @02:51PM (#50551202)
If you're using httpd just fyi - there was a recent RCE vuln for apache that was also http2 specific.
Re:Pre-auth RCE in Nginx HTTP/2 handling by geocar on Wednesday November 18, 2026 @10:59PM (#50555916)
Oof.

One idea that might work for you is client certificates if those are only internal APIs. I don't know about you, but I have a lot more confidence in openssl than the people who use openssl.

I turned off http2 a few years ago https://news.ycombinator.com/item?id=41486452 and absolutely did not regret it.

I do regret every experience I've had with gRPC though. I feel for you.

Re:Pre-auth RCE in Nginx HTTP/2 handling by ghm2199 on Wednesday November 18, 2026 @12:12PM (#50548961)
The patch gap.
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.
Re:Pre-auth RCE in Nginx HTTP/2 handling by requeo on Wednesday November 18, 2026 @01:15PM (#50549906)
These commits weren't visible until today. Yesterday, the last public commit was Nov 9.
Re:Pre-auth RCE in Nginx HTTP/2 handling by TedDoesntTalk on Wednesday November 18, 2026 @04:25PM (#50552318)
How is that done with git?
Re:Pre-auth RCE in Nginx HTTP/2 handling by jen729w on Wednesday November 18, 2026 @04:31PM (#50552386)
Just don't push upstream?
Re:Pre-auth RCE in Nginx HTTP/2 handling by TedDoesntTalk on Wednesday November 18, 2026 @01:27PM (#50550079)
Re:Pre-auth RCE in Nginx HTTP/2 handling by brunoborges on Wednesday November 18, 2026 @01:41PM (#50550292)
> this could've been abused by anyone smart enough to monitor repos like this for exploitable bugfixes for a week

And here lies the risk of AI agents in cybersecurity: the speed of processing for monitoring, scanning, identifying security fixes in open source, writing exploits for affected versions, and attempting infiltration, is a matter of minutes now.

It is not "by anyone smart enough". It is by "anyone ill intentioned enough". They don't need to be super smart anymore.

Re:Pre-auth RCE in Nginx HTTP/2 handling by antonvs on Wednesday November 18, 2026 @02:22PM (#50550804)
How's that alignment going...
Re:Pre-auth RCE in Nginx HTTP/2 handling by rheisen_ on Wednesday November 18, 2026 @02:45PM (#50551135)
As much as I like open weight models.. what alignment lol
Re:Pre-auth RCE in Nginx HTTP/2 handling by icantevenhold on Wednesday November 18, 2026 @01:56PM (#50550500)
This is the reason why the oss project i work for is not publishing commits anymore outside of releases but people are freaking out over this.

Cant win.

Seriously reconsidering if open source has a future nowadays

Re:Pre-auth RCE in Nginx HTTP/2 handling by Aperocky on Wednesday November 18, 2026 @02:04PM (#50550593)
I mean, win or not, it has nothing to do with some people freaking out, and that certainly have nothing to do with whether open source have a future.
Re:Pre-auth RCE in Nginx HTTP/2 handling by icantevenhold on Wednesday November 18, 2026 @03:45PM (#50551899)
Not really sure what you’re trying to say; my main point is that OSS is going to change drastically in the next couple years
Re:Pre-auth RCE in Nginx HTTP/2 handling by antonvs on Wednesday November 18, 2026 @02:23PM (#50550814)
> Seriously reconsidering if open source has a future nowadays

*In C or C++.

Re:Pre-auth RCE in Nginx HTTP/2 handling by pjmlp on Wednesday November 18, 2026 @02:42PM (#50551099)
Until we don't replace UNIX clones, Khronos APIs, LLVM or GCC with something else.

C and C++ will stay around for a very long time, even with AI powered systems.

If anything, maybe that is a call that even if implementing compiler backends is hard and time consuming, bootstraping compilers, and new approaches to OS design, are the only path away from such dependencies.

Re:Pre-auth RCE in Nginx HTTP/2 handling by anthk on Wednesday November 18, 2026 @04:31PM (#50552398)
Rust is on its way. Vulkan is no GL, and Gallium it's something else over classical MESA under SGI/Sun.

Legacy 32 bit users with NetBSD and Hyperbola can survive a little with Go based tools/small browsers/mail/usenet/IRC clients and some web browsers with Bubblewrap, but not forever.

Re:Pre-auth RCE in Nginx HTTP/2 handling by pjmlp on Wednesday November 18, 2026 @05:21PM (#50553108)
Rust being here matters,

https://www.khronos.org

https://vulkan.org/events/vulkanised-2027#program

The only thing closer to it is WSGL.

Also there are much more operating systems than those examples.

Re:Pre-auth RCE in Nginx HTTP/2 handling by gmueckl on Wednesday November 18, 2026 @02:52PM (#50551225)
rust isn't invulnerable.
Re:Pre-auth RCE in Nginx HTTP/2 handling by sophacles on Wednesday November 18, 2026 @03:38PM (#50551827)
A tank isn't invulnerable either, but of someone starts shooting at me I'd rather be in a tank than on a 50 year old bicycle.
Re:Pre-auth RCE in Nginx HTTP/2 handling by hunterpayne on Wednesday November 18, 2026 @06:09PM (#50553666)
Fun fact, Russian soldiers ride on top of their tanks and APCs because its safer than being inside of one during an assault. Doesn't mean you are wrong, but there will always be trade-offs. There is no such thing as perfectly secure.
Re:Pre-auth RCE in Nginx HTTP/2 handling by openasocket on Wednesday November 18, 2026 @07:09PM (#50554189)
Tank desant is practiced because there isn’t room in the tank to fit extra people. It’s very much not safer outside of a tank than inside! It’s actually the worst of both worlds, because you don’t have the armor protection but are highly visible. The only advantage it gives over infantry assault on foot is mobility. Which is why it’s generally only practiced when there aren’t sufficient APCs/IFVs available
Re:Pre-auth RCE in Nginx HTTP/2 handling by dralley on Wednesday November 18, 2026 @09:56PM (#50555488)
Not exactly true. BMPs are death traps, sure, and sitting on top of those instead of in them is rational given the risk of burning to death inside of one or being obliterated by a mine.

But the only reason to sit outside a tank rather than in one is because riding on a vehicle is safer than walking through an open field. Tank crews are not sitting outside of their tanks, and they don't have seats inside for passengers.

Re:Pre-auth RCE in Nginx HTTP/2 handling by hunterpayne on Wednesday November 18, 2026 @06:07PM (#50553653)
Fun fact, these specific types of problems aren't possible on a JVM. Yet somehow Java isn't the right language to write a webserver in. These problems are possible in Rust and C/C++. At least its "hard" to have this type of problem in Rust.

Security is hard and is mostly about the number of engineers and amount of time spent looking at a specific implementation. When writing code, do you think about the problems of leaking information due to different operations taking specific amounts of time? That's an actual concern when writing a prod service that uses the network. And it has to be balanced against scalability and issues caused by DOSes. It isn't trivial and it isn't binary...there are always trade-offs. Nothing will ever be perfectly secure and usable and scalable.

Re:Pre-auth RCE in Nginx HTTP/2 handling by perlgeek on Wednesday November 18, 2026 @02:29PM (#50550899)
So what happens when somebody tries to contribute based on the last-published commit? Do you merge/rebase their contributions for them?
Re:Pre-auth RCE in Nginx HTTP/2 handling by icantevenhold on Wednesday November 18, 2026 @03:44PM (#50551881)
Haven’t figured out how to deal with contributions going forward…

The issue is that we get dozens of PRs, generating a bunch of code is trivial but reviewing and merging it and making sure it doesn’t break in interesting ways is still pretty hard.

Personally I lean towards not accepting code contributions anymore, but accepting design documents for features and l bug reports etc

Re:Pre-auth RCE in Nginx HTTP/2 handling by mort96 on Wednesday November 18, 2026 @04:08PM (#50552137)
How about a strict anti LLM use policy for contributors? It adds what's basically a "proof of human work" challenge to opening new PRs, and effort required to review human PRs usually roughly scales in proportion to the amount of effort required to make human PRs. And human contributors who take time to make a PR manually are probably more likely to become longer term community members and not just drive-by contributors

It's not a perfect solution of course, it just takes OSS back to the fairly broken state it was pre-AI. Still, it might be an improvement and should be at least considered.

Re:Pre-auth RCE in Nginx HTTP/2 handling by baq on Wednesday November 18, 2026 @04:17PM (#50552238)
Amounts to ‘won’t be getting contributions‘ which is maybe not that bad at this point on the timeline
Re:Pre-auth RCE in Nginx HTTP/2 handling by mort96 on Wednesday November 18, 2026 @04:26PM (#50552328)
There's plenty of people who contribute to non-AI open source projects, you just don't get the lazy people who don't want to be a serious part of the project or the people who don't know how to program anymore
Re:Pre-auth RCE in Nginx HTTP/2 handling by icantevenhold on Wednesday November 18, 2026 @08:50PM (#50555086)
We do have a LLM disclosure policy.

I’m not sure how we could enforce an 0 LLM policy in practice though…

Re:Pre-auth RCE in Nginx HTTP/2 handling by seba_dos1 on Wednesday November 18, 2026 @10:26PM (#50555696)
You only need to enforce it enough to fulfill its goals.

https://xkcd.com/810/

Re:Pre-auth RCE in Nginx HTTP/2 handling by cluckindan on Wednesday November 18, 2026 @04:58PM (#50552776)
The future is in closed source ecosystems on a modified Harvard architecture
Re:Pre-auth RCE in Nginx HTTP/2 handling by davidkwast on Wednesday November 18, 2026 @07:16PM (#50554251)
WTF but I get the point
Re:Pre-auth RCE in Nginx HTTP/2 handling by kbolino on Wednesday November 18, 2026 @08:12PM (#50554753)
The actual behavior of a running system is extremely data-dependent. There is no security-relevant distinction between Harvard and modern von Neumann architectures anymore, and it's arguable that there ever was one in the first place.
Re:Pre-auth RCE in Nginx HTTP/2 handling by jamesfinlayson on Wednesday November 18, 2026 @09:15PM (#50555229)
I'm sure things will stabilise in the near future.

That said, I just moved from a Linux based job to a Windows based job and it's been nice not having to be panicked about having update most of the technologies that my last job used. As an aside I did try in the past to make sure we were always updating dependencies but my manager was bothered by the amount of work that created. I'm watching that team now take forever to deal with these issues because they're too far behind to just version number and rebuild.

Re:Pre-auth RCE in Nginx HTTP/2 handling by a34729t on Wednesday November 18, 2026 @03:25PM (#50551662)
Oh everybody worth worrying about is monitoring this on every major repo already.
Re:Pre-auth RCE in Nginx HTTP/2 handling by EGreg on Wednesday November 18, 2026 @03:32PM (#50551748)
HTTP/2 is usually the source of most of these bugs in webservers of all kinds
Re:Pre-auth RCE in Nginx HTTP/2 handling by OJFord on Wednesday November 18, 2026 @05:58PM (#50553566)
Yes, fixing open source software is at most an obfuscated announcement.
Re:Pre-auth RCE in Nginx HTTP/2 handling by tancop on Wednesday November 18, 2026 @11:45AM (#50548533)
Everybody here talking about going back to HTTP/1.1, it's a good stop gap solution but we should really think about moving to HTTP3-only as fast as possible. Changing over is easy, if your server doesn't support it just put it behind a reverse proxy that does.

Unlike IPv6 it doesn't need any OS or ISP support, just a browser that's newer than 2020. Everyone outside of air gap networks and government sites should be switching.

Re:Pre-auth RCE in Nginx HTTP/2 handling by gkbrk on Wednesday November 18, 2026 @12:19PM (#50549069)
HTTP/1.1 is still way better and way simpler than HTTP/3.
Re:Pre-auth RCE in Nginx HTTP/2 handling by seki285 on Wednesday November 18, 2026 @12:35PM (#50549343)
Could you please share why?
Re:Pre-auth RCE in Nginx HTTP/2 handling by lysace on Wednesday November 18, 2026 @01:03PM (#50549754)
~25 years of hardening.
Re:Pre-auth RCE in Nginx HTTP/2 handling by gkbrk on Wednesday November 18, 2026 @01:08PM (#50549820)
Because any HTTP spec after 1.1 is incredibly complicated. You can implement HTTP/1 in half a day, and HTTP/1.1 in a day. But HTTP/2 will probably take you a month and HTTP/3 might take something like 6 months.
Re:Pre-auth RCE in Nginx HTTP/2 handling by qweqwe14 on Wednesday November 18, 2026 @01:47PM (#50550386)
Do you realize that no one writes toy HTTP implementations from scratch? I get that you might have a "suckless" mindset but that's just not how the real world works.
Re:Pre-auth RCE in Nginx HTTP/2 handling by dannyw on Wednesday November 18, 2026 @02:38PM (#50551033)
A simpler protocol has less surface area for vulnerabilities. I think GP was just using that as an expression of this.
Re:Pre-auth RCE in Nginx HTTP/2 handling by doodlesdev on Wednesday November 18, 2026 @02:38PM (#50551037)
[delayed]
Re:Pre-auth RCE in Nginx HTTP/2 handling by cozzyd on Wednesday November 18, 2026 @10:13PM (#50555591)
I've definitely done that before on a microcontroller.
Re:Pre-auth RCE in Nginx HTTP/2 handling by postalrat on Wednesday November 18, 2026 @02:17PM (#50550729)
You forgot about all the networking hardware and software those run on. The difference is negligible.
Re:Pre-auth RCE in Nginx HTTP/2 handling by Liuser on Wednesday November 18, 2026 @02:43PM (#50551106)
It boggles my mind that people are patting themselves on the back for staying on old tech stacks and using a discovered vulnerability as further justification of their decision to stay on h1.1.

No one is implementing h2 and h3 from the ground up.

Vulnerabilities are discovered all the time, the solution is to patch, and if you can’t, downgrade to h1.1 as a mitigation.

But there are many legitimate use cases for h2 (eg bidi streaming, latency improvements) and h3 (eg seamless network switching). If you don’t need these features that’s also fine.

Re:Pre-auth RCE in Nginx HTTP/2 handling by otterley on Wednesday November 18, 2026 @03:04PM (#50551401)
> If you don’t need these features and just serve vanilla text webpages that’s also fine to just use h1.1.

Which, to be fair, is most sites.

Re:Pre-auth RCE in Nginx HTTP/2 handling by oasisbob on Wednesday November 18, 2026 @03:09PM (#50551463)
HTTP 1.1 has enough complex behaviors at the edge that the idea of implementing it in a day, correctly, is wildly laughable.
Re:Pre-auth RCE in Nginx HTTP/2 handling by qurren on Wednesday November 18, 2026 @02:36PM (#50551006)
It's debuggable? I can wireshark it and understand everything. I can even speak it with a telnet client. I can write microcontroller code in C that issues REST API requests. No Pure TCP, nice to work with, no UDP hex craps.

Simple is good.

Re:Pre-auth RCE in Nginx HTTP/2 handling by oasisbob on Wednesday November 18, 2026 @03:06PM (#50551419)
HTTP desync attacks are reason enough to stay as far away from HTTP1.1 as you can:

https://portswigger.net/research/http-desync-attacks-request...

Unfortunately, there are still plenty of customers behind CDNs which don't support HTTP2 for backend origin connections.

Re:Pre-auth RCE in Nginx HTTP/2 handling by layer8 on Wednesday November 18, 2026 @01:06PM (#50549787)
HTTP is used for a lot more things than web pages, and most non-browser clients in production don’t support HTTP/3. The current LTS Java version (25) for example doesn’t support it.
Re:Pre-auth RCE in Nginx HTTP/2 handling by SoftTalker on Wednesday November 18, 2026 @01:22PM (#50550000)
Because HTTP3 was implemented without any errors? Citation needed I guess.
Re:Pre-auth RCE in Nginx HTTP/2 handling by lsof on Wednesday November 18, 2026 @02:31PM (#50550925)
well HTTP3 wouldn't have helped here (CVE-2026-121810)
Re:Pre-auth RCE in Nginx HTTP/2 handling by Imustaskforhelp on Wednesday November 18, 2026 @11:46AM (#50548551)
Okay now I believe that AI is finally burning down the internet and that all the incidents are not just pure coincidences.

Some of these things could've been coincidence but I remember seeing an apache RCE a few days back and people said, oh imagine using Apache, I use Nginx and now not a few days later Nginx has RCE.

And this is just a very very small iceberg of all the recent RCE cases with a serious uptick that I have just observed on Hackernews alone.

Basically, there is a sort of justification that people provide with one RCE is that that software X has had issues and to use Y software, but now that X,Y software and A1...Z1 all are being found to have quite severe bugs. I can't in good faith just consider it to be a coincidence.

Though I do still hope that this might just be a coincidence and not a recurring pattern, because, A) I don't wish to live in that reality where each software that we trusted seems to have quite so many bugs and which would be exploited and B) Have it be continued for a prolonged period of time.

Though the plus point is that we are gonna find extremely resilient software after all of this hopefully as sort of a need in our times.

We might have to agree that the cybersecurity world seems to have changed (though I am no expert right now to comment on it but I am curious what experts think)

Re:Pre-auth RCE in Nginx HTTP/2 handling by origini on Wednesday November 18, 2026 @11:55AM (#50548682)
It was clear a year ago already.

Theh people laughing at Anthropic and co for being cautios of Mythos just didn't understand whats happening.

Instead of finding, hiring and then finding security issues, you can throw money and compute at it. This alone is a complete game changer. Combined with models which are very very capable.

This can be potentially the death of certain programming lanugages or requirement of a complete rewrite. It can mean that only big companies have the resources and capacity to continue playing this game.

Re:Pre-auth RCE in Nginx HTTP/2 handling by dist-epoch on Wednesday November 18, 2026 @01:11PM (#50549855)
Imagine using Nginx
Re:Pre-auth RCE in Nginx HTTP/2 handling by codedokode on Wednesday November 18, 2026 @11:46AM (#50548554)
Integer underflow again. Programming languages should trap on integer overflows and not ignore them. Don't care about legacy CPUs not having a trap for this - they will go sooner or later.
Re:Pre-auth RCE in Nginx HTTP/2 handling by deathanatos on Wednesday November 18, 2026 @12:35PM (#50549341)
Rust has a compile time option, though to my immense disappointment, it defaults to on only in debug mode. (You can opt into it for release, if desired.)

Python simply can't overflow, since its integral type is not a fixed width.

But it is the sort of correctness thing that I do wish languages would pay more attention to.

Re:Pre-auth RCE in Nginx HTTP/2 handling by insanitybit on Wednesday November 18, 2026 @01:24PM (#50550030)
In Rust's case it just matters a lot less since bounds checks are still present. But I do think int under/overflows are probably one of the scarier issues in the language.
Re:Pre-auth RCE in Nginx HTTP/2 handling by codedokode on Wednesday November 18, 2026 @09:57PM (#50555499)
Overflows are dangerous by itself. Assume you keep the order total price as uint32. Someone orders a spaceship for 2.2B credits, and then adds another one which is not an expected scenario. The total counter overflows and now you have sold 2 expensive spaceships at 99% discount.
Re:Pre-auth RCE in Nginx HTTP/2 handling by TZubiri on Wednesday November 18, 2026 @01:32PM (#50550159)
>Python simply can't overflow, since its integral type is not a fixed width.

Python master race

Re:Pre-auth RCE in Nginx HTTP/2 handling by IshKebab on Wednesday November 18, 2026 @05:42PM (#50553394)
While I do think that was one of (maybe the only) really great decision Python made... There are so many other things wrong with it that it's a poor choice for almost anything in my book.
Re:Pre-auth RCE in Nginx HTTP/2 handling by hollerith on Wednesday November 18, 2026 @11:48AM (#50548576)
HTTP/2 is so complicated that the code that handles it tends to be vulnerable. What a surprise
Re:Pre-auth RCE in Nginx HTTP/2 handling by acdha on Wednesday November 18, 2026 @12:37PM (#50549368)
This doesn’t seem very HTTP/2 specific, though, and it seems more like the conclusion should be “don’t use C for things which matter”. It’s not like HTTP pipelining and keepalives didn’t have plenty of edge cases to worry about.
Re:Pre-auth RCE in Nginx HTTP/2 handling by basilikum on Wednesday November 18, 2026 @01:17PM (#50549933)
True, but offering three different protocols with different code paths for the same thing is a lot more attack surface. If you start factoring in different compression methods things look even worse.
Re:Pre-auth RCE in Nginx HTTP/2 handling by dist-epoch on Wednesday November 18, 2026 @01:10PM (#50549842)
Caddy also supports HTTP/2 and it's not affected.

In fact in general there were waaay less CVEs for Caddy lately compared to nginx

Re:Pre-auth RCE in Nginx HTTP/2 handling by fullstop on Wednesday November 18, 2026 @02:24PM (#50550835)
I have used nginx for ages, but have been slowly moving things over to Traefik + Caddy.

I guess it was the right move.

Re:Pre-auth RCE in Nginx HTTP/2 handling by Juvination on Wednesday November 18, 2026 @11:56AM (#50548701)
Nginx Proxy Manager isn't updated yet, I know a lot of people use this for their home server so just a reminder to disable http/2 here as well.
Re:Pre-auth RCE in Nginx HTTP/2 handling by wolttam on Wednesday November 18, 2026 @12:15PM (#50549010)
Disabling http/2 here is a bit of a pain: you have to go through each configured host and disable it, there's no global switch
Re:Pre-auth RCE in Nginx HTTP/2 handling by timw4mail on Wednesday November 18, 2026 @02:17PM (#50550723)
Yes, but multi-file find and replace exists, and you can verify every replacement.
Re:Pre-auth RCE in Nginx HTTP/2 handling by therepanic on Wednesday November 18, 2026 @11:57AM (#50548705)
What’s the point of these researchers if their autonomous system is now finding these vulnerabilities?
Re:Pre-auth RCE in Nginx HTTP/2 handling by pixl97 on Wednesday November 18, 2026 @12:13PM (#50548978)
Making sure AI isn't hallucinating.
Re:Pre-auth RCE in Nginx HTTP/2 handling by jwr on Wednesday November 18, 2026 @11:57AM (#50548712)
I am growing increasingly annoyed at Ubuntu for not keeping up. This was disclosed, patched software has been available, yet LTS is still on unpatched version.
Re:Pre-auth RCE in Nginx HTTP/2 handling by hokkos on Wednesday November 18, 2026 @12:15PM (#50549002)
don't know why the mainline alpine have the empty image sha-256 : https://hub.docker.com/layers/library/nginx/1.31.9-alpine/im...
Re:Pre-auth RCE in Nginx HTTP/2 handling by FAYSAL-KA on Wednesday November 18, 2026 @12:37PM (#50549370)
i dont know what it is this but good work
Re:Pre-auth RCE in Nginx HTTP/2 handling by sandeepkd on Wednesday November 18, 2026 @12:40PM (#50549410)
I have mixed feelings. There is a bug for sure, the impact is what I am not convinced of. The Demo shows exploiting its own request, I do not know if that should even be considered.

On the top, the article was so much LLM generated, it was painful to read through the repetitions to understand the details of the vulnerability

Re:Pre-auth RCE in Nginx HTTP/2 handling by hacker_homie on Wednesday November 18, 2026 @12:50PM (#50549549)
This sound suspiciously similar to the issue Microsoft said they were dealing with excess traffic on their front door, taking them down. maybe not an RCE but a DOS in the same http/tls code.
Re:Pre-auth RCE in Nginx HTTP/2 handling by 0xBA5ED on Wednesday November 18, 2026 @01:22PM (#50550001)
Imagine there are 1 million things to know. Some of them are related but most of them aren't. Now imagine that you know 10 things.
Re:Pre-auth RCE in Nginx HTTP/2 handling by puszczyk on Wednesday November 18, 2026 @12:51PM (#50549563)
ugh, looks like if you still run ingress-controller (you shouldn't but it was super popular and there was a very little time to migrate away) you won't get these patches https://github.com/kubernetes/ingress-NGINX
Re:Pre-auth RCE in Nginx HTTP/2 handling by andrelaszlo on Wednesday November 18, 2026 @12:52PM (#50549596)
I assume OpenResty is affected as well? ("High Performance Web Platform Based on Nginx and LuaJIT")
Re:Pre-auth RCE in Nginx HTTP/2 handling by pelzatessa on Wednesday November 18, 2026 @01:03PM (#50549747)
OPs article mentions 2 CVEs, however this one claims that there are 5 new ones: https://news.ycombinator.com/item?id=50547423
Re:Pre-auth RCE in Nginx HTTP/2 handling by testtestmetest on Wednesday November 18, 2026 @01:21PM (#50549996)
Isreael btw everyone at Wiz is a veteran of Unit 8200.

But sure, keep telling yourself this is AI lmfao and anyone can hack because of LLMs.

Re:Pre-auth RCE in Nginx HTTP/2 handling by manishrana on Wednesday November 18, 2026 @01:28PM (#50550084)
Everyday we are seeing new vulnerabilities. Thanks to AI
Re:Pre-auth RCE in Nginx HTTP/2 handling by insanitybit on Wednesday November 18, 2026 @01:39PM (#50550263)
Did AI write this vuln?
Re:Pre-auth RCE in Nginx HTTP/2 handling by tguedes on Wednesday November 18, 2026 @02:31PM (#50550934)
Both this vuln and the java4shell vuln from yesterday have very narrow attack vectors. It's not impossible for a human to figure out, but it does feel like an AI was used to discover both of these vulns.

That's to say that this is our new normal. Something that would have taken months or years to figure out can now take an AI hours if not minutes if you have enough compute.

Re:Pre-auth RCE in Nginx HTTP/2 handling by insanitybit on Wednesday November 18, 2026 @04:49PM (#50552660)
Right, but a human wrote the vulnerable code.
Re:Pre-auth RCE in Nginx HTTP/2 handling by marcosdumay on Wednesday November 18, 2026 @02:13PM (#50550690)
Thanks to "C is perfectly safe if you know what you are doing".
Re:Pre-auth RCE in Nginx HTTP/2 handling by FLeXMurphy on Wednesday November 18, 2026 @01:29PM (#50550101)
Is this going to end up being another exploit that requires a ridiculous amounts of special conditions so as to not actually be applicable to majority of sites running nginx?
Re:Pre-auth RCE in Nginx HTTP/2 handling by bethekidyouwant on Wednesday November 18, 2026 @04:49PM (#50552649)
At this point, I’m not even going to check, so far all of these have been nothing burgers
Re:Pre-auth RCE in Nginx HTTP/2 handling by xmcp123 on Wednesday November 18, 2026 @06:35PM (#50553893)
I think the problem is that while what you say is true, AI is also capable of generating the special conditions required. And if it can’t do so reliably, it can sit there hammering the server for as long as it takes until the conditions are met - as an example hitting a bunch of load balanced servers until 2 requests hit the same workhorse sequentially.

It is completely realistic that we start seeing a lot of bugs a human can’t (reasonably) exploit, but AI can.

Re:Pre-auth RCE in Nginx HTTP/2 handling by TZubiri on Wednesday November 18, 2026 @01:31PM (#50550143)
Hey this is TZubiri, the guy that comments that you should uninstall the dep whenever there is an post about a CVSS 9+ vuln.

Today we are going to take a look at how to avoid this vuln by not having Nginx and not using HTTP/2 (for most use cases).

We will assume that you are using Nginx for any of the following: Serving files or serving dynamic website content through some integration with a programming language.

We will be using python, but you can use any programming language that has a native integration with sockets through it's C interface (literally every language:

Step 1: import socket # import the socket library from glibc or glibc.

Step 2: socket.socket() # socket.socket()

Step 3: socket.bind((PUBLIC_ADDR,80)) # bind before listening obviously. Use a local address if you are below the IPoverty4 line.

Step 4: conn,addr = socket.accept() # this creates a connection, wrap it in a While True and a try catch for production. Sprinkle in some import threading to support multiple concurrent requests.

Step 4: req = conn.recv(4096) # split on b"\r\n\r\n" to separate headers from body, read HTTP RFCs for the rest. Feel free to reject HTTP/2 requests, they'll probably just resend as HTTP/1.1

Step 5: #Fill in the details, most likely if you are using nginx, you will end up connecting two sockets with pipe, or just storing and forwarding to another tcp endpoint. Again take a look at the HTTP RFCs and the glibc socket and stdio manuals.

Thank you for reading my tutorial, and best of lucks.

Re:Pre-auth RCE in Nginx HTTP/2 handling by timw4mail on Wednesday November 18, 2026 @02:19PM (#50550754)
I'm sure this will happen much more than it should.
Re:Pre-auth RCE in Nginx HTTP/2 handling by fduran on Wednesday November 18, 2026 @01:40PM (#50550277)
Small consolation but HTTP/2 is not enabled by default in Nginx and "only" 12% of servers run it (still huge at Internet scale) https://w3techs.com/technologies/segmentation/ce-http2/web_s...
Re:Pre-auth RCE in Nginx HTTP/2 handling by testtestmetest on Wednesday November 18, 2026 @01:44PM (#50550345)
To all the people here that would like to give AI credit for everything, and dont think it matters that everyone at Wiz is Israel Ex Cyber "Defense", and all you need is AI to find things like this. I have a challenge for you:

If you think you can do it or that anyone with AI dan be dangerous. Please, right now put everything down.. Go make a h1,bugcrowd acct and start making millions. If its as easy as having access to llms please go get rich. I assure you just having access to tokens doesnt get you very far.

Re:Pre-auth RCE in Nginx HTTP/2 handling by hosteur on Wednesday November 18, 2026 @02:39PM (#50551044)
Well, you can't because the LLMs are all nerfed and censored w.r.t cybersecurity.

I'm not saying domain knowledge is not required. But a lot of people do have domain knowledge and are prevented from using these tools. Even to secure own code bases. This sucks. A lot.

Re:Pre-auth RCE in Nginx HTTP/2 handling by testtestmetest on Wednesday November 18, 2026 @04:23PM (#50552293)
The refusals do not make that big of a difference! Holy cope. No you still need to study and become an expert. Ill give you access to unlocked fable and you still wont be able to do much with it if you dont have a ton of experience hunting bugs.
Re:Pre-auth RCE in Nginx HTTP/2 handling by red75prime on Wednesday November 18, 2026 @10:33PM (#50555747)
Cope ping-pong is a bit ridiculous, but you need to believe weird things about the human brain if you think that only humans can be experts.
Re:Pre-auth RCE in Nginx HTTP/2 handling by wildmXranat on Wednesday November 18, 2026 @02:54PM (#50551252)
The only people who have access to full throttle, no-rejection security pipeline are the OpenAI employees and very preferred security partners...

This is a monumentally dumb assertion that any Job Blow can just add a credit card and ram through these requests

Re:Pre-auth RCE in Nginx HTTP/2 handling by testtestmetest on Wednesday November 18, 2026 @04:19PM (#50552260)
Keep telling yourself that! The refusals arent that big of a deal. I have access to all the models without refusals. Your average joe still would not be able to hack something with it.

So much cope on this site. Llms havent replaced the requirement of studying and becoming an expert.

Re:Pre-auth RCE in Nginx HTTP/2 handling by NCFZ on Wednesday November 18, 2026 @05:26PM (#50553190)
if it wasn't AI then how do you explain 3 other companies co-discovering the issue? Also, didn't one of the companies discover it before Wiz?
Re:Pre-auth RCE in Nginx HTTP/2 handling by pelzatessa on Wednesday November 18, 2026 @01:53PM (#50550457)
If you want to check if your host might be vulnerable:

https://xint.io/blog/nginx2root-remote-code-execution#23-com...

Workarounds if you're vulnerable and can't update immediately:

https://xint.io/blog/nginx2root-remote-code-execution#33-eme...

Re:Pre-auth RCE in Nginx HTTP/2 handling by Aachen on Wednesday November 18, 2026 @05:50PM (#50553485)
That first link sounded like a scanner that'll actually verify your fix or workaround but it's just a long version of "check yourself if you run a vulnerable version and have http2 enabled". To save others a click
Re:Pre-auth RCE in Nginx HTTP/2 handling by 3abiton on Wednesday November 18, 2026 @06:49PM (#50554006)
It's becoming mentally costly to maintain personal VPS. Beside the time you have to put into it, now it's also worries of a vulnerability you missed, and boom, you're hacked.
Re:Pre-auth RCE in Nginx HTTP/2 handling by tgma on Wednesday November 18, 2026 @02:07PM (#50550629)
As much as everyone is getting allergic to Rust migrations that sometimes make little sense, keeping network-facing daemons in C is just asking for it at this point. It's time to start seriously migrating to web servers like https://xinproxy.com or ferron or whatnot.
Re:Pre-auth RCE in Nginx HTTP/2 handling by Creamsicle47 on Wednesday November 18, 2026 @02:19PM (#50550748)
I've reached the same conclusion myself. Many of the recent exploits seem like edge-cases that the author acknowledged 10-20 years ago but didn't predict that tools would eventually be able to chain together 100k network requests in order to trigger a buffer overflow.
Re:Pre-auth RCE in Nginx HTTP/2 handling by pclmulqdq on Wednesday November 18, 2026 @02:26PM (#50550858)
Software doesn’t generally get checked for bugs until it has users. These new web servers mostly have that going for them rather than the language.
Re:Pre-auth RCE in Nginx HTTP/2 handling by tgma on Wednesday November 18, 2026 @02:31PM (#50550928)
It is true that mileage is a good proxy for finding bugs, but this is isomorphic to the fundamental differences between testing v. verification. You can prove absence of classes of bugs with verification. Obviously there can be other logic bugs in newer software. No question. The issue is the memory-corruption bugs in socket-facing daemons can have catastrophic consequences, especially in light of chaining kernel vulnerabilities which defeats the privilege drop that nginx does.

So I'd say it is about a more holistic risk-analysis not just handwaving "all code can have bugs, duh!"

Re:Pre-auth RCE in Nginx HTTP/2 handling by uecker on Wednesday November 18, 2026 @02:40PM (#50551055)
A more holistic risk-analysis would also need to consider the fact that a high-performance webserver written in Rust may also have memory safety issue due to use of "unsafe" features or unsafe dependencies, may be affected by memory safety issues in the standard library, may also have catastrophic logic errors, may be more affect by supply chain risks due to the use of a language-level package manager, and may have a larger patch gap.
Re:Pre-auth RCE in Nginx HTTP/2 handling by ViewTrick1002 on Wednesday November 18, 2026 @02:46PM (#50551139)
Which is like complaining that Python is written in C.

Which is a far smaller surface as seen by research into incorporating rust in Android leading to none of the high profile vulnerabilities C and C++ led to previously.

Re:Pre-auth RCE in Nginx HTTP/2 handling by uecker on Wednesday November 18, 2026 @02:49PM (#50551169)
By research you mean blog posts by Google?
Re:Pre-auth RCE in Nginx HTTP/2 handling by ViewTrick1002 on Wednesday November 18, 2026 @02:56PM (#50551279)
What specifically distinguishes the empirical research presented in Google’s blog post from your definition of research?

https://blog.google/security/rust-in-android-move-fast-fix-t...

Re:Pre-auth RCE in Nginx HTTP/2 handling by uecker on Thursday November 19, 2026 @12:40AM (#50556450)
Research is not just making some plots and posting them on the internet. A proper scientific studies would need to be done much more carefully, if you want to get meaningful results, because there is a lot which can go wrong at any level. This is something learned people learned the hard way in empirical sciences. In particular, in this setting I do not see how one could ever properly control for confounding factors. Such a study should also be peer reviewed. Also if there are commercial interests mixed-up this needs to be questioned carefully.
Re:Pre-auth RCE in Nginx HTTP/2 handling by ux266478 on Wednesday November 18, 2026 @03:44PM (#50551875)
Not in the slightest. It's like pointing out that a Python script calling out to binaries written in C doesn't have the memory safety of Python's GC. Which is obviously the case, and if you're a serious developer it's a failure point you're very mindful of.

On the Android point, I remember those metrics were highly flawed and didn't account for the inequality of substructural type ergonomics in different contexts. You can get very nice metrics by rewriting things that fit to the grain of safe Rust, which gives you an inaccurate picture of how much unsafe code is "real world". LLMs have changed the field here, but it's worth pointing out that blog post you're referencing was more self-congratulatory marketing than serious science.

Also problematically, I remember it being highly misleading in that the actual observed result was lower severity in vulnerabilities, but a very minimal effect on the total number over all. That's certainly significant, but it wasn't how it presented itself, which is rather problematic if you expect people to take it seriously.

Measurements probably real, but not worth citing.

Re:Pre-auth RCE in Nginx HTTP/2 handling by dralley on Wednesday November 18, 2026 @03:30PM (#50551719)
This argument is cope.

In theory, that could be possible. In practice, there have been many many case studies demonstrating the opposite.

e.g. Cloudflare replaced Nginx with Pingora: https://blog.cloudflare.com/how-we-built-pingora-the-proxy-t...

> With those assurances we can focus more on how a change to our service will interact with other services or a customer's origin. We can develop features at a higher cadence and not be burdened by memory safety and hard to diagnose crashes.

> When crashes do occur an engineer needs to spend time to diagnose how it happened and what caused it. Since Pingora's inception we’ve served a few hundred trillion requests and have yet to crash due to our service code.

> In fact, Pingora crashes are so rare we usually find unrelated issues when we do encounter one. Recently we discovered a kernel bug soon after our service started crashing. We've also discovered hardware issues on a few machines, in the past ruling out rare memory bugs caused by our software even after significant debugging was nearly impossible.

The CVE counts for new parts of the Linux kernel written in Rust are much lower than the (recent) CVE counts for even mature, years old parts of the Linux kernel written in C, to say nothing of the historical record.

Re:Pre-auth RCE in Nginx HTTP/2 handling by slopinthebag on Thursday November 19, 2026 @12:07AM (#50556279)
A more holistic risk-analysis would also need to consider the fact that wearing seatbelts in motor vehicles still leaves drivers vulnerable to drive-by shootings, may be affected by massive boulders crashing on top of the vehicle, driving off a bridge, or gas explosions, and costs more to produce.
Re:Pre-auth RCE in Nginx HTTP/2 handling by tkz1312 on Wednesday November 18, 2026 @02:36PM (#50551009)
I now run all my network facing C code via fil-c. I have limited needs (ssh, static file server), but for those it works very well. I personally am more in favour of making existing battle tested C safer via fil-c or formal verification, than I am of rewriting the world in rust.

New code means new bugs, and losing the many years of accumulated bug fixes and hardening present in many critical pieces of our infra by rewriting in rust is not a desirable tradeoff. The new world we live in where fv has become many orders of magnitude cheaper also makes rust seem much less attractive.

Re:Pre-auth RCE in Nginx HTTP/2 handling by tgma on Wednesday November 18, 2026 @02:38PM (#50551027)
Fil-C is also a great solution, albeit with different performance trade-offs.
Re:Pre-auth RCE in Nginx HTTP/2 handling by safercplusplus on Wednesday November 18, 2026 @03:46PM (#50551908)
In theory, scpptool provides another solution with different performance, compatibility and portability trade-offs. Unlike Fil-C, it is not "fanatically compatible" with existing C code. But in theory, with maybe some minor adjustments to the code (and maybe less-minor adjustments to the build system), you can auto-translate your existing C code base to an essentially memory-safe subset of C++ at build-time [1].

While generally more of a hassle than Fil-C, the scpptool approach provides an incremental path to optimal performance (for performance-sensitive sections of the code) via migration to a (statically-enforced) memory-safe subset of C++. And unlike Fil-C, the scpptool solution essentially maintains the portability of the original code, as well as its deterministic performance and resource usage (i.e. no GC). It also supports ABI compatibility via "unsafe"/"check-suppression" annotations. The scpptool approach is not so much an alternative to Fil-C, as it is an optional path forward for C (or C++) code bases that may (or may not) be already using Fil-C for memory safety.

[1] https://github.com/duneroadrunner/SaferCPlusPlus-AutoTransla...

Re:Pre-auth RCE in Nginx HTTP/2 handling by pixl97 on Wednesday November 18, 2026 @05:50PM (#50553482)
What good is a car that goes 1000 miles per hour if it has no brakes?

It's time for performance above everything else to die, especially on anything and everything that gets anywhere close to untrusted data.

Re:Pre-auth RCE in Nginx HTTP/2 handling by codedokode on Wednesday November 18, 2026 @09:52PM (#50555461)
In many cases the performance is not that important, for example, SSH is often used to transmit mere kilobytes of text per second and I would prefer a safe SSH to a faster unsafe SSH. Or take mDNS, it servers several requests per minute max.
Re:Pre-auth RCE in Nginx HTTP/2 handling by gspr on Wednesday November 18, 2026 @02:58PM (#50551300)
This sounds like a fantastic solution, especially for non-high-volume stuff. Would you consider writing down your setup and experiences? I'm sure it'll be a hit on this site!
Re:Pre-auth RCE in Nginx HTTP/2 handling by jazzyjackson on Wednesday November 18, 2026 @03:23PM (#50551638)
fv?
Re:Pre-auth RCE in Nginx HTTP/2 handling by whilenot-dev on Wednesday November 18, 2026 @03:29PM (#50551706)
[delayed]
Re:Pre-auth RCE in Nginx HTTP/2 handling by andrepd on Wednesday November 18, 2026 @03:30PM (#50551729)
Formal verification.
Re:Pre-auth RCE in Nginx HTTP/2 handling by remixer-dec on Wednesday November 18, 2026 @05:42PM (#50553391)
Same, made a fil-c fork of nginx a while back, saved me from many RCEs https://github.com/remixer-dec/filc-nginx Don't have the tokens to maintain it though :(
Re:Pre-auth RCE in Nginx HTTP/2 handling by pjmlp on Wednesday November 18, 2026 @02:39PM (#50551049)
See Morris worm, and when it took place, afterwards check Multics security assement done by the DoD versus UNIX.

Additionally, check what the inventors themselves of UNIX and C did after being done with them, and what they did afterwards in terms of operating systems and programming languages.

Yet, some folks are more attached to C than the inventors themselves.

Re:Pre-auth RCE in Nginx HTTP/2 handling by cisrockandroll on Thursday November 19, 2026 @12:58AM (#50556540)
So what is the solution, rewrite in Rust?
Re:Pre-auth RCE in Nginx HTTP/2 handling by dyauspitr on Wednesday November 18, 2026 @02:41PM (#50551082)
As someone that was a developer for a long time what is the problem with C? How does going to rust mitigate this? Why is having the stuff in C a security challenge?
Re:Pre-auth RCE in Nginx HTTP/2 handling by unrented7977 on Wednesday November 18, 2026 @02:44PM (#50551116)
Some people think it's fundamentally impossible for C to be correct or memory safe
Re:Pre-auth RCE in Nginx HTTP/2 handling by dralley on Wednesday November 18, 2026 @03:36PM (#50551781)
Fundamentally impossible? No.

Practically impossible? Yes.

SQLite is probably the most thoroughly tested and carefully developed C library in history and they still found a handful of memory safety bugs every year.

Re:Pre-auth RCE in Nginx HTTP/2 handling by djha-skin on Wednesday November 18, 2026 @02:48PM (#50551166)
Rust is memory safe at the cost of being harder to write, but with AI, it's actually really easy to write it because AI's loove strict compilers. So now that AIs can just find 0-days before things are even released (so I'm told), it makes a lot of sense to do bun[1]-style rewrites to Rust with AI.

1: https://bun.com/blog/bun-in-rust

Re:Pre-auth RCE in Nginx HTTP/2 handling by shakna on Wednesday November 18, 2026 @03:11PM (#50551497)
[delayed]
Re:Pre-auth RCE in Nginx HTTP/2 handling by djha-skin on Wednesday November 18, 2026 @04:20PM (#50552270)
I read 0 days like "Exploitable 0 days since _discovery_". Also, it's only a bug in the normal lifecycle if the discoverer tells the developer making it. If they discover it and then have hours and days to perfect a program that exploits it, then starts running immediately when it is deployed or released, that's a new kind of "zero day". Makes you want to start differentiating what "0 days" mean, though.
Re:Pre-auth RCE in Nginx HTTP/2 handling by shakna on Wednesday November 18, 2026 @05:01PM (#50552823)
[delayed]
Re:Pre-auth RCE in Nginx HTTP/2 handling by djha-skin on Wednesday November 18, 2026 @08:04PM (#50554688)
The ai told the hacker. The hacker discovered it with his AI before the developer released by examining his git branch.

I think that's the fundamental disconnect in the conversation here. You think I'm talking about the dev because it's not released yet but just because it isn't tagged and released doesn't mean it's not done in the open where hackers can see it and their AI can scan it.

Re:Pre-auth RCE in Nginx HTTP/2 handling by Delk on Wednesday November 18, 2026 @03:47PM (#50551921)
It's very easy to accidentally write buffer overflows, use-after-frees or other memory-safety bugs in C. Modern tooling can probably catch some of these better than in the days of yore but the fundamentals of the language are still safe.

If e.g. the standard array type in a language has built-in bounds checks that error out when you try to write to an index that's outside of the array, you can't trivially create buffer overflows simply by writing to the wrong index or by trying to write n + 10 bytes into an n-byte array.

But C in itself has no guardrails against something like

  char buffer[100];
  strcpy(buffer, some_user_supplied_string_with_200_chars);
Of course most memory safety bugs aren't trivial like that since C programmers have hopefully learned to avoid the simple mistakes. But there can be more complicated and difficult to spot cases, and C has no guardrails against those either.
Re:Pre-auth RCE in Nginx HTTP/2 handling by jrosenth0 on Wednesday November 18, 2026 @02:48PM (#50551156)
is xinproxy open source? the website only has binaries and I couldn't find anything on github
Re:Pre-auth RCE in Nginx HTTP/2 handling by tgma on Wednesday November 18, 2026 @02:55PM (#50551257)
Ferron is opensource. xin isn't yet.
Re:Pre-auth RCE in Nginx HTTP/2 handling by unethical_ban on Wednesday November 18, 2026 @02:51PM (#50551207)
If we're suggesting alternative web servers, I have had a pleasant experience with caddyserver (Go). It's been around 10+ years, has essentially transparent TLS certificate provisioning, and its config syntax is easy to understand. Even using AI to help vet configs, it's readable. It's packaged everywhere and has lots of plugins for things, though I only need the base package for my frontend proxy usecase.
Re:Pre-auth RCE in Nginx HTTP/2 handling by drnick1 on Wednesday November 18, 2026 @02:58PM (#50551297)
Nginx and C have been around for decades. Migrating to new, poorly tested (in the real world) software does not seem an improvement at all.
Re:Pre-auth RCE in Nginx HTTP/2 handling by Klonoar on Wednesday November 18, 2026 @03:12PM (#50551507)
I mean, a lot of nginx use cases can be handled by e.g caddy - which does have significant real world deployment.
Re:Pre-auth RCE in Nginx HTTP/2 handling by rafaelmn on Wednesday November 18, 2026 @03:14PM (#50551533)
Given the volume and depth of testing possible with AI these days I'd say the decades of testing it's that expensive to reproduce these days, especially if it's an OSS project with a public bug tracker.
Re:Pre-auth RCE in Nginx HTTP/2 handling by dralley on Wednesday November 18, 2026 @03:16PM (#50551563)
Nobody is saying that it needs to be rushed. Cloudflare started moving towards Rust more than a decade ago and (shortly after heartbleed happened) and rolled it out bit by bit. I'm sure there were problems here and there but it's hardly been a drag on them.
Re:Pre-auth RCE in Nginx HTTP/2 handling by LoganDark on Wednesday November 18, 2026 @02:58PM (#50551310)
No idea what the code is like, but the AI-generated landing page makes xinproxy an immediate "no thanks" for me.
Re:Pre-auth RCE in Nginx HTTP/2 handling by kodebach on Wednesday November 18, 2026 @03:01PM (#50551346)
Sure, using a closed source proxy from a company nobody has ever heard of... That's a good idea...

Ferron seems much better, but I'm also not convinced that it's really production ready

Re:Pre-auth RCE in Nginx HTTP/2 handling by bakugo on Wednesday November 18, 2026 @03:05PM (#50551411)
This looks like someone prompted "rewrite nginx in rust, make no mistakes" in an afternoon and is now distributing it as a closed-source binary. Might as well just do it yourself.
Re:Pre-auth RCE in Nginx HTTP/2 handling by sippingabonedry on Wednesday November 18, 2026 @03:07PM (#50551432)
I'd hate to interrupt all the Rust fans sucking each other off again, but no one has yet mentioned the RCE relies on ASLR being disabled, which is basically non-existent nowadays. Another nothingburger CVE with a silly name and it's only Wednesday.
Re:Pre-auth RCE in Nginx HTTP/2 handling by nemothekid on Wednesday November 18, 2026 @03:08PM (#50551451)
xin seems to be closed source and ai generated. Before even worrying about exploits, how is someone supposed to ascertain that xin's implementation is correct? Sure Rust might not have any memory safety issues, but other logic vulnerabilities may exist. 'Claude make no mistakes?'

Caddy, Traefik, or even Envoy may be better choices.

Re:Pre-auth RCE in Nginx HTTP/2 handling by EGreg on Wednesday November 18, 2026 @03:16PM (#50551561)
If you're using NGINX to run your PHP applications, consider eliminating everything other than PHP itself:

https://news.ycombinator.com/item?id=50551504

Re:Pre-auth RCE in Nginx HTTP/2 handling by reducesuffering on Wednesday November 18, 2026 @03:18PM (#50551582)
Haven't you heard? These vulnerabilities are just AI marketing stunts. And also, the Bun rewrite to rust was a marketing stunt, those things don't work. There's no way Bun is running on Rust from a couple month AI powered rewrite, that would shatter my preconceived worldview about what the future looks like. /s
Re:Pre-auth RCE in Nginx HTTP/2 handling by terminalcommand on Wednesday November 18, 2026 @03:29PM (#50551703)
But rust is not a silver bullet. Rust compiler still has memory corruption bugs. Rust is only memory safe by design not by implementation. Borrow checker allows unsafe code without using unsafe keyword.
Re:Pre-auth RCE in Nginx HTTP/2 handling by empath75 on Wednesday November 18, 2026 @03:30PM (#50551728)
You can still die in a car accident while wearing a seatbelt, too.
Re:Pre-auth RCE in Nginx HTTP/2 handling by thayne on Wednesday November 18, 2026 @03:31PM (#50551732)
It isn't perfect. But it is still way better than c.
Re:Pre-auth RCE in Nginx HTTP/2 handling by slopinthebag on Wednesday November 18, 2026 @03:32PM (#50551751)
this is just a perfection fallacy. silver bullets don’t need to be perfect in every single way to be silver bullets. and rust is as much of one as anything.
Re:Pre-auth RCE in Nginx HTTP/2 handling by andersonpico on Wednesday November 18, 2026 @04:08PM (#50552139)
> Borrow checker allows unsafe code without using unsafe keyword.

is this just the continuation of the previous point (compiler/borrow checker can have bugs), a nod that you can import unsafe dependencies, or is there a soundness gap in rust that I'm not aware of?

Re:Pre-auth RCE in Nginx HTTP/2 handling by jpardoe on Thursday November 19, 2026 @12:50AM (#50556501)
No one is expecting a silver bullet. The absence of a silver bullet shouldn't prevent people moving towards better solutions.
Re:Pre-auth RCE in Nginx HTTP/2 handling by Klonoar on Wednesday November 18, 2026 @03:34PM (#50551774)
Who exactly are the people behind xin...?

The project isn't currently open source and there's next to nothing on the site to reassure you who's behind the server gateway you'd be running.

Googling the company in the footer produces this, but it also doesn't have much: https://www.signeen.com

Re:Pre-auth RCE in Nginx HTTP/2 handling by fullstop on Wednesday November 18, 2026 @03:35PM (#50551779)
xinproxy has a pretty restrictive license, but I'll give ferron.sh a closer look.
Re:Pre-auth RCE in Nginx HTTP/2 handling by TZubiri on Wednesday November 18, 2026 @06:03PM (#50553622)
It's a bit political to say that C is the fault here, I'd venture the radical position that this was an Nginx issue.
Re:Pre-auth RCE in Nginx HTTP/2 handling by nikcub on Wednesday November 18, 2026 @02:13PM (#50550689)
every major exploit now comes with a marketing website - nginx2root dot com in this case

the certificate for it was issued on the 2nd of November

if you were scanning CT logs you would have had a 16 day head start on RE'ing this

there are more examples in the current CT logs

https://api.certspotter.com/v1/issuances?domain=nginx2root.c...

Re:Pre-auth RCE in Nginx HTTP/2 handling by quesera on Wednesday November 18, 2026 @02:32PM (#50550945)
Someone registered ping2shell.com on Nov 9th, nine days ago.

ping2root.com is available though. :)

Re:Pre-auth RCE in Nginx HTTP/2 handling by badgersnake on Wednesday November 18, 2026 @02:39PM (#50551051)
And irresponsible disclosure but a bunch of attention seeking tossers
Re:Pre-auth RCE in Nginx HTTP/2 handling by pixl97 on Wednesday November 18, 2026 @05:38PM (#50553327)
Sitting on flaws is dead, the responsible disclosure people can get lost. AI finds and exploits flaws in hours. We also have little knowledge if the people finding the exploits have already intentionally or unintentionally leaked said exploits to AI providers.

If you want to promote responsible anything, go for responsible writing of software in the first place.

Re:Pre-auth RCE in Nginx HTTP/2 handling by frangonf on Wednesday November 18, 2026 @04:01PM (#50552080)
Security companies should buy all this $tech2root domains as a diverting measure first and also as a pretty safe investment, given current trends.
Re:Pre-auth RCE in Nginx HTTP/2 handling by nikcub on Wednesday November 18, 2026 @05:03PM (#50552852)
there's one that squatted on 30+ domains a few weeks ago that i saw
Re:Pre-auth RCE in Nginx HTTP/2 handling by aftbit on Wednesday November 18, 2026 @05:40PM (#50553367)
but what about $tech4shell.com tho?
Re:Pre-auth RCE in Nginx HTTP/2 handling by AtNightWeCode on Wednesday November 18, 2026 @07:53PM (#50554605)
I scan new domain names but for a different reason. There is an insane amount of nonsense domains registered everyday. Would be hard to tell just based on that.
Re:Pre-auth RCE in Nginx HTTP/2 handling by xr8 on Wednesday November 18, 2026 @02:18PM (#50550741)
Ops is not fun these days … used to pinned versions and an auditing approval process with SecDevOps … how are you mostly automate the process in a you build it you run it environment ?
Re:Pre-auth RCE in Nginx HTTP/2 handling by denvrede on Wednesday November 18, 2026 @02:38PM (#50551025)
Mandatory SBOM creation while building. Sending the SBOM into Dependency Track and then some automation flavors of your choice.
Re:Pre-auth RCE in Nginx HTTP/2 handling by jawiggins on Wednesday November 18, 2026 @02:37PM (#50551020)
Is this the reason why those banks were down the other day? Did they get advanced knowledge so they could patch their instances? Kind of questionable that the AI labs are creating a two-tiered system for system security if so.
Re:Pre-auth RCE in Nginx HTTP/2 handling by ppjim on Wednesday November 18, 2026 @03:05PM (#50551415)
[delayed]
Re:Pre-auth RCE in Nginx HTTP/2 handling by EGreg on Wednesday November 18, 2026 @03:08PM (#50551447)
If you are running a PHP site, you don't need an external webserver anymore, like Apache, NGINX or Caddy.

This webserver is not vulnerable to PHP2Shell nor this TLS issue, because it's completely userland PHP:

https://github.com/Qbix/webserver

It's now been battle-tested in production, and also supports websockets, etc.

(However, it doesn't support sendfile, because PHP doesn't have support for that, so it's not as fast as nginx for sending static files. This shouldn't make a difference, though, if you use a CDN in front.)

Re:Pre-auth RCE in Nginx HTTP/2 handling by dmonterocrespo on Wednesday November 18, 2026 @03:08PM (#50551460)
[delayed]
Re:Pre-auth RCE in Nginx HTTP/2 handling by brisky on Wednesday November 18, 2026 @03:12PM (#50551513)
Reading news like this makes me remember the ship hacking scene from GITS Innocence. In the end there will be AI attacking vs AI defending. Humans will be too slow to participate. Defender AIs should be coming soon - maybe some sort of proactive memory and usage anomaly pattern monitoring AI systems?
Re:Pre-auth RCE in Nginx HTTP/2 handling by j45 on Wednesday November 18, 2026 @03:14PM (#50551536)
My firewall needs a firewall
Re:Pre-auth RCE in Nginx HTTP/2 handling by iqbal1980 on Wednesday November 18, 2026 @03:30PM (#50551712)
Thank you! I had to patch bunch of products I'm working on.
Re:Pre-auth RCE in Nginx HTTP/2 handling by iqbal1980 on Wednesday November 18, 2026 @03:30PM (#50551718)
Was this discovered using an AI?
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.

Re:Pre-auth RCE in Nginx HTTP/2 handling by sourcecodeplz on Wednesday November 18, 2026 @03:33PM (#50551755)
the new "hack" now is to monitor wide-spread repos for critical PRs
Re:Pre-auth RCE in Nginx HTTP/2 handling by TuckerBMorgan on Wednesday November 18, 2026 @03:37PM (#50551800)
I wonder when all of this die down. I assume at some tipping point most software will be written/patched with LLMs and so hopefully (fingers crossed) more resistent to these bugs.

Certainly a stressful time for sysadmins everywhere, let us hope your coworkers are picking up your beer tab

Re:Pre-auth RCE in Nginx HTTP/2 handling by talon8635 on Wednesday November 18, 2026 @03:44PM (#50551883)
But are LLM patches exhaustive? Cant a new model find even more obscure bugs, including bugs introduced by the old LLM patch? Is it really realistic that we such complex projects as some of these critical dependencies are can be truly 100% bug free?
Re:Pre-auth RCE in Nginx HTTP/2 handling by TuckerBMorgan on Wednesday November 18, 2026 @03:51PM (#50551964)
We dont need to be bug free, so much as the juice needs to be not worth squeeze. I think i am also making an assumption that we "level" in terms of frontier model progress at some point, and we have months or years between upgrades.
Re:Pre-auth RCE in Nginx HTTP/2 handling by tclancy on Wednesday November 18, 2026 @04:09PM (#50552144)
>so much as the juice needs to be not worth squeeze

I wonder about that though: if the price of the squeeze collapses to 0 because of this (think of what models and prices might be like a year from now), I think I know where all those out of work mathematicians can find gigs. We are going to need to invent a layer on top of, an evolution of or some new concept a level above "computer programming" that deals with meta-organization of code.

Re:Pre-auth RCE in Nginx HTTP/2 handling by Aachen on Wednesday November 18, 2026 @05:57PM (#50553552)
If the software is too complex to understand, maybe it should be made simpler. Nginx does a million things currently but what most people need is something that parses http1 strings and sends back a file or calls a second program based on the path. Every component can be thought of in this way, with the most complexity perhaps in being sure the interfaces don't do something unexpected
Re:Pre-auth RCE in Nginx HTTP/2 handling by tripleee on Wednesday November 18, 2026 @04:02PM (#50552085)
It's possible that AI is going to be better at finding and exploiting systems than at securing them. It's not really an even playing field. On the one hand you have to somehow ensure that you've patched everything when there's no definite list of everything, the other side just needs to find one overlooked way in.

At the rate of development, also, will AI developed in 6 months from now be able to break a system that was secured by todays AI?

Re:Pre-auth RCE in Nginx HTTP/2 handling by jtmarmon on Wednesday November 18, 2026 @04:25PM (#50552326)
It's not possible. It generally requires more work to find an exploit than to patch the (known) exploit.

Now, you could argue that writing secure code ex-ante is harder than discovering an exploit. But you can hypothetically run the same "exploit finding" process on a first pass of code before it ships (e.g on the PR) given low enough token costs, which is where we're headed.

Re:Pre-auth RCE in Nginx HTTP/2 handling by tripleee on Wednesday November 18, 2026 @04:29PM (#50552377)
How do you know when the "exploit finding" pass is done? A hacker group would happily burn a month or more of tokens trying to break a critical piece of software.
Re:Pre-auth RCE in Nginx HTTP/2 handling by HappyDreamer on Wednesday November 18, 2026 @04:47PM (#50552622)
> It generally requires more work to find an exploit than to patch the (known) exploit.

Not sure if that's true, but in any case, you seem to forget:

When the hackers have breached something, awaits a reward.

E.g. a Bitcoin wallet, or learning something about a political competitor and getting rid of them.

(So the hackers can spend lots of ...)

Re:Pre-auth RCE in Nginx HTTP/2 handling by snowwrestler on Wednesday November 18, 2026 @11:06PM (#50555954)
The better LLMs get at finding vulnerabilities, the more obvious it will be to bolt them into software development processes to find the bugs prior to release.

With enterprise frontier LLM models, there is no longer an “other side.” Everyone is just using what they can rent from a few big suppliers. You can too.

Re:Pre-auth RCE in Nginx HTTP/2 handling by mglvsky on Wednesday November 18, 2026 @04:37PM (#50552472)
but at least sysadmins/ops still have work to do
Re:Pre-auth RCE in Nginx HTTP/2 handling by malikNF on Wednesday November 18, 2026 @03:42PM (#50551857)
Hey so, does anyone know of a good tutorial on getting in to woodwork?
Re:Pre-auth RCE in Nginx HTTP/2 handling by hi41 on Wednesday November 18, 2026 @03:51PM (#50551955)
I felt your post was off topic. But maybe it was on purpose because we are getting bored of so many vulnerabilities being discovered by AI security tools. So your post is important because of that.

I see a lot of interest in woodworking on HN. Is that because Jesus was a carpenter and HN folks are interested in woodwork because of the larger context and history shaped by Christianity? What is your motivation for woodwork? Is that because we see a concrete finished project instead of vague intellectual stuff which has no seeable boundaries?

Re:Pre-auth RCE in Nginx HTTP/2 handling by Lambdanaut on Wednesday November 18, 2026 @03:57PM (#50552039)
This is a beautifully autistic comment.
Re:Pre-auth RCE in Nginx HTTP/2 handling by senordevnyc on Wednesday November 18, 2026 @04:03PM (#50552095)
Botistic more like it
Re:Pre-auth RCE in Nginx HTTP/2 handling by InsideOutSanta on Wednesday November 18, 2026 @04:24PM (#50552310)
I think most LLMs would have gotten that woodworking joke.
Re:Pre-auth RCE in Nginx HTTP/2 handling by mettamage on Wednesday November 18, 2026 @04:31PM (#50552395)
Just take a second to check out the account if you're going to say stuff like this. It's not just you either, so this goes for everyone making these comments.

The account is from 2017. There are enough comments before LLMs were a thing. Given his karma score, unlikely to be a bot.

Some people really don't get these type of things.

Re:Pre-auth RCE in Nginx HTTP/2 handling by hi41 on Wednesday November 18, 2026 @04:36PM (#50552452)
Well, I am usually the person in the room who does not get a joke. I am so scared of get-togethers that I actively try to avoid it. Also, they ask me to dance. I am terrible at that. I am not autistic but don’t get the drift of many jokes. I am human and not a bot. Guess that’s what a bot would say. But still I am human.
Re:Pre-auth RCE in Nginx HTTP/2 handling by tudorconstantin on Wednesday November 18, 2026 @10:12PM (#50555583)
I didn’t get the joke myself either, so thanks for asking. I first thought “woodworking” was used as a synonym for hacking and clicked on the links with the book recommendations just to see they’re about actual woodworking.

Not sure why others downvoted you, but you have my upvote on it.

Re:Pre-auth RCE in Nginx HTTP/2 handling by jkingsman on Wednesday November 18, 2026 @04:02PM (#50552086)
Becoming a carpenter,sentiments of "I'm going to live in the forest," or "I'm going to be a farmer" are usually expressions of fatigue with technology, and a desire to be free of their problems; thus, an expressed desire to pursue a career where technology is not a major component. It can also sometimes carry a desire to have one's labor output be tangible and physical (i.e. a worked wood object) rather than abstract, as so much programming/operations/etc. work often is.

The comment you replied to is shortcutting the joke, assuming the common riff of becoming a carpenter is well known, and jumping ahead to asking about tutorials for woodworking as part of that process.

Re:Pre-auth RCE in Nginx HTTP/2 handling by electric_mayhem on Wednesday November 18, 2026 @04:19PM (#50552249)
Piffle.

Preposterous, even.

That said, my RHCE CISSP self is going to go outside and spend some time with my flock of chickens and guinea fowl.

While Claude writes Ansible to update the fleet to use nginx's deb repo.

Re:Pre-auth RCE in Nginx HTTP/2 handling by devsda on Wednesday November 18, 2026 @10:18PM (#50555619)
Haha. The image of shouting voice instructions to Claude while trying to herd a flock of chickens to their coop is the dream, very tony stark'esque only with chickens!
Re:Pre-auth RCE in Nginx HTTP/2 handling by hising on Wednesday November 18, 2026 @04:29PM (#50552374)
This feels like an AI bot reply
Re:Pre-auth RCE in Nginx HTTP/2 handling by jareklupinski on Wednesday November 18, 2026 @04:35PM (#50552440)
wood, unlike logic and machine, is firm, yet yielding
Re:Pre-auth RCE in Nginx HTTP/2 handling by HoldOnAMinute on Wednesday November 18, 2026 @05:35PM (#50553296)
As programmers, we do see ourselves as Jesus, yes.
Re:Pre-auth RCE in Nginx HTTP/2 handling by bsoles on Wednesday November 18, 2026 @04:03PM (#50552097)
[delayed]
Re:Pre-auth RCE in Nginx HTTP/2 handling by djeastm on Wednesday November 18, 2026 @05:00PM (#50552807)
I took a quick look at The Anarchist's Tool Chest and noticed in Chapter 20 a short vignette about an expert woodworker named Troy that seemed... oddly familiar.

According to the author, Troy could do the work of three people. That would make him a 3x woodworker, I guess. And he was facing automation in the woodworking industry.

"But Troy decided to compete with the machines on their own turf. He tried to become a one-man factory. He succeeded in that. But the most efficient one-man factory cannot compete with a factory driven by a hundred men.

So no matter what Troy did, the prices for work (good or otherwise) declined. Ikea’s well-designed kitchens and Value City’s cheap junk made it impossible to survive and live well.

So Troy struggled with his business. And that’s nuts. He should have had more business than he could handle. But like many professional cabinetmakers I know, it became harder and harder for him to make ends meet every year. His cabinetmaking business is closed, and the last time we talked, Troy was working for his wife’s successful tax business.

Who is to blame for this? We are.

We have become a culture that is obsessed with price more than any other attribute of the things we buy. It doesn’t matter if the item is ugly, poorly made or constructed of materials that cannot be recycled. All that matters is if the price is low enough.

Because the price of our household objects has hit rock bottom, if an item breaks or starts to look dated, we can throw it away and buy some- thing else. For the first time in human history, manufactured furniture is shockingly inexpensive.

So it’s no wonder that artisans are exiting the craft. It’s difficult to compete against furniture that costs less than what you pay for your raw materials.

Lesson: People cannot imitate machines and defeat them."

Re:Pre-auth RCE in Nginx HTTP/2 handling by boc on Wednesday November 18, 2026 @05:17PM (#50553046)
The lesson is that most people aren't discerning consumers in multiple fields.

Appreciating good design, quality craftsmanship, having taste in food.. having these "elevated" tastes in multiple areas is very rare for humans. Take a look at a musician - they can tell you precisely what makes a quality violin, but they might not care that they eat microwave frozen dinners. You compound that across the population and the artisans will always lose out to the mass-produced slop because it's impossible to naturally get a critical mass of people to care about that quality curve. You have to sell them on it.

Troy struggled because he failed at marketing, not production.

Re:Pre-auth RCE in Nginx HTTP/2 handling by throwforfeds on Wednesday November 18, 2026 @06:48PM (#50554003)
Or even single fields. I've purchased my parents the "nicer" version of things and they inevitably end up back on some crappier version. Japanese knives? Nope, still use the ones that barely cut. Ubiquiti wifi system that covered their whole house? Nope, dad unplugged something, got frustrated, and the cable company came over and put them back on the old crappy system. Nice speakers? Nope, they listen to music on their crappy TV speakers.

I think I've learned that most people don't want to put in any effort to learn or appreciate things that may be of nicer quality. Those Japanese knives didn't do any good for them because they didn't spend time learning how to use them properly. In fact one of them used them improperly and ended up needing stitches. So in the end the crappier version is no different than the nicer version, because crappy and nice are about the potential of the item, and most people don't see potential. Does this Ikea dresser hold clothes? Great, who cares that the other one is of nicer wood, the joinery is done by hand, and it'll last multiple generations.

Re:Pre-auth RCE in Nginx HTTP/2 handling by bordercases on Wednesday November 18, 2026 @08:19PM (#50554830)
[delayed]
Re:Pre-auth RCE in Nginx HTTP/2 handling by drewbeck on Wednesday November 18, 2026 @06:38PM (#50553914)
Re:Pre-auth RCE in Nginx HTTP/2 handling by red75prime on Wednesday November 18, 2026 @09:29PM (#50555322)
50% are lower than median. I feel the need to join police forces.
Re:Pre-auth RCE in Nginx HTTP/2 handling by tclancy on Wednesday November 18, 2026 @04:05PM (#50552103)
Ha, sadly there's a huge long line of developers who pivoted this way already. Plus now that you can fire up an MCP for a CnC machine, that art will be "ruined" too!
Re:Pre-auth RCE in Nginx HTTP/2 handling by baq on Wednesday November 18, 2026 @04:19PM (#50552255)
I hear electrician and plumbing schools are overflowing with newly enrolled students, too
Re:Pre-auth RCE in Nginx HTTP/2 handling by tclancy on Wednesday November 18, 2026 @05:42PM (#50553398)
I would be suspicious of any plumbing school that is overflowing.
Re:Pre-auth RCE in Nginx HTTP/2 handling by xyproto on Wednesday November 18, 2026 @03:56PM (#50552027)
Most web servers are undergoing a security tsunami right now. It's important to switch to the ones that are on the fixed side of the tsunami, IMO.
Re:Pre-auth RCE in Nginx HTTP/2 handling by hackthemack on Wednesday November 18, 2026 @04:01PM (#50552069)
I notice a phenomena that when older software has a critical vulnerability, like say Apache, you get quite a few comments of "Why does anyone use that? Use Nginx"

But when newer software has the same vulnerability, you do not see the same kind of comments.

There always seems to be a latent stance in IT that newer is better.

Re:Pre-auth RCE in Nginx HTTP/2 handling by tredre3 on Wednesday November 18, 2026 @04:31PM (#50552385)
> But when newer software has the same vulnerability, you do not see the same kind of comments.

This isn't true! Just look at this thread, people suggest replacing nginx with newer but less widely used and less battle-tested software, as if they're superior alternatives or don't have RCEs in their own history: Envoy, caddy, traeffik, Qbix.

Re:Pre-auth RCE in Nginx HTTP/2 handling by jeroenhd on Wednesday November 18, 2026 @06:04PM (#50553628)
I can't speak for the others, but one advantage Caddy has over Nginx is that it isn't written in C.

Go isn't quite a memory safe language, but it provides fewer footguns.

On the other hand, Caddy has a lot more features, so there's more code that can contain exploits.

Re:Pre-auth RCE in Nginx HTTP/2 handling by chlorion on Wednesday November 18, 2026 @06:50PM (#50554020)
Having RCEs in general is fine. It's the rate and severity that matter.

We have evidence that large unsafe codebases suffer from more and more severe CVEs than those who are not in memory unsafe languages.

In other fields of engineering, people use stats and actually measure things like this, and use the results to determine what to do. They don't just assume something is better because its "battle tested" (whatever that even means?).

Re:Pre-auth RCE in Nginx HTTP/2 handling by cozzyd on Wednesday November 18, 2026 @08:58PM (#50555136)
I haven't even heard of any of those other than caddy...
Re:Pre-auth RCE in Nginx HTTP/2 handling by redox99 on Wednesday November 18, 2026 @04:35PM (#50552439)
I'm actually moving from nginx to Caddy after this. I'll replace all C/C++ stuff within reason.
Re:Pre-auth RCE in Nginx HTTP/2 handling by zug_zug on Wednesday November 18, 2026 @05:08PM (#50552914)
Me too. An agent was able to replace my nginx with caddy on my webserver in a few minutes.

All the remaining C code needs to die in a matter of months not years.

Re:Pre-auth RCE in Nginx HTTP/2 handling by SpaceManNabs on Wednesday November 18, 2026 @06:06PM (#50553646)
> All the remaining C code needs to die in a matter of months not years.

Why so? are most of these vulnerabilities from C's memory model?

Re:Pre-auth RCE in Nginx HTTP/2 handling by redox99 on Wednesday November 18, 2026 @06:09PM (#50553667)
Yes
Re:Pre-auth RCE in Nginx HTTP/2 handling by dtf on Wednesday November 18, 2026 @05:22PM (#50553120)
I do love Caddy. But it was vulnerable to CVE-2026-98432 a few weeks back, due to Go's MPTCP policy.
Re:Pre-auth RCE in Nginx HTTP/2 handling by jeroenhd on Wednesday November 18, 2026 @06:06PM (#50553648)
CVE-2026-98432 also applies to non-MPTCP connections. That's why disabling MPTCP was actively discouraged as a workaround (low level firewalls that clear all options do work, though, and they'd also work fine with Caddy).

Plus, Caddy itself wasn't vulnerable in this specific case. There wasn't much the Caddy folks could've done to protect against a problem in the Linux kernel itself.

Re:Pre-auth RCE in Nginx HTTP/2 handling by waterTanuki on Wednesday November 18, 2026 @08:37PM (#50554991)
surprised there hasn't been an effort to rewrite nginx or other critical networking infrastructure in Rust. We just went straight from C (nginx) to Go (Caddy/Traefik) which are not interchangeable (garbage collection).
Re:Pre-auth RCE in Nginx HTTP/2 handling by karel-3d on Wednesday November 18, 2026 @05:31PM (#50553253)
Just use Pingora. It's in Rust and from Cloudflare so it is safe. (/s but not really I guess)
Re:Pre-auth RCE in Nginx HTTP/2 handling by mbrubeck on Wednesday November 18, 2026 @06:04PM (#50553632)
Doesn't nginx count as "older software" at this point? It's over twenty years old...
Re:Pre-auth RCE in Nginx HTTP/2 handling by levkk on Wednesday November 18, 2026 @04:02PM (#50552090)
Pretty funny times. AI is making it faster to both write insecure code and to detect buffer overflows. Sell both the problem and the solution. Genius.

It'll take a few years for the market to adjust. If nothing else, businesses are good at figuring out ROIs, eventually.

Re:Pre-auth RCE in Nginx HTTP/2 handling by Culonavirus on Wednesday November 18, 2026 @04:25PM (#50552325)
> Complexity can no longer be relied upon as a barrier to discovery or exploitation.

I mean sure if we close our eyes and ears we can ignore the elephant in the room that is proprietary, closed source software.

Re:Pre-auth RCE in Nginx HTTP/2 handling by dirkc on Wednesday November 18, 2026 @04:27PM (#50552354)
Just what I needed on a Wednesday evening after promising myself I'll go to bed before 10. Oh well, thanks for the disclosure.
Re:Pre-auth RCE in Nginx HTTP/2 handling by unsloppable on Wednesday November 18, 2026 @04:30PM (#50552382)
Is it time to vibe code my whole stack so I'm secure through obscurity?

Only half joking.

Re:Pre-auth RCE in Nginx HTTP/2 handling by Buttons840 on Wednesday November 18, 2026 @04:31PM (#50552399)
Everyone's worried about security right now, even non-tech people, but hasn't half the nation's personal data been leaked twice a month for the last decade or two?

I know times are changing, it's just curious that nobody seemed to care until now.

Re:Pre-auth RCE in Nginx HTTP/2 handling by mportela on Wednesday November 18, 2026 @04:37PM (#50552466)
I think all airplanes in the entire country being grounded, banks not able to process transfers, or grocery store freezers being disabled hit differently than data leaking…
Re:Pre-auth RCE in Nginx HTTP/2 handling by vinyl7 on Wednesday November 18, 2026 @05:06PM (#50552879)
None of those were due to vulnerabilities
Re:Pre-auth RCE in Nginx HTTP/2 handling by pixl97 on Wednesday November 18, 2026 @05:22PM (#50553112)
I disagree. They may not be because of exploited vulns, but the rate updates and patches are happening there is a very long tail of instability after patching due to extremely fast turn arounds.
Re:Pre-auth RCE in Nginx HTTP/2 handling by aftbit on Wednesday November 18, 2026 @05:39PM (#50553352)
I'm not sure yet, but my guess is that the FAA grounding was not really related to vuln patches. I thought there was a copper to fiber network upgrade gone wrong involved there. It seems like the bigger problem is aging infra that needs replacement.
Re:Pre-auth RCE in Nginx HTTP/2 handling by aftbit on Wednesday November 18, 2026 @05:38PM (#50553332)
The freezers were, at least to some extent. One could argue that they should never have been on the internet and so the vulns wouldn't matter ... but a hidden, insecure admin password based only on a static key and today's date is definitely a vuln in my opinion.
Re:Pre-auth RCE in Nginx HTTP/2 handling by trvrprkr on Wednesday November 18, 2026 @04:40PM (#50552501)
Yes. That’s the confidentiality part of the CIA triad. But now you have a whole lot of things suddenly impacting availability in really visible ways, so yes, a whole different cross-section of people are really perking up.
Re:Pre-auth RCE in Nginx HTTP/2 handling by perrygeo on Wednesday November 18, 2026 @04:36PM (#50552454)
I was talking with someone about buffer overflows due to HTTP requests this morning. I think I said something like "but we don't need to worry about that, just put nginx in front of it." Sigh. Off to update some VMs. Again.
Re:Pre-auth RCE in Nginx HTTP/2 handling by 1vuio0pswjnm7 on Wednesday November 18, 2026 @05:00PM (#50552805)
"Both vulnerabilities are memory-safety issues in how NGINX handles HTTP/2 traffic."

HTTP/2 again. First Apache, now NGINX

I rarely use HTTP/2, I rarely use a popular web browser, I use a TLS forward proxy that has HTTP/2 support but I prefer HTTP/1.1

I find that 1.1 is faster for the way I use the www (text-only, no images, CSS, Javascript, cookies, advertising, tracking), plus the 1.1 protocol comes from academia not Google, Akamai, etc.

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.
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.

Re:Pre-auth RCE in Nginx HTTP/2 handling by beaviskhan on Wednesday November 18, 2026 @05:35PM (#50553294)
If you use Cloudflare to proxy traffic, you can disable HTTP/2 quickly and easily: https://developers.cloudflare.com/speed/optimization/protoco...
Re:Pre-auth RCE in Nginx HTTP/2 handling by throooooo on Wednesday November 18, 2026 @05:38PM (#50553335)
If Cloudflare is in front of an origin I'd expect that they absorb or block this attack in the first place.
Re:Pre-auth RCE in Nginx HTTP/2 handling by beaviskhan on Wednesday November 18, 2026 @05:46PM (#50553441)
Re:Pre-auth RCE in Nginx HTTP/2 handling by swozey on Wednesday November 18, 2026 @05:36PM (#50553310)
Please know the implications of this it's a much bigger thing to do than usually deserves a quick on off switch
Re:Pre-auth RCE in Nginx HTTP/2 handling by beaviskhan on Wednesday November 18, 2026 @05:42PM (#50553401)
Yeah, if it matters for your workload, then don't do this :) And obviously test outside of production first if you're doing anything important. But if all is happy with http/1.1 then this is likely much easier than making a config change or waiting for a patch that doesn't seem to exist yet for some downstream consumers of nginx (like apisix for example).
Re:Pre-auth RCE in Nginx HTTP/2 handling by Aachen on Wednesday November 18, 2026 @05:52PM (#50553509)
You mean moving your site behind the great internet firewall or turning off a second http implementation?
Re:Pre-auth RCE in Nginx HTTP/2 handling by brynet on Wednesday November 18, 2026 @05:36PM (#50553303)
Nginx used to be in the OpenBSD base system between 2012-2015.

12 years on, OpenBSD's port of nginx still maintains its default chroot(2) patch.

https://raw.githubusercontent.com/rnagy/nginx_chroot_patch/m...

Re:Pre-auth RCE in Nginx HTTP/2 handling by karel-3d on Wednesday November 18, 2026 @05:38PM (#50553325)
Re:Pre-auth RCE in Nginx HTTP/2 handling by BSTRhino on Wednesday November 18, 2026 @05:42PM (#50553404)
I saw this and realised I'm running nginx in a docker container, very easy update, no waiting for the distro to make the update available
Re:Pre-auth RCE in Nginx HTTP/2 handling by xmddmx on Wednesday November 18, 2026 @06:17PM (#50553741)
I'm self-hosting Discourse forum software which runs in a Docker container, but it sounds like I can't just easily update myself ? See https://meta.discourse.org/t/nginx2root-http2-is-on-by-defau...
Re:Pre-auth RCE in Nginx HTTP/2 handling by BSTRhino on Wednesday November 18, 2026 @06:26PM (#50553800)
Oh no, how annoying, yes I can see how that could be the case if Discourse is running its own copy of nginx with its own configuration inside its container. That's unfortunate - I don't know much about Discourse but I hope that had a good reason to bundle in nginx, seems unnecessary at first glance. I really hope a Discourse developer gets to the issue soon and releases an update, that would be the fastest and easiest way!

I am running the official nginx docker image by itself in front of all my services, which are their own docker images. So it's easy for me to update just one of them. This works for me because I want my dedicated server to run all my projects with nginx in front. If I were running Discourse I would want it to not bundle nginx because I've already got one of my own. So that's interesting that they do that.

Re:Pre-auth RCE in Nginx HTTP/2 handling by aftbit on Wednesday November 18, 2026 @05:43PM (#50553406)
Hardly anyone talking about the Linux SCTP bug that they used to LPE out of the container. Apparently that's a zero-day without a public CVE number yet? Presumably they're coordinating with the kernel team and distros to get it patched first. Of course, one might just assume that there are a bazillion LPEs available to even a properly confined rootless container, but ... yuck.
Re:Pre-auth RCE in Nginx HTTP/2 handling by wmf on Wednesday November 18, 2026 @06:31PM (#50553851)
SCTP should be disabled in every distro.
Re:Pre-auth RCE in Nginx HTTP/2 handling by Bender on Wednesday November 18, 2026 @06:48PM (#50553999)
Sadly it is not but one can disable it easily enough.

    echo 'install sctp /bin/false' > /etc/modprobe.d/no-sctp.conf
    echo 'install dccp /bin/false' > /etc/modprobe.d/no-dccp.conf
    echo 'install rds /bin/false' > /etc/modprobe.d/no-rds.conf
Re:Pre-auth RCE in Nginx HTTP/2 handling by thenewnewguy on Wednesday November 18, 2026 @07:04PM (#50554135)
Is there some context to this, I don't see a mention of SCTP in the blog post? Maybe edited out?
Re:Pre-auth RCE in Nginx HTTP/2 handling by aftbit on Wednesday November 18, 2026 @11:43PM (#50556159)
Re:Pre-auth RCE in Nginx HTTP/2 handling by jon128 on Wednesday November 18, 2026 @05:53PM (#50553517)
nginx is so pervasive, these CVEs are serious.
Re:Pre-auth RCE in Nginx HTTP/2 handling by fvrshaibu on Wednesday November 18, 2026 @07:18PM (#50554266)
its crazy how exploits are being discovered in software nowadays, especially using AI
Re:Pre-auth RCE in Nginx HTTP/2 handling by george_max on Wednesday November 18, 2026 @07:23PM (#50554317)
FYI, you need to send around 128GB of data for this bug to work.
Re:Pre-auth RCE in Nginx HTTP/2 handling by AtNightWeCode on Wednesday November 18, 2026 @07:48PM (#50554555)
Maybe you should not run in production a Russian reverse proxy slash web server commercialized by F5 written in C to begin with...
Re:Pre-auth RCE in Nginx HTTP/2 handling by testtestmetest on Wednesday November 18, 2026 @08:27PM (#50554914)
You need 128Gb of http/2 traffic and specific cpu instructions to get this to work.

https://x.com/Laughing_Mantis/status/2123146699396858260

Its a non issue, but people just want to be told AI is God or something and the world is ending.

Its a non issue.

Re:Pre-auth RCE in Nginx HTTP/2 handling by zackwu on Wednesday November 18, 2026 @08:58PM (#50555142)
what do you mean it's a non issue? Surely no one is going to take the trouble to take down my toy website, but if there's something valuable enough, a motivated actor can/will try to exploit
Re:Pre-auth RCE in Nginx HTTP/2 handling by codedokode on Wednesday November 18, 2026 @09:43PM (#50555418)
At 1 Gbit/s (typical datacenter connection) how much time does it take to transmit 128 Gb of traffic?
Re:Pre-auth RCE in Nginx HTTP/2 handling by dathery on Wednesday November 18, 2026 @10:09PM (#50555568)
There are two bugs here; CVE-2026-123633 does not require a large amount of data or AVX-512.
Re:Pre-auth RCE in Nginx HTTP/2 handling by nojs on Wednesday November 18, 2026 @08:32PM (#50554951)
"Check if our site is vulnerable to the latest nginx security advisory"

> Error: API Error: Opus 5.5's safeguards flagged this session

Literally the first message, lol.

Re:Pre-auth RCE in Nginx HTTP/2 handling by red75prime on Wednesday November 18, 2026 @09:59PM (#50555516)
All those conversations 10 years ago when I was a bit into rust evangelism... "Memory unsafety is not a problem because my code don't have such errors." Those specific people might be correct, of course.
Re:Pre-auth RCE in Nginx HTTP/2 handling by userbinator on Wednesday November 18, 2026 @10:44PM (#50555821)
HTTP/2 again, not surprisingly. The curse of complexity strikes again. When I first saw the spec, I knew it would be far more difficult to implement correctly than 1.1 or 1.0. While 1.x is not ideal either (parsing a protocol that involves free-form text with no fixed limits is always a bit scary), at least it has a much smaller attack surface.

On the bright side, perhaps "security review" of code which involves throwing it at an AI and fixing what it finds before releasing will become a normal practice.

"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies." - C.A.R. Hoare

Re:Pre-auth RCE in Nginx HTTP/2 handling by sarreph on Wednesday November 18, 2026 @11:34PM (#50556123)
I wonder how much of this exploitation will push the industry towards closed-source. Previously the advantage of OSS was trust and collaborative improvement, but that is getting eroded quite heavily now by the barrage of attacks and insidious discovery.

The first step was closing contributions down to known contributors and maintainers. Maybe there’ll be a similar step where only a select group will be able to access — and attest to — the code?