Exploited CVEs / Android / CVE-2025-48543
CVE-2025-48543
Android Runtime Use-After-Free Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies were required to remediate by 2025-09-25 (that deadline has passed); treat that date as the outer bound for your own environment. Check the vendor security advisory for the fix.
Risk summary
Actively exploited Android Runtime vulnerability, High severity, CVSS 8.8. Added to the CISA KEV catalog 2025-09-04.
Senserva AI Opinion for CVE-2025-48543
A use-after-free in the Android Runtime that enables escape from the Chrome sandbox into local privilege escalation, Severity High at CVSS 8.8. It is a chain component: paired with a browser renderer bug it turns a malicious web page into device compromise, and CISA confirmed such use in September 2025.
Do this: Push the latest Android security patch level and Chrome update together through your MDM.
AI-generated from public data, 2026-07-07. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for CVE-2025-48543
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Updated August 14, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.
Full tracking and change history for CVE-2025-48543
- Published
- 2025-09-04
- Last revised
- 2025-09-04
- Changes tracked
- 1
Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.
- 2025-09-04 added to the CISA KEV catalog by CISA
- 2026-07-17 CVSS 0.0 to 8.8; EPSS first scored at 0.5%
- 2026-08-05 EPSS 0.5% to 0.5%
Recorded by Senserva on the dates shown, from CISA KEV and FIRST EPSS. This is what moved and when, which neither the vendor advisory nor NVD publishes.
CISA required action
Federal (BOD 22-01) remediation due date: 2025-09-25 (past due).
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Official fix for CVE-2025-48543
Check the vendor's security advisory channel for the patched Runtime versions and workarounds.
Common questions about CVE-2025-48543
Is CVE-2025-48543 actively exploited?
Yes. CVE-2025-48543 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2025-09-04, which means exploitation in the wild has been confirmed, not predicted. Its EPSS 30-day exploitation probability is <1%.
What is the CISA deadline and required action for CVE-2025-48543?
CISA set the federal (BOD 22-01) remediation due date at 2025-09-25, which has passed; treat any unremediated system as overdue. The verbatim required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
What fixes CVE-2025-48543?
Check the vendor's security advisory for the patched Runtime versions and any workarounds. KEV listing makes this a fix-first item: patch it ahead of higher-CVSS issues nobody is exploiting.
Can I ask my own AI about CVE-2025-48543?
Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2025-48543's key facts: severity, CVSS, EPSS, the KEV date, the CISA due date, and the required action. Copy it into Claude, ChatGPT, or Copilot; the data is refreshed twice a day (5 AM and 3 PM US Central).
Scope and sources
- More exploited Android CVEs
- CVE-2025-48595CVE-2025-48633CVE-2025-48572CVE-2024-43093CVE-2024-36971CVE-2024-32896CVE-2024-29748CVE-2024-29745
All Android exploited CVEs on one page: Android vulnerabilities actively exploited.
- Authoritative references
Every actively exploited CVE, searchable with due dates and CSV export: the exploited-CVE tracker. The newest additions: exploited this week.