News for hackers. Stuff that matters.
Re:Pre-auth RCE in Nginx HTTP/2 handling by jtmarmon on Wednesday November 18, 2026 @04:25PM (#50552326)
It's not possible. It generally requires more work to find an exploit than to patch the (known) exploit.

Now, you could argue that writing secure code ex-ante is harder than discovering an exploit. But you can hypothetically run the same "exploit finding" process on a first pass of code before it ships (e.g on the PR) given low enough token costs, which is where we're headed.

Re:Pre-auth RCE in Nginx HTTP/2 handling by tripleee on Wednesday November 18, 2026 @04:29PM (#50552377)
How do you know when the "exploit finding" pass is done? A hacker group would happily burn a month or more of tokens trying to break a critical piece of software.
Re:Pre-auth RCE in Nginx HTTP/2 handling by HappyDreamer on Wednesday November 18, 2026 @04:47PM (#50552622)
> It generally requires more work to find an exploit than to patch the (known) exploit.

Not sure if that's true, but in any case, you seem to forget:

When the hackers have breached something, awaits a reward.

E.g. a Bitcoin wallet, or learning something about a political competitor and getting rid of them.

(So the hackers can spend lots of ...)