upvote
> 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.

reply
I haven't even heard of any of those other than caddy...
reply
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.

reply
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?).

reply
I'm actually moving from nginx to Caddy after this. I'll replace all C/C++ stuff within reason.
reply
I do love Caddy. But it was vulnerable to CVE-2026-98432 a few weeks back, due to Go's MPTCP policy.
reply
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.

reply
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.

reply
> 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?

reply
Yes
reply
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).
reply
Doesn't nginx count as "older software" at this point? It's over twenty years old...
reply
Just use Pingora. It's in Rust and from Cloudflare so it is safe. (/s but not really I guess)
reply
deleted
reply