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