How severe is CVE-2025-48633?

CVE-2025-48633 has a CVSS 3.x base score of 5.5, rated medium severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.

Is CVE-2025-48633 being actively exploited?

Yes. CVE-2025-48633 is on CISA's Known Exploited Vulnerabilities (KEV) catalog, added on 2025-12-02, which means active exploitation has been confirmed. It should be prioritised for remediation.

What products are affected by CVE-2025-48633?

CVE-2025-48633 primarily affects Google Android. In total, 4 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2025-48633?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Because this CVE is known to be actively exploited, treat remediation as urgent — CISA KEV typically sets a short remediation deadline.

Does CVE-2025-48633 have an EU (EUVD) identifier?

Yes. CVE-2025-48633 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-201737. It is also flagged as exploited in the EUVD (since 2025-12-02).

When was CVE-2025-48633 published?

CVE-2025-48633 was published on 2025-12-08 and last updated on 2026-06-17.

CVE-2025-48633

CVE-2025-48633 is a medium-severity vulnerability in Google Android with a CVSS 3.x base score of 5.5. It is listed in CISA's Known Exploited Vulnerabilities (KEV) catalog, confirming it has been exploited in the wild (added 2025-12-02).

Key facts

Severity: Medium (CVSS 3.x base score 5.5)
EPSS exploit prediction: 0% (16th percentile)
Actively exploited: Yes — listed in CISA KEV (added 2025-12-02)
EU (EUVD) id: EUVD-2025-201737
EU exploitation: Flagged exploited in the ENISA EU Vulnerability Database (since 2025-12-02)
Affected product: Google Android
Published: 2025-12-08
Last modified: 2026-06-17

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.

Frequently asked questions

What is 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.
How severe is CVE-2025-48633?: CVE-2025-48633 has a CVSS 3.x base score of 5.5, rated medium severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2025-48633 being actively exploited?: Yes. CVE-2025-48633 is on CISA's Known Exploited Vulnerabilities (KEV) catalog, added on 2025-12-02, which means active exploitation has been confirmed. It should be prioritised for remediation.
What products are affected by CVE-2025-48633?: CVE-2025-48633 primarily affects Google Android. In total, 4 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2025-48633?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Because this CVE is known to be actively exploited, treat remediation as urgent — CISA KEV typically sets a short remediation deadline.
Does CVE-2025-48633 have an EU (EUVD) identifier?: Yes. CVE-2025-48633 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-201737. It is also flagged as exploited in the EUVD (since 2025-12-02).
When was CVE-2025-48633 published?: CVE-2025-48633 was published on 2025-12-08 and last updated on 2026-06-17.

References

Affected products (4)

cpe:2.3:o:google:android:13.0:*:*:*:*:*:*:*
cpe:2.3:o:google:android:14.0:*:*:*:*:*:*:*
cpe:2.3:o:google:android:15.0:*:*:*:*:*:*:*
cpe:2.3:o:google:android:16.0:*:*:*:*:*:*:*

More vulnerabilities in Google Android

CVE-2026-0092 — Critical (CVSS 10.0): In Package Manager, there is a possible device lock controller bypass due to a missing permission check. This could…
CVE-2025-48611 — Critical (CVSS 10.0): In DeviceId of DeviceId.java, there is a possible desync in persistence due to a missing bounds check. This could lead…
CVE-2015-8073 — Critical (CVSS 10.0): mediaserver in Android 4.4 and 5.1 before 5.1.1 LMY48X allows remote attackers to execute arbitrary code or cause a…
CVE-2015-8072 — Critical (CVSS 10.0): mediaserver in Android 4.4 through 5.x before 5.1.1 LMY48X and 6.0 before 2015-11-01 allows remote attackers to execute…
CVE-2015-6610 — Critical (CVSS 10.0): libstagefright in Android before 5.1.1 LMY48X and 6.0 before 2015-11-01 allows attackers to gain privileges or cause a…
CVE-2015-6609 — Critical (CVSS 10.0): libutils in Android before 5.1.1 LMY48X and 6.0 before 2015-11-01 allows remote attackers to execute arbitrary code or…

All CVEs affecting Google Android →