dbcve.org
AndroidOperating system · Google

CVE-2025-0086

MEDIUM · 6.2 CVSS v3.1 Published 2025-08-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/100
Remediation priority · Elevated
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In onResult of AccountManagerService.java, there is a possible way to overwrite auth token due to a missing permission check. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A missing permission check in the onResult method of AccountManagerService.java allows local attackers to overwrite authentication tokens without proper authorization. This enables local information disclosure as attackers can manipulate auth tokens to gain unauthorized access to account data.

MitigationImplement proper permission verification in the onResult callback of AccountManagerService.java to validate caller identity before allowing auth token modifications.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AndroidOperating system
Affected:= 12.0= 12.1= 13.0= 14.0= 15.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Android OS version
    Go to Settings > About Phone > Android version (or run 'getprop ro.build.version.release' via ADB)
    Affected if The installed Android version is 12.0, 12.1, 13.0, 14.0, or 15.0
  2. Verify AccountManagerService permission configuration
    Inspect the AccountManagerService.java source code or decompiled APK to confirm if onResult method includes a permission check (e.g., checkCallingPermission) before processing auth token modifications
    Affected if The onResult callback lacks proper permission verification and the device runs an affected Android version
  3. Audit installed apps with account permissions
    Run 'adb shell pm list permissions -g' and look for apps granted android.permission.GET_ACCOUNTS or android.permission.MANAGE_ACCOUNTS permissions, or inspect using Settings > Apps > Permissions
    Affected if Any app without legitimate need holds account management permissions and the device is on an affected Android version
  4. Review account access logs
    Check logcat output for AccountManager operations (filter: 'AccountManagerService') or review system audit logs for unauthorized auth token modification attempts
    Affected if Unusual or unauthorized auth token write operations are observed from apps other than system components

The device is affected if it runs Android 12.0, 12.1, 13.0, 14.0, or 15.0 and the AccountManagerService onResult method lacks permission checks for auth token modifications.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper permission verification in the onResult callback of AccountManagerService.java to validate caller identity before allowing auth token modifications.

Recommended fix Moderate confidence

Android 15 (API level 35) or later security patch

  1. 1. Verify the current Android version on the affected device by navigating to Settings > About Phone > Android version
  2. 2. Check if a newer Android version (15.0 or higher) is available for your device through Settings > System > Software Update
  3. 3. If Android 15 is available, perform a full backup of device data before upgrading
  4. 4. Apply the system update to receive the security patch containing the fix for CVE-2025-0086
  5. 5. After updating, verify the Android version has changed to 15.0 or later and confirm the security patch level is current
Caveat Upgrading to Android 15 may introduce UI changes, remove support for older apps not compatible with the new API level, and require re-authentication for some accounts

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-0086 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-0086 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data