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.
[ Parent
| on HN ]
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
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).