ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2025-48612

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.

Published Dec 8, 2025 · catalog updated Jun 1, 2026 · Google Android

Last checked Oct 26, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2025-48612. EPSS is 0.11%. Act only if a listed version of Google Android is installed.

Gaps on this record

  • No version range is stored. A customer cannot check an installed version against this record.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.

Same product and reporting

Severity
High7.8
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.11%
Remediation
Advisory link
Affected products
vendor Google Android 16-qpr2

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • vendor Google Android 16-qpr216-qpr2

How to fix CVE-2025-48612

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2025-48612. EPSS is 0.11%. Act only if a listed version of Google Android is installed.

Which versions are affected?

Compare what you have installed with Google Android 16-qpr2 16-qpr2. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 0.11%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Dec 8, 2025 · EUVD

    Detected

    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.

  2. Jun 1, 2026 · EUVD

    Updated

    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.

Sources

  • CVE.orgVulnerability recordCVE-2025-48612

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2025-48612

    30-day exploitation probability 0.11%

    first.org
  • EUVDVulnerability recordEUVD-2025-201752

    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 i

    euvd.enisa.europa.eu

References

Freshness

Last verified in this catalog Oct 26, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • FIRST EPSSOct 26, 2026
  • CVE.orgOct 26, 2026
  • EUVDOct 26, 2026