CVE-2025-48626 — Protection Mechanism Failure in Frameworks Base

CWE-693 — Protection Mechanism Failure5 documents5 sources
Severity
9.8CRITICALNVD
EPSS
0.5%
top 32.56%
CISA KEV
Not in KEV
Exploit
No known exploits
Affected products
3
Platform Frameworks BasePlatform Packages Apps Launcher3Google Android
Timeline
PublishedDec 8

Description

In multiple locations, there is a possible way to launch an application from the background due to a precondition check failure. This could lead to remote escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitability: 3.9 | Impact: 5.9

Affected Packages4 packages

▶Androidplatform/packages_apps_launcher316-qpr2-next:0 — 16-qpr2-next:2025-12-01+4
▶Androidplatform/frameworks_base16-qpr2-next:0 — 16-qpr2-next:2025-12-01+4
▶CVEListV5google/android4 versions+3
▶NVDgoogle/android4 versions+3

Patches

Patch: android.googlesource.com ↗Patch: android.googlesource.com ↗

🔴Vulnerability Details

3
GHSA
GHSA-882w-jx24-3www: In multiple locations, there is a possible way to launch an application from the background due to a precondition check failure↗2025-12-08
▶
CVEList
CVE-2025-48626: In multiple locations, there is a possible way to launch an application from the background due to a precondition check failure↗2025-12-08
▶
OSV
CVE-2025-48626: In multiple locations, there is a possible way to launch an application from the background due to a precondition check failure↗2025-12-01
▶

📋Vendor Advisories

1
Android
CVE-2025-48626: Android Security Bulletin 2025-12-01 CVE: CVE-2025-48626 Severity: HIGH Type: EoP Affected AOSP versions: 13, 14, 15, 16 References: A-381339822 [2]↗2025-12-01
▶
CVE-2025-48626 — Protection Mechanism Failure | cvebase