News for hackers. Stuff that matters.
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 Pokepokalypse on Thursday November 19, 2026 @01:22AM (#50556686)
Imagine how those of us running a commercial OS feel. . . (Mac OS, Windows)
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 Pokepokalypse on Thursday November 19, 2026 @01:21AM (#50556673)
Honestly, yes. I'm shining so bright right now, I gotta wear shades. The burnout will be absolutely spectacular. And no one will notice with the rest of us all dropping like flies at the same time.

My guess is that this phenomenon is going to be reflected in what we're seeing right now: a wide pattern of unintended outages from rapid unplanned emergency remediation operations. Which I'm guessing is a lot of people's job description over the past 3 months or so. (really, since March, for me, with that Trivy hack).