Threats / Android / CVE-2025-48572
CVE-2025-48572
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Android Framework vulnerability
Android Framework contains an unspecified privilege escalation vulnerability that has been exploited in the wild.
Verdict
Today item — known-exploited.
A privilege escalation flaw in Android Framework enables attackers to gain elevated system permissions. Active exploitation in the wild indicates immediate risk to deployed Android devices, though ransomware campaigns have not been observed.
CISA KEV Yes · 2025-12-024EPSS 0.00247 (verify live)5CVSS 7.8 (CISA)3CISA SSVC Exploitation: active · Automatable: no · Impact: total3
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
4 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-12-02).
Probability (EPSS)
EPSS 0.00247 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 7.8 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) · Affected: Android, Framework. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog the same day the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
Gain code execution within an Android application sandbox with limited privileges.
Business
User device runs untrusted or compromised application with restricted permissions.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
Exploit the Framework vulnerability to escalate privileges beyond the application sandbox.
Business
Attacker obtains system-level access to the device, bypassing security boundaries.
3
Lateral reach — past segmentation narrative 3
Attacker
Access sensitive system resources, user data, and device functions normally restricted to privileged processes.
Business
Confidentiality and integrity of user data compromised; device control transferred to attacker.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by google_androidCNA
Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.