black3r 2 hours 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.

vanschelven 2 hours 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

verst 2 hours 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 an hour 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 an hour 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.

ChadNauseam 14 minutes ago

Another reason not to couple your software versioning to Ubuntu and Debians' package managers' schedule

ghm2199 2 hours ago

The patch gap.

SubiculumCode 2 hours 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 2 hours ago

RCE is about at the top of the stack for severity.

ArcHound 2 hours 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.

PcChip an hour ago

put up some bitcoin behind an nginx server and tell hackernews to steal it, see how long it takes

ryanisnan an hour ago

Great context. Thank you for the add.

pocksuppet 5 minutes ago

This was also true with php2shell but AI got there in the end.

lanstin an hour 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.

requeo an hour ago

These commits weren't visible until today. Yesterday, the last public commit was Nov 9.

brunoborges 26 minutes ago

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

icantevenhold 11 minutes ago

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

fduran 27 minutes ago

Small consolation but HTTP/2 is not enabled by default in Nginx and "only" 12% of servers run it (still huge at Internet scale) https://w3techs.com/technologies/segmentation/ce-http2/web_s...

fn-mote 3 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.

cute_boi 3 hours ago

Tech moves too fast and if we move too fast without doing review like 5-10 times, this will keep happening.

mynameisvlad 2 hours ago

I would hope you know that no matter how many reviews, humans are fallible and miss things.

cute_boi 2 hours ago

AI agents are also fallible? So, what do you think we should do?

mynameisvlad 2 hours 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 2 hours ago

The difference is that the AI doesn't get tired so you can review everything.

g-b-r 40 minutes ago

Except that it's very far from guaranteed to find everything, and especially everything that humans would find easily.

phkahler 2 hours 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.

anilakar 11 minutes ago

> tried and true software

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

jacobgold 2 hours 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 2 hours 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.

colechristensen 2 hours 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.

jacobgold 2 hours 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.

devy 9 minutes ago

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.

Florin_Andrei 2 hours 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 2 hours 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 34 minutes 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 an hour 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.

testtestmetest an hour ago

"Hacker gangs"

wannabe44 26 minutes ago

Well I didn't get into any trouble with the professional hacker gangs. The script kiddies on the other hand...

make3 15 minutes ago

AI is also making it much easier to attack, likely more than it's helping secure things

vanschelven 2 hours ago

and C is the tinderbox

UltraSane 2 hours ago

The billions of lines of C and C++ code is like a square lightyear of agar for LLMs to find bugs in.

codedokode 2 hours ago

Not AI but poorly designed programming languages ignoring integer overflows.

vlovich123 2 hours 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.

tptacek 2 hours 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 2 hours 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 2 hours 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.

codedokode 2 hours 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 2 hours 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 2 hours ago

How does that saying go?

"Go fast and get your things broken into"

10000truths 2 hours ago

Zig traps arithmetic overflow/underflow when compiling in ReleaseSafe.

BoingBoomTschak an hour 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.

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

rlt 2 hours 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 2 hours ago

And your first thought was the NSA? Patching and adding their own rootkit eh?

zzril 2 hours ago

Don't you dare patching my honeypots!

UltraSane 2 hours 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 2 hours 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 2 hours 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)

fla 2 hours 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.

zodwick 2 hours ago

There is going to be hardships before this gets better. But it is hardship we must endure

jooops1 an hour 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.

tgv 30 minutes ago

It's like blaming people for having wooden doors when robots with chainsaws start appearing in the street.

jethro_tell 19 minutes ago

When 85 percent of doors were installed before metal doors were available.

streetfighter64 9 minutes ago

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.

dilyevsky an hour 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.

gspr an hour 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.

worldsavior an hour ago

This comment is very dramatic and very hype-y. I don't think this is an appropriate comment.

pelzatessa 14 minutes ago

If you want to check if your host might be vulnerable:

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

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

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

ROllerozxa 3 hours ago

Well I guess this was the vuln that was teased about on Mastodon some hours ago:

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

8by3 2 hours 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 2 hours 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 an hour 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.

codedokode 2 hours 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 2 hours 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 43 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 35 minutes ago

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

Python master race

yerimyerimie 3 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 2 hours ago

How was this disclosure coordinated? Considering the website dropped before the official nginx patch was even released on Github...

codedokode 2 hours ago

Why post such exploits? What is the purpose?

voakbasda 2 hours ago

