CVE-2025-48633
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.
do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? No. The attack needs local access to the machine, so a WAF is not on its path.
Also consider: patch
Based on the attack vector (local or physical access). We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2025-48633 being exploited?
Yes. CVE-2025-48633 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2025-48633?
CVE-2025-48633 is rated Medium with a CVSS score of 5.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2025-48633?
Yes. A fix has been recorded for CVE-2025-48633. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2025-48633 affect?
CVE-2025-48633 affects google:android. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected16
- affected15
- affected14
- affected13
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
cisa ssvc
- exploitation
- active
- automatable
- no
- technical impact
- partial
Assessed by CISA 9 Dec 2025 (SSVC 2.0.3).
timeline
- 2 Dec 2025Added to CISA KEV (exploited in the wild)
- 8 Dec 2025Published · 7 days later
- 9 Dec 2025CISA SSVC assessment: exploitation active · same day later
- 23 Dec 2025CISA remediation due date (US federal agencies) · 14 days later
- 26 Feb 2026CVE record last updated · 66 days (about 2 months) later
- 2 Nov 2026Analysed by vulneraibility.com · 249 days (about 8 months) later
- Linkandroid.googlesource.com /platform/frameworks/base/+/d00bcda9f42dcf272d329e9bf9298f32af732f93
- Linksource.android.com /security/bulletin/2025-12-01
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-48633
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.