This isn't a newly discovered problem - I worked at Microsoft in the early 2000's and was part of the group that released something called "Safe CPP Runtime" library. Doing simple pointer validation and bounds checking of structures and objects among other validations developers were required to use for Windows app development. This reduced the easy path for hackers and made Windows XP much much safer *assuming* developers used this library and not some open source variant.

I'm a bit shocked that the c++ community hasn't already gone the lengths to fully implement secure memory management by now. We don't need yet another programming language to further dilute this sector. C++ has been IMHO the defacto language that is performant in all environments and assuming developers are disciplined in code practices can meet the requirements for safety. It's developer habits that should be corrected to make sure we're not creating a generation of engineers not willing to safeguard their work against maladroit actors.