HTTP/2 is so complicated that the code that handles it tends to be vulnerable. What a surprise
This doesn’t seem very HTTP/2 specific, though, and it seems more like the conclusion should be “don’t use C for things which matter”. It’s not like HTTP pipelining and keepalives didn’t have plenty of edge cases to worry about.
Caddy also supports HTTP/2 and it's not affected.
In fact in general there were waaay less CVEs for Caddy lately compared to nginx
This doesn’t seem very HTTP/2 specific, though, and it seems more like the conclusion should be “don’t use C for things which matter”. It’s not like HTTP pipelining and keepalives didn’t have plenty of edge cases to worry about.