Permanent service interruption via unbounded account-data writes
Published Sep 4, 2025 · Updated Sep 4, 2025
Resource exhaustion in Android 13 through 16 AccountManagerService allows local users to cause a permanent service interruption. Multiple account-data write paths accept oversized values without per-account storage limits, allowing the AccountManager database to consume excessive storage. Low-privileged local execution is sufficient and requires no user interaction; the resulting exhaustion can leave the account service permanently unavailable.
Summary
What happened
Resource exhaustion in Android 13 through 16 AccountManagerService allows local users to cause a permanent service interruption. Multiple account-data write paths accept oversized values without per-account storage limits, allowing the AccountManager database to consume excessive storage. Low-privileged local execution is sufficient and requires no user interaction; the resulting exhaustion can leave the account service permanently unavailable.
The record
- CVE
- CVE-2025-48542
- Published
- Sep 4, 2025
- Updated
- Sep 4, 2025
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-400
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 4, 2025CVE publishedPublication date reported by the CVE source.
- Sep 4, 2025Record 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