CVE-2025-48632
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-12-08

Last updated on: 2025-12-08

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

Description
In setDisplayName of AssociationRequest.java, there is a possible way to cause CDM associations to persist after the user has disassociated them 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
2025-12-08
Generated
2026-06-16
AI Q&A
2025-12-08
EPSS Evaluated
2026-06-15
NVD
CVE-2025-48632
Affected Vendors & Products
Showing 3 associated CPEs
Vendor Product Version / Range
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 occurs in the setDisplayName method of AssociationRequest.java, where improper input validation allows CDM associations to persist even after a user has disassociated them. This means that associations that should have been removed remain active.

Impact Analysis

The vulnerability can lead to a local escalation of privilege without requiring any additional execution privileges or user interaction. This means an attacker could gain higher privileges on the local system by exploiting this issue.

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