Auth bypass in Google Android
CVE-2025-48572
In multiple locations, there is a possible way to launch activities from the background due to a permissions bypass. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
Vulnerability class: Broken Authentication
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.8 (High). Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
EPSS exploit prediction
EPSS: 0.003 (16.5th percentile), scored .
Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 17th percentile — 16.5% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.003 · newest: 0.003 · change: 0.000
Affected products
- Google Android — versions 15.0, 14.0, 13
Weakness classification (CWE)
CISA KEV (Known Exploited Vulnerabilities)
This CVE is on the CISA KEV catalog, added on . CISA KEV inclusion means CISA has confirmed in-the-wild exploitation; US federal agencies are required to remediate within a published due date.
BOD 22-01 due date: .
Required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
References
- android.googlesource.com/platform/frameworks/base/+/e707f6600330691f9c67dc023c0… (Product)
- source.android.com/security/bulletin/2025-12-01 (Vendor Advisory)
- 134c704f-9b21-4f2e-91b3-4a467353bcc0 (Third Party Advisory, US Government Resource)
Frequently asked questions
- What is CVE-2025-48572?
- CVE-2025-48572 is a high-severity vulnerability in Google Android, classified under Missing Authentication for Critical Function. CVSS score: 7.8/10. Published 2025-12-08.
- How severe is CVE-2025-48572?
- High severity. CVSS v3 base score is 7.8 out of 10.
- Is CVE-2025-48572 known to be exploited?
- Yes. CVE-2025-48572 is listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-12-02), indicating it is being actively exploited.