Top
Best
New

Posted by speedping 3 hours ago

Pre-auth RCE in Nginx HTTP/2 handling(www.wiz.io)
443 points | 153 comments
black3r 1 hour ago|
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.

TedDoesntTalk 6 minutes ago||
Source: https://github.com/nginx/nginx/commit/b89c4100bf6762a45e4a64...
verst 1 hour ago|||
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 42 minutes ago||
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 35 minutes ago||
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.
requeo 18 minutes ago|||
These commits weren't visible until today. Yesterday, the last public commit was Nov 9.
SubiculumCode 1 hour ago|||
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 1 hour ago||
RCE is about at the top of the stack for severity.
lanstin 15 minutes ago|||
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.
ArcHound 1 hour ago|||
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.
ryanisnan 19 minutes ago|||
Great context. Thank you for the add.
PcChip 41 minutes ago|||
put up some bitcoin behind an nginx server and tell hackernews to steal it, see how long it takes
vanschelven 1 hour ago|||
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
ghm2199 1 hour ago||
The patch gap.
fn-mote 2 hours ago||
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.

jacobgold 1 hour ago||
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 1 hour ago|||
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.

jacobgold 1 hour ago|||
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.
colechristensen 1 hour ago|||
>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.

testtestmetest 16 minutes ago||||
"Hacker gangs"
Florin_Andrei 1 hour ago||||
> > 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 59 minutes ago||||
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 43 seconds ago||
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.
Ungh 36 minutes ago|||
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.

jooops1 41 minutes ago|||
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.
fla 1 hour ago|||
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.
worldsavior 12 minutes ago|||
This comment is very dramatic and very hype-y. I don't think this is an appropriate comment.
dilyevsky 34 minutes ago|||
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.
zodwick 1 hour ago|||
There is going to be hardships before this gets better. But it is hardship we must endure
rlt 1 hour ago|||
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 1 hour ago|||
And your first thought was the NSA? Patching and adding their own rootkit eh?
zzril 1 hour ago|||
Don't you dare patching my honeypots!
gspr 22 minutes ago|||
I'm pretty solidly in the AI skeptic camp. But adversarial use of AI to improve software security is a good thing in my mind.

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

codedokode 1 hour ago|||
Not AI but poorly designed programming languages ignoring integer overflows.
vlovich123 1 hour ago||
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.
benlivengood 4 minutes ago|||
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.
10000truths 1 hour ago||||
Zig traps arithmetic overflow/underflow when compiling in ReleaseSafe.
tptacek 1 hour ago||||
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 1 hour ago||
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 1 hour ago||
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.

BoingBoomTschak 44 minutes ago||||
Lisp or Python have a proper numeric tower and don't default to machine types. Keyword being default, fast is still possible in CL.
codedokode 1 hour ago|||
"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 1 hour ago||
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 1 hour ago||
How does that saying go?

"Go fast and get your things broken into"

cute_boi 2 hours ago|||
Tech moves too fast and if we move too fast without doing review like 5-10 times, this will keep happening.
phkahler 1 hour ago|||
>> 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.

mynameisvlad 1 hour ago|||
I would hope you know that no matter how many reviews, humans are fallible and miss things.
cute_boi 1 hour ago||
AI agents are also fallible? So, what do you think we should do?
mynameisvlad 1 hour ago||
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 1 hour ago||
The difference is that the AI doesn't get tired so you can review everything.
g-b-r 6 minutes ago||
Except that it's very far from guaranteed to find everything, and especially everything that humans would find easily.
vanschelven 1 hour ago|||
and C is the tinderbox
UltraSane 1 hour ago||
The billions of lines of C and C++ code is like a square lightyear of agar for LLMs to find bugs in.
UltraSane 1 hour ago||
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 1 hour ago||
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 1 hour ago||
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)
ROllerozxa 2 hours ago||
Well I guess this was the vuln that was teased about on Mastodon some hours ago:

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

codedokode 1 hour ago||
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 58 minutes ago||
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 9 minutes ago|||
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.
TZubiri 1 minute ago|||
>Python simply can't overflow, since its integral type is not a fixed width.

Python master race

8by3 1 hour ago||
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 1 hour ago||
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 41 minutes ago||
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.
yerimyerimie 2 hours ago||
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 1 hour ago||
How was this disclosure coordinated? Considering the website dropped before the official nginx patch was even released on Github...
codedokode 1 hour ago|||
Why post such exploits? What is the purpose?
voakbasda 1 hour ago||
Fame, money, and everything else those bring along for the ride.
michael-bey 2 hours ago||
[dead]
manishrana 5 minutes ago||
Everyday we are seeing new vulnerabilities. Thanks to AI
Retr0id 2 hours ago||
> Wiz Research, Ikotas Labs, Metnir, Rapid7, and Xint independently uncovered

Is this some kind of record for bug collision?

ryanschaefer 2 hours ago||
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 2 hours ago|||
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 1 hour ago||
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."

baobabKoodaa 1 hour ago|||
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 36 minutes ago|||
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 35 minutes ago|||
Cost scales with the size of your search space. Smarter questions get answers for less money & time.
MeetingsBrowser 2 hours ago|||
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?

pjungwir 1 hour ago|||
That seems likely, but maybe it was being actively exploited so several people started investigating.
cozzyd 2 hours ago|||
or maybe the model leaked the exploit from one to the other...
vel0city 2 hours ago|||
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.
mxuribe 2 hours ago|||
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 2 hours ago||
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 1 hour ago||
This was one of the takeaways from Greg Kroah-Hartman‘s recent Linux in the land of LLM keynote.
afavour 2 hours ago|||
When everyone is using the same tools for the same purpose...
puszczyk 42 minutes ago||
ugh, looks like if you still run ingress-nginx controller (you shouldn't but it was super popular in Kubernetes docs/community and there was a very little time to migrate away) you won't get these patches https://github.com/kubernetes/ingress-NGINX

edit noted it's about a Kubernetes controller

More comments...