CVE-2025-48612
Modified Modified - Updated After Analysis
BaseFortify

Publication date: 2025-12-08

Last updated on: 2026-06-01

Assigner: Android (associated with Google Inc. or Open Handset Alliance)

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-12-08
Last Modified
2026-06-01
Generated
2026-06-16
AI Q&A
2025-12-08
EPSS Evaluated
2026-06-15
NVD
Affected Vendors & Products
Showing 4 associated CPEs
Vendor Product Version / Range
google android 13.0
google android 14.0
google android 15.0
google android 16.0
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-20 The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability allows an application running in a work profile on an Android device to improperly set the main user's default NFC payment setting due to insufficient input validation. This means the app can change NFC payment settings without proper authorization or user interaction.

Impact Analysis

The vulnerability could lead to a local escalation of privilege, allowing a work profile application to alter NFC payment settings of the main user without needing additional execution privileges or user interaction. This could potentially enable unauthorized NFC payments or changes to payment configurations.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2025-48612. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart