How severe is CVE-2025-48572?

No CVSS score has been assigned to CVE-2025-48572 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-48572?

CVE-2025-48572 affects the following packages: platform/frameworks/base (Android), platform/frameworks/base (Android), platform/frameworks/base (Android), platform/frameworks/base (Android), platform/frameworks/base (Android). Ecosystems affected: Android.

How do I fix CVE-2025-48572?

Update platform/frameworks/base to 16-qpr2-next:2025-12-01 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-48572 is resolved across your whole dependency graph.

How do I detect CVE-2025-48572 in my Android dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for platform/frameworks/base, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-48572 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2025-48572 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-48572 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-48572?

CVE-2025-48572 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 17th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

Is CVE-2025-48572 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2025-48572 (Android Framework Privilege Escalation Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2025-12-02. CISA required all US federal civilian agencies to remediate this vulnerability by 2025-12-23. The required action was: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2025-48572?

CVE-2025-48572 is classified as Missing Authentication (CWE-306). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-48572 published, and has it been updated?

CVE-2025-48572 was published on December 1, 2025 and was last updated on October 23, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 Android

CISA KEV · ACTIVELY EXPLOITED

CVE-2025-48572 — base

CVE-2025-48572 is a Missing Authentication vulnerability in platform/frameworks/base. It is in CISA's Known Exploited Vulnerabilities catalog (added 2025-12-02) — treat it as actively exploited and patch now. A fix is available for platform/frameworks/base — see the affected versions and patch details below.

Also known asA-385736540

Published

Dec 1, 2025

Updated

Oct 23, 2026

Affected

5 pkgs

Patched

5 / 5

Exploits

None indexed

Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2025-12-02. Federal agencies were required to remediate by 2025-12-23.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2025-48572.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs17th percentile — riskier than 17% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

5 pkgs affected

📦platform/frameworks/base📦platform/frameworks/base📦platform/frameworks/base📦platform/frameworks/base📦platform/frameworks/base

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Android packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

5 total 5 fixed

Ecosystem	Package	Vulnerable range	Fix
📦Android	`platform/frameworks/base`	≥ 16-qpr2-next:0&&< 16-qpr2-next:2025-12-01	16-qpr2-next:2025-12-01
📦Android	`platform/frameworks/base`	≥ 15:0&&< 15:2025-12-01	15:2025-12-01
📦Android	`platform/frameworks/base`	≥ 16:0&&< 16:2025-12-01	16:2025-12-01
📦Android	`platform/frameworks/base`	≥ 13:0&&< 13:2025-12-01	13:2025-12-01
📦Android	`platform/frameworks/base`	≥ 14:0&&< 14:2025-12-01	14:2025-12-01

Affected Products

1 product · 4 configurations

androidgoogle

4 versions

13.014.015.016.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for platform/frameworks/base, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update platform/frameworks/base to 16-qpr2-next:2025-12-01 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-48572 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2025-48572 in your dependencies?

Find it across Android, including transitive dependencies.

Scan my dependencies How O3 SCA works