In setDefaultKey of DefaultPaymentSettings.java, there is a possible way for an application to set the main user's default NFC payment setting due to improper input validation. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2025-48612US | high7.8 | — | ||
In setDefaultKey of DefaultPaymentSettings.java, there is a possible way for an application to set the main user's default NFC payment setting due to improper input validation. Thi… | ||||
02
references
External citations — patches, advisories, analysis.
- https://android.googlesource.com/platform/packages/apps/Settings/+/46ddb9d440cad942163700985242d2206f29cc40FIX
- https://android.googlesource.com/platform/packages/apps/Settings/+/94c4cecfe4aff8e558bfc25054b60ee7cd9b11c4FIX
- https://android.googlesource.com/platform/packages/apps/Settings/+/aa744e8988f0e7b77a71087edd4d2546b58d2f24FIX
- https://android.googlesource.com/platform/packages/apps/Settings/+/f2babe193c762ee4ee1b03a77e55d4a4acb1f3b0FIX
- https://source.android.com/security/bulletin/2026-06-01ADVISORY
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan