How severe is CVE-2025-48621?

CVE-2025-48621 has a CVSS 3.x base score of 7.3, rated high severity. It is exploitable over local access with low attack complexity, requires low privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2025-48621 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (3rd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2025-48621?

CVE-2025-48621 primarily affects Google Android. In total, 4 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2025-48621?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2025-48621 have an EU (EUVD) identifier?

Yes. CVE-2025-48621 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-201747.

When was CVE-2025-48621 published?

CVE-2025-48621 was published on 2025-12-08 and last updated on 2026-06-17.

CVE-2025-48621

CVE-2025-48621 is a high-severity vulnerability in Google Android with a CVSS 3.x base score of 7.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-1188.

Key facts

Severity: High (CVSS 3.x base score 7.3)
EPSS exploit prediction: 0% (3rd percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-201747
Weakness: CWE-1188
Affected product: Google Android
Published: 2025-12-08
Last modified: 2026-06-17

Description

In DefaultTransitionHandler.java, there is a possible way to enable a tapjacking attack due to a insecure default. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation.

Frequently asked questions

What is CVE-2025-48621?: In DefaultTransitionHandler.java, there is a possible way to enable a tapjacking attack due to a insecure default. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation.
How severe is CVE-2025-48621?: CVE-2025-48621 has a CVSS 3.x base score of 7.3, rated high severity. It is exploitable over local access with low attack complexity, requires low privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2025-48621 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (3rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-48621?: CVE-2025-48621 primarily affects Google Android. In total, 4 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2025-48621?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2025-48621 have an EU (EUVD) identifier?: Yes. CVE-2025-48621 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-201747.
When was CVE-2025-48621 published?: CVE-2025-48621 was published on 2025-12-08 and last updated on 2026-06-17.

References

Affected products (4)

cpe:2.3:o:google:android:13.0:*:*:*:*:*:*:*
cpe:2.3:o:google:android:14.0:*:*:*:*:*:*:*
cpe:2.3:o:google:android:15.0:*:*:*:*:*:*:*
cpe:2.3:o:google:android:16.0:*:*:*:*:*:*:*

More vulnerabilities in Google Android

CVE-2026-0092 — Critical (CVSS 10.0): In Package Manager, there is a possible device lock controller bypass due to a missing permission check. This could…
CVE-2025-48611 — Critical (CVSS 10.0): In DeviceId of DeviceId.java, there is a possible desync in persistence due to a missing bounds check. This could lead…
CVE-2015-8073 — Critical (CVSS 10.0): mediaserver in Android 4.4 and 5.1 before 5.1.1 LMY48X allows remote attackers to execute arbitrary code or cause a…
CVE-2015-8072 — Critical (CVSS 10.0): mediaserver in Android 4.4 through 5.x before 5.1.1 LMY48X and 6.0 before 2015-11-01 allows remote attackers to execute…
CVE-2015-6610 — Critical (CVSS 10.0): libstagefright in Android before 5.1.1 LMY48X and 6.0 before 2015-11-01 allows attackers to gain privileges or cause a…
CVE-2015-6609 — Critical (CVSS 10.0): libutils in Android before 5.1.1 LMY48X and 6.0 before 2015-11-01 allows remote attackers to execute arbitrary code or…

All CVEs affecting Google Android →

Other CWE-1188 (Insecure Default Initialization of Resource) vulnerabilities

CVE-2026-31957 — Critical (CVSS 10.0): Himmelblau is an interoperability suite for Microsoft Azure Entra ID and Intune. From 3.0.0 to before 3.1.0, if…
CVE-2025-41672 — Critical (CVSS 10.0): A remote unauthenticated attacker may use default certificates to generate JWT Tokens and gain full access to the tool…
CVE-2024-0001 — Critical (CVSS 10.0): A condition exists in FlashArray Purity whereby a local account intended for initial array configuration remains active…
CVE-2024-2912 — Critical (CVSS 10.0): An insecure deserialization vulnerability exists in the BentoML framework, allowing remote code execution (RCE) by…
CVE-2021-34795 — Critical (CVSS 10.0): Multiple vulnerabilities in the web-based management interface of the Cisco Catalyst Passive Optical Network (PON)…
CVE-2017-7964 — Critical (CVSS 10.0): Zyxel WRE6505 devices have a default TELNET password of 1234 for the root and admin accounts, which makes it easier for…

Browse all CWE-1188 (Insecure Default Initialization of Resource) vulnerabilities →