dbcve.org
AndroidOperating system · Google

CVE-2025-32345

HIGH · 7.8 CVSS v3.1 Published 2025-09-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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 updateState of ContentProtectionTogglePreferenceController.java, there is a possible way for a secondary user to disable the primary user's deceptive app scanning setting due to a logic error in the code. This could lead to local escalation of privilege 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 logic error in the updateState method of ContentProtectionTogglePreferenceController.java allows a secondary user to disable the primary user's deceptive app scanning setting. This improper access control enables local privilege escalation where one user can modify security settings intended for another user.

MitigationApply the vendor patch when released; until then, monitor for unauthorized changes to content protection settings and restrict secondary user access where feasible.

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:= 15.0= 16.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Identify Android version
    Run 'getprop ro.build.version.release' or check Settings > About Phone > Android version. Compare to affected versions 15.0 and 16.0.
    Affected if Android version is exactly 15.0 or 16.0
  2. Check for multiple user accounts
    Run 'pm list users' or check Settings > Accounts > Multiple users. Determine if secondary users exist on the device.
    Affected if Multiple user accounts are configured on the device
  3. Verify deceptive app scanning status
    Check Settings > Google > Safe Browsing or equivalent content protection setting. Note whether deceptive app scanning is enabled.
    Affected if Content protection/deceptive app scanning setting is present and was potentially modified by an unauthorized user
  4. Audit content protection preference changes
    Review system logs (logcat) for changes to ContentProtectionTogglePreferenceController or content protection settings. Look for events from secondary user sessions.
    Affected if Logs show content protection settings were modified from a non-owner user session

A user is affected if their Android device runs version 15.0 or 16.0, has multiple user accounts configured, and the deceptive app scanning setting may have been altered by a secondary user.

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

Apply the vendor patch when released; until then, monitor for unauthorized changes to content protection settings and restrict secondary user access where feasible.

Recommended fix Moderate confidence

Latest Android security patch level (Android 15.0+ with subsequent security updates)

  1. Check for and install the latest Android system updates via Settings > System > Software Update > Check for updates
  2. If an over-the-air update is not available, contact the device manufacturer or carrier for patch availability
  3. Ensure Android system is updated to a version newer than 15.0 and 16.0 that includes the security fix for this vulnerability
Caveat Standard upgrade risks apply - ensure user data is backed up before updating

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

Fix this in Android Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32345 — 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-32345 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