MIDREAL
Menu

Unauthenticated remote code execution in Nginx

https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities (wiz.io)

1505 points | 3d ago | Discuss on Hacker News | Back to Radar

Comments

leca 3d ago on HN
How many hours before this is exploited in the wild ? Probably not all that long, that blog has a significant amount of details.
lwarfield 3d ago on HN
One tops
LeonM 3d ago on HN
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

superkuh 3d ago on HN
It seems like it always HTTP/2 (except when it's regex) with nginx. Glad I'm http/1.1 only.
citrin_ru 3d ago on HN
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

sebiw 3d ago on HN
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?

Edit: All good. They released the new versions within 30 mins.

GrayShade 3d ago on HN
They're out now.
mjhagen 3d ago on HN
Upstream fixes are available in 1.30.7 stable and 1.31.9 mainline.
CER10TY 3d ago on HN
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.

ferngodfather 3d ago on HN
> 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.

derhuerst 3d ago on HN
Currently, the Ubuntu [1] & Debian [2] packages seem unpatched.

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

ROllerozxa 3d ago on HN
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?
mdbug 3d ago on HN
Everyone called me crazy for running Arch on my servers btw
ranger_danger 3d ago on HN
> Why disclose this level of detail when the patches are not ready yet?

Perhaps it was already being exploited?

Aachen 3d ago on HN
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"
johnbellone 3d ago on HN
The beatings will continue until morale improves.
lostmsu 3d ago on HN
All system critical software must be rewritten in memory-safe languages before the end of the year.
mxuribe 3d ago on HN
Wow, that sounds eerily like leadership at my $dayjob! :-D lol Or, maybe that is default way of thinking for many leaders nowadays!?! :-(
Twirrim 3d ago on HN
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.

Retr0id 3d ago on HN
> Wiz Research, Ikotas Labs, Metnir, Rapid7, and Xint independently uncovered

Is this some kind of record for bug collision?

MeetingsBrowser 3d ago on HN
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?

cozzyd 3d ago on HN
or maybe the model leaked the exploit from one to the other...
mxuribe 3d ago on HN
So, do you mean that the relevant model(s) keeps disclosing these reports in an effort to create urgency and velocity across the industry, such that, us humans will throw our collective hands up in resignation, and decide to hand over all this "security" stuff over to the AI? No, no, that sounds just too crazy! /s
cozzyd 3d ago on HN
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.
hooch 3d ago on HN
This was one of the takeaways from Greg Kroah-Hartman‘s recent Linux in the land of LLM keynote.
rcxdude 3d ago on HN
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.
vel0city 3d ago on HN
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.
pjungwir 3d ago on HN
That seems likely, but maybe it was being actively exploited so several people started investigating.
WarmWash 3d ago on HN
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.

ryanschaefer 3d ago on HN
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)

rustyhancock 3d ago on HN
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).

serf 3d ago on HN
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."

antonvs 3d ago on HN
> It's never clear quite where you are in the technologically cycle.

The problem is that everyone is at a different place in the cycle. As Gibson put it, "The future is already here - it's just not evenly distributed."

baobabKoodaa 3d ago on HN
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"?
ryanschaefer 3d ago on HN
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.

pbronez 3d ago on HN
Cost scales with the size of your search space. Smarter questions get answers for less money & time.
pixl97 3d ago on HN
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.
Cthulhu_ 2d ago on HN
Personally I think it's a good thing - many vulnerabilities are being found and fixed now, people are wide awake and paying attention to them being found so updating is quicker and easier, and since code is finite, so are vulnerabilities so in, say, a year or so there's going to be the status quo of LLM vulnerability scanners run by dozens of companies running 24/7 on every software ever... unable to find anything.

So yeah it sucks right now, there's outages, probable PII theft left right and center (but that's nothing new at this point), millions / billions in damages and lost productivity from Office365 and co being offline for a day or two... but it's still manageable, the world isn't on fire, and it's better to get all that out of the way now than in an actual crisis.

afavour 3d ago on HN
When everyone is using the same tools for the same purpose...
ROllerozxa 3d ago on HN
Well I guess this was the vuln that was teased about on Mastodon some hours ago:

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

hosteur 3d ago on HN
So work around is to disable http/2 and only allow http/1.1?
Simber 3d ago on HN
Yep, that or update to 1.31.9+ or 1.30.7+ if they are available in your distro
kijin 3d ago on HN
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 reading HN today.
baggy_trough 3d ago on HN
There isn't even a mail about this on oss-security, as of now.
cm2187 3d ago on HN
Unless I am confused, it doesn't look like ubuntu server has made available the fix.
dannyw 3d ago on HN
It’s time to switch away from Ubuntu and go upstream to Debian.
MrDOS 3d ago on HN
While I wholeheartedly agree with you, Debian hasn't patched yet, either. See my sibling comment: https://news.ycombinator.com/item?id=50551026.
karel-3d 3d ago on HN
Lol no

Debian is unfixed too

MrDOS 3d ago on HN
lousken 3d ago on HN
pier25 3d ago on HN
Amazing that they don't disclose these CVEs to the major Linux distros before going public
imhoguy 3d ago on HN
Who is sane enough in 2026 to expose distro default services to the Internet?

I wouldn't expect any distro maintainers to react in hours. Distros are too complex to dump updates in rush.

Start to use Docker/Podman/systemd-nspawn.. and isolate public services to necessary needs (static binaries, drop capabilities, default drop rule firewall between containers, r/o storage, access logs bind mounted as rw file, memory temp dir with noexec). Container images are patched the quickest.

