News for hackers. Stuff that matters.
Re:Pre-auth RCE in Nginx HTTP/2 handling by black3r on Wednesday November 18, 2026 @11:43AM (#50548510)
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.

Re:Pre-auth RCE in Nginx HTTP/2 handling by vanschelven on Wednesday November 18, 2026 @11:49AM (#50548592)
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
Re:Pre-auth RCE in Nginx HTTP/2 handling by Gigachad on Wednesday November 18, 2026 @08:19PM (#50554825)
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.
Re:Pre-auth RCE in Nginx HTTP/2 handling by verst on Wednesday November 18, 2026 @12:08PM (#50548865)
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.
Re:Pre-auth RCE in Nginx HTTP/2 handling by meowface on Wednesday November 18, 2026 @12:50PM (#50549561)
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.
Re:Pre-auth RCE in Nginx HTTP/2 handling by black3r on Wednesday November 18, 2026 @12:58PM (#50549685)
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.
Re:Pre-auth RCE in Nginx HTTP/2 handling by ChadNauseam on Wednesday November 18, 2026 @01:53PM (#50550467)
[delayed]
Re:Pre-auth RCE in Nginx HTTP/2 handling by sippingabonedry on Wednesday November 18, 2026 @02:03PM (#50550582)
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.

Re:Pre-auth RCE in Nginx HTTP/2 handling by nsoam on Wednesday November 18, 2026 @02:08PM (#50550640)
...or you could use Gentoo.
Re:Pre-auth RCE in Nginx HTTP/2 handling by antonvs on Wednesday November 18, 2026 @02:21PM (#50550776)
Keep the flame alive!
Re:Pre-auth RCE in Nginx HTTP/2 handling by robotmay on Wednesday November 18, 2026 @02:40PM (#50551064)
Embrace true chaos and let an LLM do the config file merges for you in Portage.
Re:Pre-auth RCE in Nginx HTTP/2 handling by bombcar on Wednesday November 18, 2026 @06:52PM (#50554035)
LLMs love gentoo they go hog wild.

Which may be good or bad.

Re:Pre-auth RCE in Nginx HTTP/2 handling by mikepurvis on Wednesday November 18, 2026 @02:16PM (#50550720)
NixOS is probably the best modern option for those who crave building the whole world from source.
Re:Pre-auth RCE in Nginx HTTP/2 handling by prennert on Wednesday November 18, 2026 @02:32PM (#50550942)
yep, already deployed fixes to our fleet (NixOS for the win)
Re:Pre-auth RCE in Nginx HTTP/2 handling by kd913 on Wednesday November 18, 2026 @05:44PM (#50553418)
Or just use it in a podman quadlet?

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

Re:Pre-auth RCE in Nginx HTTP/2 handling by usr1106 on Wednesday November 18, 2026 @09:38PM (#50555376)
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.

Re:Pre-auth RCE in Nginx HTTP/2 handling by xorcist on Wednesday November 18, 2026 @02:14PM (#50550693)
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.

Re:Pre-auth RCE in Nginx HTTP/2 handling by antonvs on Wednesday November 18, 2026 @02:22PM (#50550797)
It makes more sense to install services like nginx via the official containers. In the modern world, the OS is for base services only.
Re:Pre-auth RCE in Nginx HTTP/2 handling by raegis on Wednesday November 18, 2026 @05:23PM (#50553137)
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.
Re:Pre-auth RCE in Nginx HTTP/2 handling by kd913 on Wednesday November 18, 2026 @05:47PM (#50553450)
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.

Re:Pre-auth RCE in Nginx HTTP/2 handling by subsection1h on Wednesday November 18, 2026 @07:08PM (#50554172)
> Podman container auto-updates to the latest upstream

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

Re:Pre-auth RCE in Nginx HTTP/2 handling by jamesfinlayson on Wednesday November 18, 2026 @09:10PM (#50555204)
Agreed. At a previous job all the important stuff came from repos that always shipped latest.
Re:Pre-auth RCE in Nginx HTTP/2 handling by newsoftheday on Wednesday November 18, 2026 @02:31PM (#50550938)
This looks like it was patched in Ubuntu on the 12th?

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

Re:Pre-auth RCE in Nginx HTTP/2 handling by man8alexd on Wednesday November 18, 2026 @02:39PM (#50551048)
This Ubuntu security notice is about an Apache vulnerability, not nginx.
Re:Pre-auth RCE in Nginx HTTP/2 handling by kayfox on Wednesday November 18, 2026 @02:40PM (#50551063)
> Several security issues were fixed in Apache HTTP Server.

Um, what does this have to do with NGINX?

Re:Pre-auth RCE in Nginx HTTP/2 handling by baggy_trough on Wednesday November 18, 2026 @02:45PM (#50551128)
Re:Pre-auth RCE in Nginx HTTP/2 handling by magahugu on Wednesday November 18, 2026 @05:39PM (#50553345)
Good to see
Re:Pre-auth RCE in Nginx HTTP/2 handling by oddIdentities on Wednesday November 18, 2026 @04:07PM (#50552119)
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.

Re:Pre-auth RCE in Nginx HTTP/2 handling by fhub on Wednesday November 18, 2026 @06:27PM (#50553813)
FWIW, for nodes that don't have packages, I compiled from source under /opt and deploy scripts check higher version so it will auto switch back when the new packages are installed.
Re:Pre-auth RCE in Nginx HTTP/2 handling by mediaserf on Wednesday November 18, 2026 @10:15PM (#50555606)
You can also add nginx.org repos and install the updated versions from there. https://nginx.org/en/linux_packages.html
Re:Pre-auth RCE in Nginx HTTP/2 handling by hiddenvulkcan on Wednesday November 18, 2026 @02:12PM (#50550680)
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
Re:Pre-auth RCE in Nginx HTTP/2 handling by throwitaway222 on Wednesday November 18, 2026 @02:16PM (#50550713)
I told me agent to do that - similar situation.
Re:Pre-auth RCE in Nginx HTTP/2 handling by TedDoesntTalk on Wednesday November 18, 2026 @04:24PM (#50552304)
> me agent

Did you talk to it like a pirate?

Re:Pre-auth RCE in Nginx HTTP/2 handling by hiddenvulkcan on Wednesday November 18, 2026 @05:23PM (#50553135)
New caveman version just dropped! /Pirate
Re:Pre-auth RCE in Nginx HTTP/2 handling by dboreham on Wednesday November 18, 2026 @07:08PM (#50554176)
There are large areas of the English speaking world where this is common speech.
Re:Pre-auth RCE in Nginx HTTP/2 handling by Ikersl on Wednesday November 18, 2026 @04:46PM (#50552609)
Definitely, but unfortunately I use Debian for my servers so.
Re:Pre-auth RCE in Nginx HTTP/2 handling by weitendorf on Wednesday November 18, 2026 @02:34PM (#50550971)
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

Re:Pre-auth RCE in Nginx HTTP/2 handling by trey-jones on Wednesday November 18, 2026 @03:49PM (#50551940)
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.
Re:Pre-auth RCE in Nginx HTTP/2 handling by weitendorf on Wednesday November 18, 2026 @04:02PM (#50552092)
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.

Re:Pre-auth RCE in Nginx HTTP/2 handling by TedDoesntTalk on Wednesday November 18, 2026 @04:20PM (#50552267)
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.
Re:Pre-auth RCE in Nginx HTTP/2 handling by weitendorf on Wednesday November 18, 2026 @04:46PM (#50552608)
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.

Re:Pre-auth RCE in Nginx HTTP/2 handling by technion on Wednesday November 18, 2026 @05:04PM (#50552862)
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.

Re:Pre-auth RCE in Nginx HTTP/2 handling by Lucasoato on Wednesday November 18, 2026 @04:54PM (#50552738)
Does Envoy support things like rate limiting?
Re:Pre-auth RCE in Nginx HTTP/2 handling by weitendorf on Wednesday November 18, 2026 @05:03PM (#50552840)
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...

Re:Pre-auth RCE in Nginx HTTP/2 handling by fcantournet on Wednesday November 18, 2026 @08:12PM (#50554752)
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.
Re:Pre-auth RCE in Nginx HTTP/2 handling by verst on Wednesday November 18, 2026 @06:23PM (#50553781)
I am using Envoy :)
Re:Pre-auth RCE in Nginx HTTP/2 handling by voodooEntity on Wednesday November 18, 2026 @06:26PM (#50553804)
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
Re:Pre-auth RCE in Nginx HTTP/2 handling by weitendorf on Wednesday November 18, 2026 @06:46PM (#50553980)
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.

Re:Pre-auth RCE in Nginx HTTP/2 handling by chanux on Wednesday November 18, 2026 @09:55PM (#50555485)
I wonder if being prepared to switch the reverse proxy you use in whim is a good strategy in this climate.
Re:Pre-auth RCE in Nginx HTTP/2 handling by trollbridge on Wednesday November 18, 2026 @11:16PM (#50556015)
A while ago I started releasing our stuff with dual stacks (originally nginx and haproxy, more recently added traefik to the list).
Re:Pre-auth RCE in Nginx HTTP/2 handling by ktm5j on Wednesday November 18, 2026 @02:51PM (#50551202)
If you're using httpd just fyi - there was a recent RCE vuln for apache that was also http2 specific.
Re:Pre-auth RCE in Nginx HTTP/2 handling by geocar on Wednesday November 18, 2026 @10:59PM (#50555916)
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.

Re:Pre-auth RCE in Nginx HTTP/2 handling by ghm2199 on Wednesday November 18, 2026 @12:12PM (#50548961)
The patch gap.
Re:Pre-auth RCE in Nginx HTTP/2 handling by SubiculumCode on Wednesday November 18, 2026 @12:16PM (#50549025)
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.
Re:Pre-auth RCE in Nginx HTTP/2 handling by ryanisnan on Wednesday November 18, 2026 @12:25PM (#50549168)
RCE is about at the top of the stack for severity.
Re:Pre-auth RCE in Nginx HTTP/2 handling by ArcHound on Wednesday November 18, 2026 @12:30PM (#50549252)
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.
Re:Pre-auth RCE in Nginx HTTP/2 handling by PcChip on Wednesday November 18, 2026 @12:51PM (#50549581)
put up some bitcoin behind an nginx server and tell hackernews to steal it, see how long it takes
Re:Pre-auth RCE in Nginx HTTP/2 handling by wildmXranat on Wednesday November 18, 2026 @02:48PM (#50551168)
:) 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
Re:Pre-auth RCE in Nginx HTTP/2 handling by ryanisnan on Wednesday November 18, 2026 @01:13PM (#50549884)
Great context. Thank you for the add.
Re:Pre-auth RCE in Nginx HTTP/2 handling by pocksuppet on Wednesday November 18, 2026 @02:02PM (#50550565)
This was also true with php2shell but AI got there in the end.
Re:Pre-auth RCE in Nginx HTTP/2 handling by smallerize on Wednesday November 18, 2026 @02:31PM (#50550927)
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"
Re:Pre-auth RCE in Nginx HTTP/2 handling by mountainro53 on Wednesday November 18, 2026 @03:51PM (#50551959)
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.
Re:Pre-auth RCE in Nginx HTTP/2 handling by Gigachad on Wednesday November 18, 2026 @08:17PM (#50554802)
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..

Re:Pre-auth RCE in Nginx HTTP/2 handling by lanstin on Wednesday November 18, 2026 @01:17PM (#50549942)
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.
Re:Pre-auth RCE in Nginx HTTP/2 handling by requeo on Wednesday November 18, 2026 @01:15PM (#50549906)
These commits weren't visible until today. Yesterday, the last public commit was Nov 9.
Re:Pre-auth RCE in Nginx HTTP/2 handling by TedDoesntTalk on Wednesday November 18, 2026 @04:25PM (#50552318)
How is that done with git?
Re:Pre-auth RCE in Nginx HTTP/2 handling by jen729w on Wednesday November 18, 2026 @04:31PM (#50552386)
Just don't push upstream?
Re:Pre-auth RCE in Nginx HTTP/2 handling by TedDoesntTalk on Wednesday November 18, 2026 @01:27PM (#50550079)
Re:Pre-auth RCE in Nginx HTTP/2 handling by brunoborges on Wednesday November 18, 2026 @01:41PM (#50550292)
> 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.

Re:Pre-auth RCE in Nginx HTTP/2 handling by antonvs on Wednesday November 18, 2026 @02:22PM (#50550804)
How's that alignment going...
Re:Pre-auth RCE in Nginx HTTP/2 handling by rheisen_ on Wednesday November 18, 2026 @02:45PM (#50551135)
As much as I like open weight models.. what alignment lol
Re:Pre-auth RCE in Nginx HTTP/2 handling by icantevenhold on Wednesday November 18, 2026 @01:56PM (#50550500)
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

Re:Pre-auth RCE in Nginx HTTP/2 handling by Aperocky on Wednesday November 18, 2026 @02:04PM (#50550593)
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.
Re:Pre-auth RCE in Nginx HTTP/2 handling by icantevenhold on Wednesday November 18, 2026 @03:45PM (#50551899)
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
Re:Pre-auth RCE in Nginx HTTP/2 handling by antonvs on Wednesday November 18, 2026 @02:23PM (#50550814)
> Seriously reconsidering if open source has a future nowadays

*In C or C++.

Re:Pre-auth RCE in Nginx HTTP/2 handling by pjmlp on Wednesday November 18, 2026 @02:42PM (#50551099)
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.

Re:Pre-auth RCE in Nginx HTTP/2 handling by anthk on Wednesday November 18, 2026 @04:31PM (#50552398)
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.

Re:Pre-auth RCE in Nginx HTTP/2 handling by pjmlp on Wednesday November 18, 2026 @05:21PM (#50553108)
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.

Re:Pre-auth RCE in Nginx HTTP/2 handling by gmueckl on Wednesday November 18, 2026 @02:52PM (#50551225)
rust isn't invulnerable.
Re:Pre-auth RCE in Nginx HTTP/2 handling by sophacles on Wednesday November 18, 2026 @03:38PM (#50551827)
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.
Re:Pre-auth RCE in Nginx HTTP/2 handling by hunterpayne on Wednesday November 18, 2026 @06:09PM (#50553666)
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.
Re:Pre-auth RCE in Nginx HTTP/2 handling by openasocket on Wednesday November 18, 2026 @07:09PM (#50554189)
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
Re:Pre-auth RCE in Nginx HTTP/2 handling by dralley on Wednesday November 18, 2026 @09:56PM (#50555488)
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.

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.

Re:Pre-auth RCE in Nginx HTTP/2 handling by hunterpayne on Wednesday November 18, 2026 @06:07PM (#50553653)
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.

Re:Pre-auth RCE in Nginx HTTP/2 handling by perlgeek on Wednesday November 18, 2026 @02:29PM (#50550899)
So what happens when somebody tries to contribute based on the last-published commit? Do you merge/rebase their contributions for them?
Re:Pre-auth RCE in Nginx HTTP/2 handling by icantevenhold on Wednesday November 18, 2026 @03:44PM (#50551881)
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

Re:Pre-auth RCE in Nginx HTTP/2 handling by mort96 on Wednesday November 18, 2026 @04:08PM (#50552137)
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.

Re:Pre-auth RCE in Nginx HTTP/2 handling by baq on Wednesday November 18, 2026 @04:17PM (#50552238)
Amounts to ‘won’t be getting contributions‘ which is maybe not that bad at this point on the timeline
Re:Pre-auth RCE in Nginx HTTP/2 handling by mort96 on Wednesday November 18, 2026 @04:26PM (#50552328)
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
Re:Pre-auth RCE in Nginx HTTP/2 handling by icantevenhold on Wednesday November 18, 2026 @08:50PM (#50555086)
We do have a LLM disclosure policy.

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

Re:Pre-auth RCE in Nginx HTTP/2 handling by seba_dos1 on Wednesday November 18, 2026 @10:26PM (#50555696)
You only need to enforce it enough to fulfill its goals.

https://xkcd.com/810/

Re:Pre-auth RCE in Nginx HTTP/2 handling by cluckindan on Wednesday November 18, 2026 @04:58PM (#50552776)
The future is in closed source ecosystems on a modified Harvard architecture
Re:Pre-auth RCE in Nginx HTTP/2 handling by davidkwast on Wednesday November 18, 2026 @07:16PM (#50554251)
WTF but I get the point
Re:Pre-auth RCE in Nginx HTTP/2 handling by kbolino on Wednesday November 18, 2026 @08:12PM (#50554753)
The actual behavior of a running system is extremely data-dependent. There is no security-relevant distinction between Harvard and modern von Neumann architectures anymore, and it's arguable that there ever was one in the first place.
Re:Pre-auth RCE in Nginx HTTP/2 handling by jamesfinlayson on Wednesday November 18, 2026 @09:15PM (#50555229)
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.

Re:Pre-auth RCE in Nginx HTTP/2 handling by a34729t on Wednesday November 18, 2026 @03:25PM (#50551662)
Oh everybody worth worrying about is monitoring this on every major repo already.
Re:Pre-auth RCE in Nginx HTTP/2 handling by EGreg on Wednesday November 18, 2026 @03:32PM (#50551748)
HTTP/2 is usually the source of most of these bugs in webservers of all kinds
Re:Pre-auth RCE in Nginx HTTP/2 handling by OJFord on Wednesday November 18, 2026 @05:58PM (#50553566)
Yes, fixing open source software is at most an obfuscated announcement.