Local privilege escalation via activity-token leak
Published Mar 2, 2026 · Updated Mar 2, 2026
Activity-token exposure in Android 14 and 15 allows local users to gain elevated privileges through Framework task-fragment handling. The registerOrganizer, registerOrganizerInternal, prepareActivityReparentedToTask, and onActivityReparentToTask paths mishandle and expose an activity token. No existing execution privileges or user interaction is required, and the exposed token enables a local privilege boundary to be crossed.
Summary
What happened
Activity-token exposure in Android 14 and 15 allows local users to gain elevated privileges through Framework task-fragment handling. The registerOrganizer, registerOrganizerInternal, prepareActivityReparentedToTask, and onActivityReparentToTask paths mishandle and expose an activity token. No existing execution privileges or user interaction is required, and the exposed token enables a local privilege boundary to be crossed.
The record
- CVE
- CVE-2025-48635
- Published
- Mar 2, 2026
- Updated
- Mar 2, 2026
- Vendor
- Go standard library
- Product
- Android
- Classifications
- CWE-200, CWE-693, CWE-532, T1404
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 2, 2026CVE publishedPublication date reported by the CVE source.
- Mar 2, 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=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