CVE-2026-28600
massConfused Deputy Local Privilege Escalation in Android Payment Default Dialog
A confused deputy vulnerability in the onCreate method of PaymentDefaultDialog.java in Android allows the device's default payment app role to be changed by an application running locally on the device. Because user interaction is not required and no additional execution privileges are needed, a low-privileged app already installed on the device can trigger the flaw without any visible prompt to the user. Successful exploitation results in local escalation of privilege, with high impact to the confidentiality, integrity, and availability of the device. All Android devices shipping the affected component are potentially exposed, though the specific affected version ranges are not stated in the available data and should be confirmed via the Android Security Bulletin. As of now there are no known exploits, no public proof-of-concept, and exploitation probability is low (EPSS ~0.1%).
What to do: Apply the patched build as soon as it is distributed via the monthly Android security bulletin (OTA update); verify the device's security patch level after updating. Because exploitation requires a malicious app already running locally on the device, prioritize patching devices that install third-party or sideloaded applications, and check OEM support pages for vendor-specific patch availability.
| Google / Android Android OS (PaymentDefaultDialog component) | — |
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
In onCreate of PaymentDefaultDialog.java, there is a possible way to change default payment app 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.
- Vendors
- Products
- android
- Weakness
- CWE-441
- Vector
- CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
In the news0 stories
No ingested article mentions this CVE yet.