> The GP might have gone a hair too far in saying that C++ “does not consider it a problem at all”, but they’re correct that C++ compiler/stdlib maintainers do

> The GP might have gone a hair too far in saying that C++ “does not consider it a problem at all”, but they’re correct that C++ compiler/stdlib maintainers do not consider it a vulnerability. No this is also just plain wrong. It was reported to both compiler through channels dedicated to report security vulnerabilities and has been fixed as such. The fact it did not make his way through a CVE is mainly related to how CVE naming and reservation works, nothing more.