basicsecurity.net
Proof, not just disclosure.
Threats / Android / CVE-2025-48543
CVE-2025-48543 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Android Runtime vulnerability

Android Runtime use-after-free vulnerability enables sandbox escape and local privilege escalation.

Verdict

Today item — known-exploited.

A use-after-free flaw in Android Runtime permits attackers to escape the Chrome sandbox and gain elevated privileges on affected devices. Active exploitation in the wild confirms practical threat.

CISA KEV Yes · 2025-09-043EPSS 0.00545 (verify live)4Exploit Public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
vulncheck.com ↗Confirmed
Reported exploitation
5 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
docs.google.com ↗source.android.com ↗cisa.gov ↗rapid7.com ↗Confirmed
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-09-04).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.00545 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
FIRST EPSS ↗High
Severity / affected
Affected: Android, Runtime. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution 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 board
1

Front door — unauthenticated access narrative 1

Attacker
I craft malicious input to trigger a use-after-free condition in Android Runtime memory management.
Business
Unpatched devices remain exposed to memory corruption attacks with no mitigation.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I exploit the memory corruption to break out of the Chrome sandbox isolation boundary.
Business
Sandbox containment fails, expanding attack surface from browser context to system level.
3

Lateral reach — past segmentation narrative 3

Attacker
I execute arbitrary code with elevated privileges after escaping sandbox restrictions.
Business
Attackers gain system-level access, enabling data theft, malware installation, and device compromise.
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’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • Public PoC available (VulnCheck)
  • 5 reported-exploitation source(s)
  • Public exploit availability
  • Catalogued by google_android (CNA)

    • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
    • Disclosure & credit2
    Catalogued by google_androidCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.