upvote
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