Every CVESearch/Get API key

CVE-2025-48522

In setDisplayName of AssociationRequest.java, there is a possible way for an app to retain CDM...

7.8 HighFix available

In setDisplayName of AssociationRequest.java, there is a possible way for an app to retain CDM association due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

Attack profile

How easy it is to exploit

Attack vector
Local
Complexity
Low
Privileges needed
Low
User interaction
None

What an attacker can affect

Confidentiality
High
Integrity
High
Availability
High

Exploit likelihood

0.10%Up 0.1 points since Sep 5, 2025
90%50%10%1%

What each source reports

CVE List Score used7.8

In setDisplayName of AssociationRequest.java, there is a possible way for an app to retain CDM association due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

Record
CVE-2025-48522
CVSS 3.1
7.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness
CWE-693
Updated
2026-11-02
EUVDEUVD-2025-268277.8

In setDisplayName of AssociationRequest.java, there is a possible way for an app to retain CDM association due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

Record
EUVD-2025-26827
CVSS 3.1
7.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Updated
2026-11-02
GitHub AdvisoriesGHSA-87v6-8c5r-wh3w7.8

In setDisplayName of AssociationRequest.java, there is a possible way for an app to retain CDM...

In setDisplayName of AssociationRequest.java, there is a possible way for an app to retain CDM association due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

Record
GHSA-87v6-8c5r-wh3w
CVSS 3.1
7.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness
CWE-693
Updated
2026-11-02
NVD7.8

In setDisplayName of AssociationRequest.java, there is a possible way for an app to retain CDM association due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

Record
CVE-2025-48522
CVSS 3.1
7.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness
CWE-693
Updated
2026-11-02
OSVASB-A-418773283No score

In setDisplayName of AssociationRequest.java, there is a possible way for an app to retain CDM association due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

Record
ASB-A-418773283
Updated
2026-11-09

Affected products

Affected packages

Affected packages
PackageAffectedFixed
platform/frameworks/base
Android
16-next:0 up to 16-next:2025-09-01, plus listed versions
16-next
16-next:2025-09-01
platform/frameworks/base
Android
15:0 up to 15:2025-09-01, plus listed versions
15
15:2025-09-01
platform/frameworks/base
Android
16:0 up to 16:2025-09-01, plus listed versions
16
16:2025-09-01
platform/frameworks/base
Android
13:0 up to 13:2025-09-01, plus listed versions
13
13:2025-09-01
platform/frameworks/base
Android
14:0 up to 14:2025-09-01, plus listed versions
14
14:2025-09-01

History

History
RecordedChangedSources
factsOSV
first indexedCVE List, EUVD, GitHub Advisories, NVD, OSV

Dates are when Every CVE recorded each change. Upstream dates may differ.

In short

CVE-2025-48522 is a high vulnerability (CVSS 7.8) in Google Android, published September 1, 2025. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.10%, the 0th percentile. Fixed in platform/frameworks/base 16-next:2025-09-01.

References

PagesAll vulnerabilitiesBrowseDocsSourcesGuideGet API key
MoveEnter Open