Local privilege escalation via unbounded display name
Published Sep 4, 2025 · Updated Feb 26, 2026
Protection mechanism failure in Android 13 through 16 allows local users to retain Companion Device Manager associations via long display names. AssociationRequest.setDisplayName accepts app-supplied names longer than 1,024 characters, allowing the app to retain its Companion Device Manager association. A locally installed app with low privileges can exploit the flaw without user interaction and retain association-backed elevated access.
Summary
What happened
Protection mechanism failure in Android 13 through 16 allows local users to retain Companion Device Manager associations via long display names. AssociationRequest.setDisplayName accepts app-supplied names longer than 1,024 characters, allowing the app to retain its Companion Device Manager association. A locally installed app with low privileges can exploit the flaw without user interaction and retain association-backed elevated access.
The record
- CVE
- CVE-2025-48522
- Published
- Sep 4, 2025
- Updated
- Feb 26, 2026
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-693, T1404
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 4, 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
- Affected versionversion=16
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