How severe is CVE-2025-48633?

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

Which packages are affected by CVE-2025-48633?

CVE-2025-48633 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-48633?

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-48633 is resolved across your whole dependency graph.

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

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for platform/frameworks/base. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

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

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2025-48633?

O3 pinpoints whether CVE-2025-48633 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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

No public exploit code has been indexed for CVE-2025-48633 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-48633?

CVE-2025-48633 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-48633 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2025-48633 (Android Framework Information Disclosure 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.

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

CVE-2025-48633 was published on December 1, 2025 and was last updated on September 8, 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-48633

CVE-2025-48633 is a security 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. O3 Security confirms whether CVE-2025-48633 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Also known asA-417988098

Published

Dec 1, 2025

Updated

Sep 8, 2026

Affected

5 pkgs

Patched

5 / 5

Exploits

None indexed

Exploitation data as of Aug 26, 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.

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

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk+0.01%

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

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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 hasAccountsOnAnyUser of DevicePolicyManagerService.java, there is a possible way to add a Device Owner after provisioning 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.

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

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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-48633 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2025-48633 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2025-48633. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2025-48633 in your dependencies?

O3 detects CVE-2025-48633 across Android dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works