Eliminating Memory Safety Vulnerabilities at the Source

Google outlines how prioritizing memory-safe languages for new Android development drives down memory-safety risk, citing a decline from 76% of Android vulnerabilities in 2019 to 24% in 2024. The post explains that vulnerabilities decay exponentially, so preventing new unsafe code yields rapid gains; it advocates a “Safe Coding” secure-by-design approach, emphasizes adopting Rust and Kotlin via safe interoperability with existing C++ code, highlights investments such as a $1M grant to the Rust Foundation and tooling (e.g., Crubit, autocxx), and anticipates reduced reliance on mitigations and fuzzing as prevention scales.