Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Back to vulnerabilities
Medium

Android Framework lockscreen browser launch privilege bypass in CommandParamsFactory

IdentifiersCVE-2025-48618CWE-667· Improper Locking

CVE-2025-48618 is an Android Framework elevation-of-privilege vulnerability in processLaunchBrowser of CommandParamsFactory.java. According to the provided description, improper locking allows browser interaction to occur from the lockscreen. This creates a lockscreen bypass condition in which restricted functionality becomes accessible despite the device being locked. The issue is described as enabling physical escalation of privilege and does not require additional execution privileges or user interaction for exploitation.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial
ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an attacker with physical access to a locked Android device to trigger browser interaction from the lockscreen, bypassing intended lock-state restrictions. This constitutes a local/physical elevation of privilege because the attacker can access functionality that should be blocked until the device is unlocked. Depending on device configuration and browser behavior, this may expose data or actions reachable through the browser context while the device remains locked.

Mitigation

If you can’t patch tonight, do this now.

Until patches are deployed, risk reduction is limited because the issue is exploitable without user interaction once an attacker has physical access to the device. Practical mitigations are to prevent unauthorized physical access to devices, enforce rapid screen lock and strong unlock mechanisms, and prioritize deployment of the December 2025 Android security updates or vendor-equivalent firmware. Enterprise fleets should verify both Google patch level and OEM update status.

Remediation

Patch, then assume compromise.

Apply the Android security update that includes the fix for CVE-2025-48618. The provided context places this issue in Google’s December 2025 Android Security Bulletin affecting supported Android 13 through Android 16 builds, with full remediation described at the 2025-12-05 patch level. OEM and downstream vendors should integrate the corresponding Framework fix into their builds and distribute updated firmware to affected devices.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GoogleAndroidoperating_system

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

4 SOURCESView more in app
What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Start free trial
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity3

Community discussion across Reddit, Mastodon, and other social sources.

EXTERNAL REFERENCES
MITRE CVE
cve.org · CVE-2025-48618
NVD
nvd.nist.gov/vuln/detail/CVE-2025-48618
MITRE CWE · CWE-667
Improper Locking
Patch
android.googlesource.com/platform/frameworks/opt/telephony/+/fee68bcdcf029e8f40980616d09367610544bc62
Vendor Advisory
source.android.com/security/bulletin/2025-12-01