News for hackers. Stuff that matters.
Re:Pre-auth RCE in Nginx HTTP/2 handling by hackthemack on Wednesday November 18, 2026 @04:01PM (#50552069)
I notice a phenomena that when older software has a critical vulnerability, like say Apache, you get quite a few comments of "Why does anyone use that? Use Nginx"

But when newer software has the same vulnerability, you do not see the same kind of comments.

There always seems to be a latent stance in IT that newer is better.

Re:Pre-auth RCE in Nginx HTTP/2 handling by tredre3 on Wednesday November 18, 2026 @04:31PM (#50552385)
> But when newer software has the same vulnerability, you do not see the same kind of comments.

This isn't true! Just look at this thread, people suggest replacing nginx with newer but less widely used and less battle-tested software, as if they're superior alternatives or don't have RCEs in their own history: Envoy, caddy, traeffik, Qbix.

Re:Pre-auth RCE in Nginx HTTP/2 handling by jeroenhd on Wednesday November 18, 2026 @06:04PM (#50553628)
I can't speak for the others, but one advantage Caddy has over Nginx is that it isn't written in C.

Go isn't quite a memory safe language, but it provides fewer footguns.

On the other hand, Caddy has a lot more features, so there's more code that can contain exploits.

Re:Pre-auth RCE in Nginx HTTP/2 handling by chlorion on Wednesday November 18, 2026 @06:50PM (#50554020)
Having RCEs in general is fine. It's the rate and severity that matter.

We have evidence that large unsafe codebases suffer from more and more severe CVEs than those who are not in memory unsafe languages.

In other fields of engineering, people use stats and actually measure things like this, and use the results to determine what to do. They don't just assume something is better because its "battle tested" (whatever that even means?).

Re:Pre-auth RCE in Nginx HTTP/2 handling by cozzyd on Wednesday November 18, 2026 @08:58PM (#50555136)
I haven't even heard of any of those other than caddy...
Re:Pre-auth RCE in Nginx HTTP/2 handling by redox99 on Wednesday November 18, 2026 @04:35PM (#50552439)
I'm actually moving from nginx to Caddy after this. I'll replace all C/C++ stuff within reason.
Re:Pre-auth RCE in Nginx HTTP/2 handling by zug_zug on Wednesday November 18, 2026 @05:08PM (#50552914)
Me too. An agent was able to replace my nginx with caddy on my webserver in a few minutes.

All the remaining C code needs to die in a matter of months not years.

Re:Pre-auth RCE in Nginx HTTP/2 handling by SpaceManNabs on Wednesday November 18, 2026 @06:06PM (#50553646)
> All the remaining C code needs to die in a matter of months not years.

Why so? are most of these vulnerabilities from C's memory model?

Re:Pre-auth RCE in Nginx HTTP/2 handling by redox99 on Wednesday November 18, 2026 @06:09PM (#50553667)
Yes
Re:Pre-auth RCE in Nginx HTTP/2 handling by dtf on Wednesday November 18, 2026 @05:22PM (#50553120)
I do love Caddy. But it was vulnerable to CVE-2026-98432 a few weeks back, due to Go's MPTCP policy.
Re:Pre-auth RCE in Nginx HTTP/2 handling by jeroenhd on Wednesday November 18, 2026 @06:06PM (#50553648)
CVE-2026-98432 also applies to non-MPTCP connections. That's why disabling MPTCP was actively discouraged as a workaround (low level firewalls that clear all options do work, though, and they'd also work fine with Caddy).

Plus, Caddy itself wasn't vulnerable in this specific case. There wasn't much the Caddy folks could've done to protect against a problem in the Linux kernel itself.

Re:Pre-auth RCE in Nginx HTTP/2 handling by waterTanuki on Wednesday November 18, 2026 @08:37PM (#50554991)
surprised there hasn't been an effort to rewrite nginx or other critical networking infrastructure in Rust. We just went straight from C (nginx) to Go (Caddy/Traefik) which are not interchangeable (garbage collection).
Re:Pre-auth RCE in Nginx HTTP/2 handling by karel-3d on Wednesday November 18, 2026 @05:31PM (#50553253)
Just use Pingora. It's in Rust and from Cloudflare so it is safe. (/s but not really I guess)
Re:Pre-auth RCE in Nginx HTTP/2 handling by mbrubeck on Wednesday November 18, 2026 @06:04PM (#50553632)
Doesn't nginx count as "older software" at this point? It's over twenty years old...