News for hackers. Stuff that matters.
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...