6 min read
|
Saved February 14, 2026
|
Copied!
Do you care about this?
Google reports significant gains in memory safety by adopting Rust for Android development. Memory safety vulnerabilities dropped below 20% for the first time, and Rust's code changes are not only safer but also faster to implement, showing a marked reduction in rollback rates and code review times.
If you do, here's more
Google's adoption of Rust in Android development is yielding impressive results, particularly in memory safety and software delivery speed. For the first time, memory safety vulnerabilities in the Android platform have dropped below 20% of total vulnerabilities. The data for 2025 indicates that Rust has achieved a 1000x reduction in memory safety vulnerability density compared to C and C++. Not only is Rust making Android more secure, but itβs also speeding up the development process. Changes made in Rust have a rollback rate four times lower than those in C++, and they spend 25% less time in code review.
The analysis focuses on first-party code changes, highlighting a significant shift toward Rust. As Rust's usage rises, the decline in new C++ code becomes more pronounced. Google has been tracking development metrics using the DORA framework, which evaluates software engineering performance in terms of throughput and stability. Rust code requires fewer revisions and demonstrates a much lower rollback rate, which enhances overall productivity and reduces disruptions caused by faulty changes. Engineers have reported that Rust is easier to review and tends to produce correct code more consistently.
Google is expanding Rust's role beyond just Android system services. The Linux kernel now supports Rust, and there's ongoing work on a Rust-based kernel-mode GPU driver. Rust is also being deployed in firmware, addressing security concerns in high-risk environments. Notable applications like Google Play Services and the upcoming Google Messages app are implementing Rust for critical security features. Despite these advancements, Google acknowledges that memory-safe languages are just one aspect of a broader strategy for memory safety, underscoring their commitment to a multi-layered security approach.
Questions about this article
No questions yet.