dboreham 3d ago on HN
The AI gods say that http/2 is disabled in a default installation fwiw.
antiloper 3d ago on HN
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?
layer8 3d ago on HN
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.
redox99 3d ago on HN
Yeah and park is the default gear in cars...
yread 3d ago on HN
My Apaches still have http2 disabled from the last cve, now its njinx time
kijin 3d ago on HN
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.)

K0nserv 3d ago on HN
Just another set of unfortunate examples of programmers who are bad at C, definitely not a C problem.

EDIT: Okay, this comment was snarky and not in good spirit. To be serious, I think we are increasingly seeing that the notion that humans can write non-trivial amounts of C correctly is false. Especially in the face of AI-assisted vulnearbility hunting these programs a crumbling. This is not an indictment of humans, it's a sign that C is not equipped to meet this moment.

marvinborner 3d ago on HN
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...

K0nserv 3d ago on HN
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.
nh2 3d ago on HN
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.

K0nserv 3d ago on HN
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`.
uecker 3d ago on HN
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).
K0nserv 41h ago on HN
I said "specific", not "exclusive". I think we agree though, yes it's possible to bound check in C and not in Rust, but the code that gets written in practice matter a whole lot.

From your previous comments I think you'd have great insight on how to write safer C, would love a blog post on the topic if you ever have time.

stevefan1999 3d ago on HN
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.

K0nserv 3d ago on HN
I didn't think the /s was necessary
xaksnTMu2 3d ago on HN
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.
yerimyerimie 3d ago on HN
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/
peanut-walrus 3d ago on HN
How was this disclosure coordinated? Considering the website dropped before the official nginx patch was even released on Github...
dannyw 3d ago on HN
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.
codedokode 3d ago on HN
Why post such exploits? What is the purpose?
voakbasda 3d ago on HN
Fame, money, and everything else those bring along for the ride.
goodmythical 3d ago on HN
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.

pixl97 3d ago on HN
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.

rs_rs_rs_rs_rs 3d ago on HN
I agree, never post anything you find, keep all the bugs to yourself, write reliable exploits who knows when you would need one.
streetfighter64 3d ago on HN
Seems like you're a fan of security by obscurity over secure code?
hn773746483 3d ago on HN
Marketing, baby! It's the same small handful of firms pushing these same AI-generated spam attention grabbing vulnerabilities, quirky name and domain on top for maximum fear mongering.
streetfighter64 3d ago on HN
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?

pixl97 3d ago on HN
Because some people get deranged by AI in the opposite way AI lovers do.
phrotoma 3d ago on HN
> Will the exploit be published?

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

dannyw 3d ago on HN
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.
ronfriedhaber 3d ago on HN
Great work by wiz.
jascha_eng 3d ago on HN
Never turned http2 on in my side project pfew. But still, this is one is pretty rough...
koolba 3d ago on HN
This whole week is rough. And it’s only Wed.
jascha_eng 3d ago on HN
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.

whartung 3d ago on HN
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.

baby_souffle 3d ago on HN
> 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.

philipwhiuk 3d ago on HN
So...what library/tool/language is next folks? Presumably Wiz is sitting on a bunch more.
dannyw 3d ago on HN
Linux2shell?
fn-mote 3d ago on HN
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.

cute_boi 3d ago on HN
Tech moves too fast and if we move too fast without doing review like 5-10 times, this will keep happening.
mynameisvlad 3d ago on HN
I would hope you know that no matter how many reviews, humans are fallible and miss things.
cute_boi 3d ago on HN
AI agents are also fallible? So, what do you think we should do?
mynameisvlad 3d ago on HN
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.

chpatrick 3d ago on HN
The difference is that the AI doesn't get tired so you can review everything.
g-b-r 3d ago on HN
Except that it's very far from guaranteed to find everything, and especially everything that humans would find easily.
dymk 3d ago on HN
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.
g-b-r 3d ago on HN
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....
dymk 3d ago on HN
Yes, we both posted anecdotes, very astute.
g-b-r 3d ago on HN
Well, I only said that it's far from guaranteed to find everything, while you seemed to argue that your anecdote guarantees it
phkahler 3d ago on HN
>> 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.

anilakar 3d ago on HN
> tried and true software

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

jacobgold 3d ago on HN
AI is securing the internet. This is great. You should assume professional hacking gangs and state actors discovered (at least some of) these vulnerabilities months and years ago.
pixl97 3d ago on HN
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.

colechristensen 3d ago on HN
>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.

icedchai 3d ago on HN
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.
jacobgold 3d ago on HN
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.
mikepurvis 3d ago on HN
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.
markhahn 3d ago on HN
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.

pixl97 3d ago on HN
Question is how big is that finite number? One a month for the next 40 years helps no one.
fivedogit 3d ago on HN
This is the correct view. Look at blockchains.
mrheosuper 3d ago on HN
Software has finite bugs, but there is infinite software, especially with "vibecoding", everyone, every organization can vibecode a "nginx" for in house using.
soon_to_be_sb 3d ago on HN
>but there is infinite software

And the attacker does not have infinite tokens..

mrheosuper 3d ago on HN
Close to infinite that one may not care about it anymore, especially when they are backed by State.
jpardoe 3d ago on HN
Well that's up to them.
devy 3d ago on HN
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.

spiderfarmer 3d ago on HN
Attack the attackers.
ActorNightly 3d ago on HN
> The problem is security is a much harder job than attacking.

Nope.

Let say Im running a vulnerable Ngnix server. All that would take to stop any and all attacks is a simple firewall that sees anything that even remotely looks like shell code (i.e non ascii characters, ROP patterns, strings of noops, e.t.c) close that connection,blacklist that ip.

>Also in the past attackers were willing to sit on exploits longer and not do things with them,

Also nope. The reason why you didn't see many exploits is because they are mostly useless unless you have resources. You can take a gander through all the CVEs that AIs are finding. 99% of them are either DDOS with some possibilty of remote code execution only under very particular conditions, or require already user level code execution to get to root.

There are a few sprinklings of truly bad ones, but even for those, a good portion of them that exist on critical systems are protected by secondary things, like firewalls that detect shell code and close the connection and ban the IP for some time. True network security will never be not needed, as humans are still the most vulnerable vector, and if you don't have systems in play that can counter bad actors, then you are asking to get hacked.

All of this AI finding exploits is basically fear mongering that is going to be used to sell AI products that secure systems.

majewsky 2d ago on HN
> Let say Im running a vulnerable Ngnix server. All that would take to stop any and all attacks is a simple firewall that sees anything that even remotely looks like shell code (i.e non ascii characters, ROP patterns, strings of noops, e.t.c) close that connection,blacklist that ip.

How will your firewall look inside TLS traffic? If the answer is to have it terminate TLS, congratulations, now your firewall appliance is the next target.

Florin_Andrei 3d ago on HN
> > 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, or neither, are true. You can really go full Schrodinger and put a probability distribution on everything.

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

Is it good for me and, beyond me, for the world in general?

thaumaturgy 3d ago on HN
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.

VolCoder 3d ago on HN
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.
graemep 3d ago on HN
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).
robotmay 3d ago on HN
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.
robwayne 3d ago on HN
I tend to agree. We should really be focusing on simplifying instead of using these patched up, massive, and complex software stacks. For me it's starting to become a non-negotiable. I know lots will disagree on the basis of presumed practicality, though.

I don't even care if it's all written in Rust, essentially none of my problems require software boasting multi-millions of lines of code. I guess my browser and OS? But even those I question greatly.

It's funny, I never thought I'd be one to compile my own kernel, but as of this year I've been maintaining an extremely stripped down Linux base for my NixOS servers and desktops.

Feels like my end game is going to be on some micro kernel that I compile all my software for, lol.

graemep 2d ago on HN
This is somewhat on those lines:

This is somewhat on those lines: https://news.ycombinator.com/item?id=50556533

Shiggy_ 3d ago on HN
Usenet.
seanw444 3d ago on HN
> 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

Ungh 3d ago on HN
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.

testtestmetest 3d ago on HN
"Hacker gangs"
sbodnar 3d ago on HN
Just like in the movie "Hackers".
keyle 3d ago on HN
Hey, that's a piece of art!
consumer451 3d ago on HN
What term do you prefer?

Organized Cybercrime?

Digimafia?

e2p3yHizAungrCeKum7ifrssu32lnzEnyRoGdcAo23m2dNapvoGmymid.onion?

robotnikman 3d ago on HN
Kim Jong Un's megayacht fund
wannabe44 3d ago on HN
Well I didn't get into any trouble with the professional hacker gangs. The script kiddies on the other hand...
make3 3d ago on HN
AI is also making it much easier to attack, likely more than it's helping secure things
WarmWash 3d ago on HN
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.

canibalrex 3d ago on HN
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.
make3 3d ago on HN
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.

pixl97 3d ago on HN
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.

binsquare 3d ago on HN
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

pstuart 3d ago on HN
One would think that the NGINX team would be banging on their code with AI agents trying to attack it for preemptive security.
vagrantJin 3d ago on HN
There's no honor among the thieves if everyone can be a thief.
darkwi11ow 3d ago on HN
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.
lbrito 3d ago on HN
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.
djha-skin 3d ago on HN
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.

BatteryMountain 3d ago on HN
Those who don't keep up & pay technical debt will get eaten. There is no escaping this.
vanschelven 3d ago on HN
and C is the tinderbox
UltraSane 3d ago on HN
The billions of lines of C and C++ code is like a square lightyear of agar for LLMs to find bugs in.
codedokode 3d ago on HN
Not AI but poorly designed programming languages ignoring integer overflows.
vlovich123 3d ago on HN
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.
tptacek 3d ago on HN
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.
vlovich123 3d ago on HN
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).
tptacek 3d ago on HN
This is the thing about `unsafe` blocks: they're not memory safe. It's right there in the name.

I'm not making a Rust advocacy argument. I'm just saying: it's true that integer handling issues are endemic to mainstream programming languages, but the integer handling itself is almost never the actual sharp end of the vulnerability.

vlovich123 3d ago on HN
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.

AnthonyMouse 3d ago on HN
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.
tptacek 3d ago on HN
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!).

codedokode 3d ago on HN
"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?

vlovich123 3d ago on HN
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.
pixl97 3d ago on HN
How does that saying go?

"Go fast and get your things broken into"

AnthonyMouse 3d ago on HN
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.
codedokode 3d ago on HN
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.
AnthonyMouse 3d ago on HN
The trouble is that this behavior is not limited to C.
10000truths 3d ago on HN
Zig traps arithmetic overflow/underflow when compiling in ReleaseSafe.
vlovich123 2d ago on HN
Zig fans like to bring up ReleaseSafe as if it’s a mode anyone runs anything in production in. I’m pretty sure the largest Zig projects (TigerBeetle and Ghostty) run ReleaseFast.
10000truths 35h ago on HN
I can't speak for Zig fans, but what you mention has nothing to do with the programming language and everything to do with maintainer preference. Nothing stops you from cloning an open-source project and building from source with your own preferred optimization level.
jorangreef 19h ago on HN
We’ve always run ReleaseSafe at TigerBeetle. It’s plenty fast. (And we run with 6K+ assertions also enabled in production.)
BoingBoomTschak 3d ago on HN
Lisp or Python have a proper numeric tower and don't default to machine types. Keyword being default, fast is still possible in CL.
benlivengood 3d ago on HN
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.
codedokode 3d ago on HN
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.
rlt 3d ago on HN
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.
origini 3d ago on HN
And your first thought was the NSA? Patching and adding their own rootkit eh?
zzril 3d ago on HN
Don't you dare patching my honeypots!
UltraSane 3d ago on HN
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.

acdha 3d ago on HN
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.

dnautics 3d ago on HN
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)
antonvs 3d ago on HN
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.

sophacles 3d ago on HN
What overhead from borrow checking?
FridgeSeal 3d ago on HN
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.

antonvs 3d ago on HN
I was talking about coding effort - reasoning about borrowing, lifetime annotations, and the fact that this can make refactoring more involved because lifting arbitrary blocks of code, especially when closures are involved, can require extra work.

Someone who's saying "the rest of the language sucks" may be thinking of something like that, hence my question above.

But when it comes to performance overhead, programming around the constraints of the borrow checker can introduce runtime costs that wouldn't otherwise be necessary - e.g. when cloning is used to handle borrowing conflicts.

Even if, in theory, it's possible to restructure a program to avoid performance impacts, in practice people don't always do that, not least because more efficient solutions may not always be obvious. This comes back to my point about coding effort.

I spent a bunch of time, pre-LLM, to try to replace a bunch of unsafe blocks scattered throughout an ML inference codebase, that someone had used to achieve maximum performance. I wasn't able to get a version that performed as well.

This kind of thing may not matter if you're writing e.g. ordinary web services, but for more performance-critical code, it can be an issue. Of course, `unsafe` is always an option to deal with that, but that undermines Rust's guarantees.

dnautics 2d ago on HN
you should be reasoning about spatial memory safety ANYWAYS, so this is not imo extra overhead. Arguably with a checker in place (if the checker is sound and if you have good intuition about how to design code), you have to reason about it LESS, because you keep barreling on and only need to stop to think about it less. I suspect that people who complain about the borrow checker are just miring themselves into lazy choices that pile on top of each other, especially if you add more and more kludges, and then when one thing changes they need to do a ton of painful refactoring, that can break things too, if you're depending on a mutation that suddenly turns into a clone for example.
dboreham 3d ago on HN
> 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.

UltraSane 3d ago on HN
Ownership model is perfect for multithreading but then Rust goes all in on async like WTF?
dnautics 2d ago on HN
I mean, in principle, if you design it well, async is just a special case of multithreaded code where the code happens to run on the same core. Not saying that rust does this ofc
cozzyd 3d ago on HN
lack of a stable ABI is a big one
dnautics 2d ago on HN
I don't think the overhead of borrow checking is fundamentally a problem (though I hate the tick quote, that's a silly personal aesthetic preference). That said I do think it's possible to check temporal memory safety with very few if any extra annotations, and that would be preferable, I am not in principle opposed to how rust generally does things, doubly so if "drop" were explicit, instead of implicit.

Speaking of implicitness: There's a lot of implicitness in rust that can go wrong, especially with the traits system, and composition. Canonical example is copy + iter, which never gives you what you want.

This is a language design problem. The composition of two very basic stdlib traits should not cause such a problem, suggests something wrong with traits in principle -- it's not "solving" polymorphism in the way that was hoped, are the userland traits that your senior Dev (or fable) wrote free of compositional implicitness unsoundness? Are you sure?

Second example of compositional implicitness causing problems: recently identified CVE's in rust stdlib where drop can easily be composed to call a panicking function where lots of shenanigans can happen. There's no way to annotate "can panic" in rust (nor should there be?). It's easy to implement a custom type with a Drop that calls, say, a panickable- inner-type method that will have exactly those problems. Note that these CVE's happen because in rust, IIUC, a panic unwinds through drop instructions, AND can be caught.

Not an explicitness problem but macros too. Sometimes macros create major gunning fog while reading a codebase.

Allocators being bolted on as an afterthought is kinda bad for a systems PL. For example, postgres has something like 11 allocators and Erlang has 10, but it looks like it's getting fixed?

dboreham 3d ago on HN
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.
acdha 2d ago on HN
I mean, we knew there wasn’t a great alternative yet but even by like 1997 C web services were notorious for having overflow exploits (remember piping Perl “A”x99999 into things and seeing what broke?) and the language was famously limited so a lot of bugs happened because developers had to build by hand things like basic string operations which were standard features in other languages.

This was one of the reasons why people switched to things like Java, Perl, Python, PHP, etc. where performance wasn’t critical. I remember having that conversation with a number of clients who’d been burned on delays and reliability issues building everything in C as opposed to using a higher level language and maybe a couple of C libraries.

ThrowawayR2 3d ago on HN
Unlikely. An Ada compiler would be an expensive additional purchase, a C compiler usually came as part of the installed copy of UNIX.
dboreham 3d ago on HN
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.
ActorNightly 3d ago on HN
Nothing to do with language, everything to do with lack of standards. You can write perfectly unsafe Rust code.

Dunno if you have ever worked in software engineering, but if you have, count the times you have seen a backend server api written without any input sanitization or checking. Most of these exploits can be defeated by checks on inputs. I.e, no "Alex\x90\x90\x90\x90\xcc\xcc\xcc\xcc", is not a valid input for someones name.

slopinthebag 3d ago on HN
claiming that vulnerabilities due to memory unsafeness has nothing to do with the choice to use a memory unsafe language is completely ridiculous. no wonder software is getting pwned left and right, we’re just not a serious engineering discipline at all.
UltraSane 2d ago on HN
This is like saying walking a tightrope is easy if you just don't fall off.
fla 3d ago on HN
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.
zodwick 3d ago on HN
There is going to be hardships before this gets better. But it is hardship we must endure
jooops1 3d ago on HN
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.
tgv 3d ago on HN
It's like blaming people for having wooden doors when robots with chainsaws start appearing in the street.
jethro_tell 3d ago on HN
When 85 percent of doors were installed before metal doors were available.
streetfighter64 3d ago on HN
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.

crtified 3d ago on HN
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.

dalmo3 2d ago on HN
> There's no bugs in a wooden door

Heh. There's borer.

And now there's people releasing swarms of borers in the suburbs. Now you perfectly serviceable door is compromised.

sixothree 3d ago on HN
> robots with chainsaws start appearing in the street

Please stop willing things into existence.

gosub100 3d ago on HN
What about ASLR and DEP? Guess they are useless?
dilyevsky 3d ago on HN
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.
codedokode 3d ago on HN
Why your standards are so low?
gspr 3d ago on HN
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 instead use of AI as a defense. Then we're truly talking about burning down the internet.

pixl97 3d ago on HN
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.

worldsavior 3d ago on HN
This comment is very dramatic and very hype-y. I don't think this is an appropriate comment.
dyauspitr 3d ago on HN
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.
lenerdenator 3d ago on HN
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.

SV_BubbleTime 3d ago on HN
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.

raincole 3d ago on HN
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.

I do think the world is going a little insane tho. People suddenly believe in security through obscurity because, uh, AI bad?

tripleee 3d ago on HN
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.

pixl97 3d ago on HN
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.

claude-ai 3d ago on HN
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?

Creamsicle47 3d ago on HN
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.

tclancy 3d ago on HN
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.

Creamsicle47 3d ago on HN
Not quite
Sebguer 3d ago on HN
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.

cozzyd 3d ago on HN
web scale vulnerabilities
throooooo 3d ago on HN
"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.
cube00 3d ago on HN
This is why I worry about upgrading in place between major Fedora versions. I think every six months you really need start from a fresh image.
Pokepokalypse 3d ago on HN
Imagine how those of us running a commercial OS feel. . . (Mac OS, Windows)
cube00 3d ago on HN
I should have been clearer. I was thinking in terms of an internet exposed server that gets hammered with thousands of intrusion attempts per day. I'd have the same concern with Windows Server.
devopstimetoshi 3d ago on HN
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.

Pokepokalypse 3d ago on HN
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).

whizzter 2d ago on HN
No, AI is just exposing 30+ years of sloppy code written in unsafe languages.

People joke about the "Rewrite it in Rust" crowd, but that call is rooted in an unease anyone with a sceptic mind has had about all the C and C++ code we've got running our infrastructure running around tracing pointers with little lifetime- or bounds-checking. (Yes, it's a runtime cost but it's 2 CVE's, one for each class)

lionkor 2d ago on HN
The rewrite it in rust crowd is getting a major thing wrong; rewriting without sufficient (lived) knowledge of the original will usually end in disaster.

This is why people (including me), who absolutely adore Rust, make fun of the RiiR crowd. If you think a rewrite from the ground up is the best way to approach making software safer, you've lost the plot entirely.

Let's say you rewrite your terminal emulator in Rust from C or C++; you'll first undo decades of bug fixes, compatibility decisions, quirks, etc. which you WILL have to deal with eventually. This essentially puts you back at least a decade, because these issues take users using the software to point out to you before they're fixed. The only benefit of this whole game being that you get memory safety. These teams are never the original teams, which is the source of the problem. A rewrite can only succeed if it's a result of all the learned failures and shortcomings of the original, otherwise it's bound to repeat every single mistake and add more on top.

And you don't even deliver memory safety to the users of the original this way, because people won't use the rewrite, because it's buggy, incompatible, etc.

wasmitnetzen 3d ago on HN
Docker images are a bit delayed because of unstable GitHub runners: https://github.com/nginx/docker-nginx/pull/1075#issuecomment...

Cue xkcd

kawsper 3d ago on HN
Sadly, the same happened last time a CVE hit.
8by3 3d ago on HN
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...

ps. if you are on FreeBSD and doing TLS directly

sed -i.bak -E 's/^([[:space:]]server[[:space:]]\{)$/\1\ http2 off;/' /usr/local/etc/nginx/nginx.conf ;service nginx restart

wildmXranat 3d ago on HN
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.
birdgoose 3d ago on HN
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.
1over137 3d ago on HN
FreeBSD ports are now updated to nginx 1.30.7.
black3r 3d ago on HN
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.

vanschelven 3d ago on HN
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
Gigachad 3d ago on HN
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.
verst 3d ago on HN
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.
meowface 3d ago on HN
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.
black3r 3d ago on HN
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.
ChadNauseam 3d ago on HN
Another reason not to couple your software versioning to Ubuntu and Debians' package managers' schedule
sippingabonedry 3d ago on HN
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.

nsoam 3d ago on HN
...or you could use Gentoo.
antonvs 3d ago on HN
Keep the flame alive!
robotmay 3d ago on HN
Embrace true chaos and let an LLM do the config file merges for you in Portage.
bombcar 3d ago on HN
LLMs love gentoo they go hog wild.

Which may be good or bad.

mikepurvis 3d ago on HN
NixOS is probably the best modern option for those who crave building the whole world from source.
prennert 3d ago on HN
yep, already deployed fixes to our fleet (NixOS for the win)
kd913 3d ago on HN
Or just use it in a podman quadlet?

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

usr1106 3d ago on HN
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.

kd913 2d ago on HN
Small footprint inherently means less code to audit.

Containers by default enforce some level of restrictions and a sandbox around it all.

If someone does break alpine, nginx, they would still need to get out of the container sandbox?

nginx when hosed gives full access to the system.

usr1106 2d ago on HN
Depends on what type of continers.

As a Redhat container developer (IIRC) put it a long time ago: Containers do not contain.

Especially with docker everything running as host root opens new problems. Rootless containers as podman are more complex, so more code again. And user namespaces had their own vulnerabilities.

No simple answer to security...

kd913 2d ago on HN
That was in 2014/15 in regards to docker, I think rootless podman with enforced capability reduction and tuned apparmor or selinux is a tad different now.
usr1106 2d ago on HN
Sure, it's way more secure as long the security mechnisms work as designed and are used correctly.

But in the grandcrandparent the argument was that small gives reduced attack surface. SELinux and friends don't qualify for small and simple.

Not trying to say you should not use it. But I will not be surprised when a fatal vulnerability or SELinux misconfiguration gets revealed somewhere...

xorcist 3d ago on HN
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.

antonvs 3d ago on HN
It makes more sense to install services like nginx via the official containers. In the modern world, the OS is for base services only.
raegis 3d ago on HN
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.
kd913 3d ago on HN
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.

subsection1h 3d ago on HN
> Podman container auto-updates to the latest upstream

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

kd913 2d ago on HN
Sure but the trade off is faster patches from upstream and actual containment if something is exploited in the wild.

My nginx instance is very very tightly scoped for what privileges, file system space and capabilities it can access.

If someone exploits nginx on host, they have a remote shell and access to everything.

jamesfinlayson 3d ago on HN
Agreed. At a previous job all the important stuff came from repos that always shipped latest.
newsoftheday 3d ago on HN
This looks like it was patched in Ubuntu on the 12th?

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

man8alexd 3d ago on HN
This Ubuntu security notice is about an Apache vulnerability, not nginx.
kayfox 3d ago on HN
> Several security issues were fixed in Apache HTTP Server.

Um, what does this have to do with NGINX?

baggy_trough 3d ago on HN
magahugu 3d ago on HN
Good to see
oddIdentities 3d ago on HN
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.

fodkodrasz 3d ago on HN
Luckily we could not see your face during writing this, as I’m pretty sure no serious person in the industry can say this with a straight face… Maybe Theo de Raadt, but there it is a running joke I guess.
dvershinin 3d ago on HN
Not quite. The kernel bug is only the worker-to-root step. Code execution as the nginx worker through the two HTTP/2 CVEs needs nothing but HTTP/2 enabled. Three of the five CVEs don't need HTTP/2 at all: one is HTTP/3 with an upstream, one is resolver + variable proxy_pass + subrequests, and one is the mail proxy with auth_http.
oddIdentities 2d ago on HN
>the worker-to-root step

this is the whole issue, right?

>Code execution as the nginx worker

cry me a river

fhub 3d ago on HN
FWIW, for nodes that don't have packages, I compiled from source under /opt and deploy scripts check equal or higher version so it will auto switch back when the new packages are installed. Seemed less risky than disabling http 2.
mediaserf 3d ago on HN
You can also add nginx.org repos and install the updated versions from there. https://nginx.org/en/linux_packages.html
throwaway2037 2d ago on HN
That is a very well written page. I am pleasantly surprised that they provide detailed instructions to verify the package signature before installation.
hiddenvulkcan 3d ago on HN
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
throwitaway222 3d ago on HN
I told me agent to do that - similar situation.
TedDoesntTalk 3d ago on HN
> me agent

Did you talk to it like a pirate?

hiddenvulkcan 3d ago on HN
New caveman version just dropped! /Pirate
dboreham 3d ago on HN
There are large areas of the English speaking world where this is common speech.
throwitaway222 2d ago on HN
AI matey
Ikersl 3d ago on HN
Definitely, but unfortunately I use Debian for my servers so.
weitendorf 3d ago on HN
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

trey-jones 3d ago on HN
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.
weitendorf 3d ago on HN
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.

TedDoesntTalk 3d ago on HN
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.
weitendorf 3d ago on HN
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.

technion 3d ago on HN
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.

Lucasoato 3d ago on HN
Does Envoy support things like rate limiting?
weitendorf 3d ago on HN
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...

Lucasoato 3d ago on HN
Thanks for the wonderful answer!
fcantournet 3d ago on HN
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.
ragall 3d ago on HN
As a gRPC proxy Envoy is indeed more widely used than Nginx: it's used as the gRPC proxy load balancer on Google Cloud.
trey-jones 2d ago on HN
Well that is of course because it is the only proxy that seems to speak gRPC fluently. Anyone who's ever tried to configure bare nginx to serve gRPC knows this. And yet, I would wager that many stacks use both.

This requirement turns me off of gRPC entirely. Maybe Envoy truly is more secure than nginx, but it's still a whole-ass additional attack surface. It seemed to me that eliminating it if possible was best.

ragall 2d ago on HN
It seems to me that eliminating Nginx and sticking to Envoy is the best.
verst 3d ago on HN
I am using Envoy :)
voodooEntity 3d ago on HN
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
weitendorf 3d ago on HN
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.

anonreplier 2d ago on HN
How would requiring auth mitigate against a vulnerability like this nginx one?
chanux 3d ago on HN
I wonder if being prepared to switch the reverse proxy you use in whim is a good strategy in this climate.
trollbridge 3d ago on HN
A while ago I started releasing our stuff with dual stacks (originally nginx and haproxy, more recently added traefik to the list).
pjmlp 2d ago on HN
Hopefully Envoy is using bounded checked collection types and no C like tricks, with modern C++ best practices, otherwise there is not much benefit, security wise.
ktm5j 3d ago on HN
If you're using httpd just fyi - there was a recent RCE vuln for apache that was also http2 specific.
geocar 3d ago on HN
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.

ghm2199 3d ago on HN
The patch gap.
SubiculumCode 3d ago on HN
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.
ryanisnan 3d ago on HN
RCE is about at the top of the stack for severity.
ArcHound 3d ago on HN
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.
PcChip 3d ago on HN
put up some bitcoin behind an nginx server and tell hackernews to steal it, see how long it takes
wildmXranat 3d ago on HN
:) 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
ryanisnan 3d ago on HN
Great context. Thank you for the add.
pocksuppet 3d ago on HN
This was also true with php2shell but AI got there in the end.
smallerize 3d ago on HN
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"
mountainro53 3d ago on HN
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.
Gigachad 3d ago on HN
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..

lanstin 3d ago on HN
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.
requeo 3d ago on HN
These commits weren't visible until today. Yesterday, the last public commit was Nov 9.
TedDoesntTalk 3d ago on HN
How is that done with git?
jen729w 3d ago on HN
Just don't push upstream?
TedDoesntTalk 3d ago on HN
bacor44 2d ago on HN
Very reassuring to see the tests + fix.
throwaway2037 2d ago on HN
I'm confused. Is this sarcasm? When I looked at the diff on that PR, I don't see any unit tests. Am I missing something?
brunoborges 3d ago on HN
> 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.

antonvs 3d ago on HN
How's that alignment going...
rheisen_ 3d ago on HN
As much as I like open weight models.. what alignment?

There’s no good solution, it’s a minefield and the only choices are what you’re willing to lose to maybe make it out of it

antonvs 3d ago on HN
> what alignment?

That was my point. Anthropic and OpenAI used to talk about alignment a lot, and even try to use it as a way to justify restrictions on AI development. They can’t really use that argument any more.

streetfighter64 2d ago on HN
People using LLMs to hack stuff isn't really an alignment issue.

Many people, even high ups at AI companies, conflate alignment with "guardrails" (AI companies conflate intentionally as a matter of business strategy).

Alignment is just making sure the AI doesn't become a paperclip maximizer or go off and hack stuff on its own whims. This is akin to making sure a car doesn't accelerate without the accelerator being pressed.

Guardrails are about making sure people can't use the AI for nefarious purposes. This is like some sort of automatic braking to prevent people from intentionally hitting stuff with their car.

The interesting thing with AI development, is that guardrails are in some ways easier to implement than actual alignment, which is why I think many like to conflate them.

icantevenhold 3d ago on HN
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

Aperocky 3d ago on HN
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.
icantevenhold 3d ago on HN
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
antonvs 3d ago on HN
> Seriously reconsidering if open source has a future nowadays

*In C or C++.

pjmlp 3d ago on HN
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.

anthk 3d ago on HN
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.

pjmlp 3d ago on HN
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.

gmueckl 3d ago on HN
rust isn't invulnerable.
sophacles 3d ago on HN
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.
hunterpayne 3d ago on HN
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.
openasocket 3d ago on HN
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
dralley 3d ago on HN
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 splitting the hull in half.

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.

paganel 3d ago on HN
> Russian soldiers ride on top of their tanks a

That stopped being true for at least 3-4 years (with APCs maybe still used until two or so years ago, tanks are still used but as "turtles" or/and "porcupines" [1], no way to have soldiers riding them). Drones have conquered (almost) everything.

[1] https://miro.medium.com/v2/resize:fit:1400/format:webp/1*CQr...

hunterpayne 3d ago on HN
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.

pjmlp 2d ago on HN
Application servers, and apparently the idea was so good that nowadays there are startups selling the same idea with cloud based WebAssembly workloads.
Mordagh 2d ago on HN
> Fun fact, these specific types of problems aren't possible on a JVM.

CVE-2026-114938 would like a word. https://calif.io/java4shell

Yes, I know, different issue. But saying Java would be better for webservers just two days after a serious JDK RCE is pretty ironic :P

perlgeek 3d ago on HN
What happens when somebody tries to contribute based on the last-published commit? Do you merge/rebase their contributions for them?
icantevenhold 3d ago on HN
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

mort96 3d ago on HN
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.

baq 3d ago on HN
Amounts to ‘won’t be getting contributions‘ which is maybe not that bad at this point on the timeline
mort96 3d ago on HN
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
icantevenhold 3d ago on HN
We do have a LLM disclosure policy.

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

seba_dos1 3d ago on HN
You only need to enforce it enough to fulfill its goals.

https://xkcd.com/810/

cluckindan 3d ago on HN
The future is in closed source ecosystems on a modified Harvard architecture
davidkwast 3d ago on HN
WTF but I get the point
jamesfinlayson 3d ago on HN
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.

GoblinSlayer 2d ago on HN
cve-2026-114938 was found in assembler code, lol
throwaway2037 2d ago on HN

    > Seriously reconsidering if open source has a future nowadays
Personally, I am not a doomer about these LLM advances. Most of the open source stack is going to be combed over 1000x in the next 12 months to find bugs and vulns. They will get fixed. After that, open source will be stronger than ever.
a34729t 3d ago on HN
Oh everybody worth worrying about is monitoring this on every major repo already.
EGreg 3d ago on HN
HTTP/2 is usually the source of most of these bugs in webservers of all kinds
OJFord 3d ago on HN
Yes, fixing open source software is at most an obfuscated announcement.
4ndrewl 3d ago on HN
idk, the license tells me that there's a good reason why you shouldnt expect that.

Now, if you were paying for support from a vendor, that's a different matter.

"THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED."

tancop 3d ago on HN
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.

gkbrk 3d ago on HN
HTTP/1.1 is still way better and way simpler than HTTP/3.
seki285 3d ago on HN
Could you please share why?
lysace 3d ago on HN
~25 years of hardening.
gkbrk 3d ago on HN
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.
qweqwe14 3d ago on HN
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.
dannyw 3d ago on HN
A simpler protocol has less surface area for vulnerabilities. I think GP was just using that as an expression of this.
doodlesdev 3d ago on HN
That's not the point. The point is that the simpler the protocol is to implement, the simpler it is to validate and harden the implementations. A HTTP/1.1 implementation can be 10x to 30x smaller than an equivalently well-rounded HTTP/3 implementation.
qweqwe14 2d ago on HN
In the real world you want performance. "Simpler" is not "more performant" in this case. Do you understand that HTTP/3 solves real problems for real use cases, and wasn't invented because someone wanted to make a more complicated thing?

It's like if I said "you can just use Linux 2.6, it's simpler"

cozzyd 3d ago on HN
I've definitely done that before on a microcontroller.
postalrat 3d ago on HN
You forgot about all the networking hardware and software those run on. The difference is negligible.
Liuser 3d ago on HN
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. The response is to patch and move on if your environment requires h2; many large orgs these days use microservices which use h2 (grpc) as its network.

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 and just serve vanilla text webpages that’s also fine to just use h1.1. Blanket statements that h1.1 is better is just, wrong. Context is important on choosing what’s best for your environment.

otterley 3d ago on HN
> 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.

oasisbob 3d ago on HN
HTTP 1.1 has enough complex behaviors at the edge that the idea of implementing it in a day, correctly, is wildly laughable.
qurren 3d ago on HN
It's debuggable. I can wireshark it and understand everything. I can even speak to HTTP servers directly with a telnet client and fetch pages. I can write microcontroller code in C that issues REST API requests. Pure TCP, nice to work with, no multiplexed UDP hex craps.

Simple is good.

oasisbob 3d ago on HN
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.

layer8 3d ago on HN
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.
SoftTalker 3d ago on HN
Because HTTP3 was implemented without any errors? Citation needed I guess.
lsof 3d ago on HN
well HTTP3 wouldn't have helped here (CVE-2026-121810)
Woodi 3d ago on HN
More like solution should be moving to sane HTTP4 - v3 corporations made for themself so v4 can be made for users :) Without corporations involvement.

Apache and Mozilla Funds would be ideal choice for such open source implementation but I doubt they will do anything to extend their usefullness...

So: users require just visual part and html/css is not bad for that. Could be better. But transport part can be [re]done at will. Eg. would be nice to have separate layers for connection security and actual transportation.

Imustaskforhelp 3d ago on HN
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)

origini 3d ago on HN
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.

dist-epoch 3d ago on HN
Imagine using Nginx
codedokode 3d ago on HN
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.
deathanatos 3d ago on HN
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.

insanitybit 3d ago on HN
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.
codedokode 3d ago on HN
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.
insanitybit 2d ago on HN
Yes, that is bad. No one is saying that all bugs require memory unsafety.
TZubiri 3d ago on HN
>Python simply can't overflow, since its integral type is not a fixed width.

Python master race

IshKebab 3d ago on HN
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.
hollerith 3d ago on HN
HTTP/2 is so complicated that the code that handles it tends to be vulnerable. What a surprise
acdha 3d ago on HN
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.
basilikum 3d ago on HN
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.
acdha 2d ago on HN
That seems more like an argument for removing HTTP 1 and its intractable problems around parsing confusion.
dist-epoch 3d ago on HN
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

fullstop 3d ago on HN
I have used nginx for ages, but have been slowly moving things over to Traefik + Caddy.

I guess it was the right move.

Juvination 3d ago on HN
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.
wolttam 3d ago on HN
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
timw4mail 3d ago on HN
Yes, but multi-file find and replace exists, and you can verify every replacement.
therepanic 3d ago on HN
What’s the point of these researchers if their autonomous system is now finding these vulnerabilities?
pixl97 3d ago on HN
Making sure AI isn't hallucinating.
hokkos 3d ago on HN
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...

Showing 400 of 637. Read the rest on Hacker News

Comments are loaded live from Hacker News and are not stored by Mid or Real.