Fame, money, and everything else those bring along for the ride.

goodmythical 15 minutes ago

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.

rs_rs_rs_rs_rs 10 minutes ago

I agree, never post anything you find, keep all the bugs to yourself, write reliable exploits who knows when you would need one.

streetfighter64 6 minutes ago

Seems like you're a fan of security by obscurity over secure code?

Retr0id 3 hours ago

> Wiz Research, Ikotas Labs, Metnir, Rapid7, and Xint independently uncovered

Is this some kind of record for bug collision?

MeetingsBrowser 3 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?

cozzyd 3 hours ago

or maybe the model leaked the exploit from one to the other...

mxuribe 3 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 3 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 2 hours ago

This was one of the takeaways from Greg Kroah-Hartman‘s recent Linux in the land of LLM keynote.

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

pjungwir 2 hours ago

That seems likely, but maybe it was being actively exploited so several people started investigating.

ryanschaefer 3 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 3 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 2 hours 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 2 hours 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 an hour 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 an hour ago

Cost scales with the size of your search space. Smarter questions get answers for less money & time.

afavour 3 hours ago

When everyone is using the same tools for the same purpose...

Juvination 2 hours ago

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 2 hours ago

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

hosteur 3 hours ago

So work around is to disable http/2 and only allow http/1.1?

Simber 3 hours ago

Yep, that or update to 1.31.9+ or 1.30.7+ if they are available in your distro

kijin 2 hours ago

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 2 hours ago

There isn't even a mail about this on oss-security, as of now.

cm2187 5 minutes ago

Unless I am confused, it doesn't look like ubuntu server has made available the fix.

dboreham 3 hours ago

The AI gods say that http/2 is disabled in a default installation fwiw.

antiloper 3 hours ago

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 an hour ago

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.

yread 2 hours ago

My Apaches still have http2 disabled from the last cve, now its njinx time

kijin an hour ago

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

puszczyk an hour 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

andrelaszlo an hour ago

I assume OpenResty is affected as well? ("High Performance Web Platform Based on Nginx and LuaJIT")

pelzatessa an hour ago

OPs article mentions 2 CVEs, however this one claims that there are 5 new ones: https://news.ycombinator.com/item?id=50547423

hacker_homie an hour ago

This sound suspiciously similar to the issue Microsoft said they were dealing with excess traffic on their front door, taking them down. maybe not an RCE but a DOS in the same http/tls code.

0xBA5ED an hour ago

Imagine there are 1 million things to know. Some of them are related but most of them aren't. Now imagine that you know 10 things.

jascha_eng 3 hours ago

Never turned http2 on in my side project pfew. But still, this is one is pretty rough...

koolba 3 hours ago

This whole week is rough. And it’s only Wed.

jascha_eng 3 hours ago

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 3 hours ago

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 3 hours ago

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

tancop 2 hours ago

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 2 hours ago

HTTP/1.1 is still way better and way simpler than HTTP/3.

seki285 2 hours ago

Could you please share why?

lysace an hour ago

~25 years of hardening.

gkbrk an hour ago

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 19 minutes ago

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.

layer8 an hour ago

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 an hour ago

Because HTTP3 was implemented without any errors? Citation needed I guess.

manishrana 39 minutes ago

Everyday we are seeing new vulnerabilities. Thanks to AI

insanitybit 28 minutes ago

Did AI write this vuln?

hokkos 2 hours ago

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

leca 4 hours ago

How many hours before this is exploited in the wild ? Probably not all that long, that blog has a significant amount of details.

lwarfield 3 hours ago

One tops

LeonM 2 hours ago

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

testtestmetest 22 minutes ago

To all the people here that would like to give AI credit for everything, and dont think it matters that everyone at Wiz is Israel Ex Cyber "Defense", and all you need is AI to find things like this. I have a challenge for you:

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

wasmitnetzen 3 hours ago

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

Cue xkcd

TZubiri 36 minutes ago

Hey this is TZubiri, the guy that comments that you should uninstall the dep whenever there is an post about a CVSS 9+ vuln.

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

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

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

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

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

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

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

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

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

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

FLeXMurphy 38 minutes ago

Is this going to end up being another exploit that requires a ridiculous amounts of special conditions so as to not actually be applicable to majority of sites running nginx?

therepanic 2 hours ago

What’s the point of these researchers if their autonomous system is now finding these vulnerabilities?

pixl97 2 hours ago

Making sure AI isn't hallucinating.