LiveActive security incident?Get immediate response
CVE Record

CVE-2025-48572: In multiple locations, there is a possible way to launch activities from the background due to a permission...

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.

HighCVSS 7.8Known exploitedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2025-48572 is a high-severity Android flaw that can let a local app bypass permissions and start activities from the background. Google lists Android 13, 14, 15, and 16 as affected. Exploitation requires local access through an app context but does not require user interaction.

Executive priority

Treat as a priority mobile patching issue, especially for managed Android fleets handling sensitive data. The business risk is privilege escalation from a local app, not remote internet compromise. Focus on patch coverage, OEM lag, and controls that reduce untrusted app installation.

Technical view

The CVE describes a permissions bypass in multiple Android locations, classified as CWE-306. Impact is local escalation of privilege with CVSS 3.1 score 7.8: AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Google references an Android framework change and the 2025-12-01 Android Security Bulletin.

Likely exposure

Organizations with Android 13 through 16 devices may be exposed until devices receive the relevant Android security bulletin fixes from Google or OEMs. Exposure depends on device model, vendor update availability, and installed security patch level.

Exploitation context

The provided sources do not show confirmed active exploitation. The bundled CISA KEV signal is false. The issue is locally exploitable, requires low privileges, and needs no user interaction, which increases concern for malicious apps already present on a device.

Researcher notes

Public details are limited. The official description cites multiple locations and a permission bypass allowing background activity launches. Review the linked Android framework commit and bulletin for patch context. Do not assume exploitation or broader product impact beyond Android 13 through 16 from the provided sources.

Mitigation direction

  • Apply the Android 2025-12-01 security update when available for affected devices.
  • Prioritize managed Android 13, 14, 15, and 16 devices.
  • Check OEM advisories for device-specific patch availability and timing.
  • Restrict installation of untrusted apps through mobile device management controls.

Validation and detection

  • Inventory Android device versions across the fleet.
  • Verify each device security patch level includes the relevant December 2025 Android fixes.
  • Confirm OEM build notes reference the December 2025 Android Security Bulletin.
  • Monitor CISA KEV and vendor advisories for exploitation status changes.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-306: Credential and account abuse lookup

Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-48572 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
Yes
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2025-48572Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GoogleAndroid16, 15, 14, 13unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-306 · source CWE mapping

Missing Authentication for Critical Function

Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.