CVE-2025-32346
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 · uneditedIn onActivityResult of VoicemailSettingsActivity.java, there is a possible work profile contact number leak due to a confused deputy. 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 confidenceA confused deputy vulnerability in Android's VoicemailSettingsActivity allows a malicious local application to intercept work profile contact numbers through the onActivityResult callback. The component improperly trusts intent data without validating the calling identity, enabling a local attacker to escalate privileges and access sensitive work profile data without user interaction.
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= 16.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Android versionGo to Settings > About Phone > Android version. Confirm the installed version is exactly 16.0.Affected if Android version is exactly 16.0 and no June 2025 or later security patch has been applied.
-
Check work profile statusOn the device, go to Settings > Accounts > Work profile. Determine if a work profile is configured and active.Affected if A work profile is enabled, as the vulnerability specifically targets work profile contact data.
-
Inspect VoicemailProvider permissionsUse ADB command: 'adb shell dumpsys package com.android.phone | grep -i voicemail' to check if third-party apps hold the VoicemailProvider permission.Affected if Any application other than the system Phone app holds the VoicemailProvider permission.
-
Review app package visibilityUse ADB: 'adb shell pm list packages -3' to enumerate third-party installed apps. Cross-reference with any apps requesting VOICEMAIL permission in their manifest.Affected if A non-system application with VoicemailProvider permission is installed on the device.
-
Check security patch levelGo to Settings > About Phone > Security Patch Level. Verify if the installed patch level predates June 2025.Affected if Security patch level is May 2025 or earlier, meaning the vulnerability remains unpatched.
A user is affected if their device runs Android 16.0 with a work profile configured and a security patch level earlier than June 2025, especially if unknown third-party apps hold VoicemailProvider permissions.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply the Android security patch level for June 2025 or later. For enterprise environments, MDM solutions should enforce work profile containerization policies and monitor for applications requesting VoicemailProvider permissions.
- Consultation8.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32346 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-32346 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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