CVE-2026-28653
Google · Android
An integer overflow in the rw_t3t.cc component of the Android operating system leads to an out of bounds write, enabling local privilege escalation.
Executive summary
A high severity integer overflow vulnerability in Google Android allows local attackers to achieve privilege escalation without requiring user interaction.
Vulnerability
The flaw exists within multiple functions of the rw_t3t.cc source file, where an integer overflow triggers an out of bounds write. This vulnerability permits a local attacker with low privileges to escalate their permissions on the device without user interaction.
Business impact
The ability for a local attacker to escalate privileges represents a significant compromise of the device security model. Successful exploitation allows an attacker to bypass standard operating system protections, leading to full control over the local environment, potential data exfiltration, and unauthorized system modifications. With a CVSS score of 7.8, this vulnerability is categorized as high severity and poses a substantial risk to the integrity and confidentiality of mobile assets.
Remediation
Immediate Action: Apply the September 2026 Android Security Bulletin updates provided by Google or your specific device manufacturer as soon as they become available for your hardware.
Proactive Monitoring: Monitor system logs for unusual process crashes or unexpected behavioral patterns indicative of memory corruption or unauthorized privilege escalation attempts.
Compensating Controls: Ensure that Google Play Protect is enabled and that all applications are installed from verified sources to limit the initial access vector required for local exploitation.
Exploitation status
Public Exploit Available: No — exploit_available (unknown).
Analyst recommendation
This vulnerability presents a clear risk to Android device security by enabling local privilege escalation through memory corruption. Organizations managing mobile fleets should prioritize the deployment of the September 2026 security patches to all affected versions of Android. Immediate patching is the most effective method to neutralize this threat and prevent potential exploitation by malicious local actors.
More Google CVEs all →
History
CVE Brief tracked this CVE 2 days before it had a CVSS score.
- Disclosed CVE record published
- Collected by CVE Brief No CVSS score yet; tracked as early warning
- CVSS score assigned 7.8 (3.1)
- Analyst report written