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

Is this some kind of record for bug collision?

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

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

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

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

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

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

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

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

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

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

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

Soon you'll be building houses with it.

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

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

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

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

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

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