Local privilege escalation via ignored one-time flag
Published Sep 2, 2025 · Updated Feb 26, 2026
Privilege escalation in Android 13 through 15 allows local users to override user-selected location permissions without interaction. The Permission Controller role logic in Permissions.java protects USER_SET choices but omitted ONE_TIME, so role grants could replace an ask-every-time selection. A low-privileged local app is sufficient, and exploitation changes the location-permission state to obtain additional privileges without user action.
Summary
What happened
Privilege escalation in Android 13 through 15 allows local users to override user-selected location permissions without interaction. The Permission Controller role logic in Permissions.java protects USER_SET choices but omitted ONE_TIME, so role grants could replace an ask-every-time selection. A low-privileged local app is sufficient, and exploitation changes the location-permission state to obtain additional privileges without user action.
The record
- CVE
- CVE-2024-49720
- Published
- Sep 2, 2025
- Updated
- Feb 26, 2026
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-693, T1404
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 2, 2025CVE publishedPublication date reported by the CVE source.
- Feb 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=13
- Affected versionversion=14
- Affected versionversion=15
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo