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

Android Framework vulnerability

Android Framework contains an unspecified vulnerability enabling information disclosure. The vulnerability is actively exploited in the wild.

Verdict

Today item — known-exploited.

An information disclosure flaw in Android Framework is under active exploitation. The vulnerability allows unauthorized access to sensitive data, though specific attack vectors and affected Android versions require further technical analysis.

CISA KEV Yes · 2025-12-023EPSS 0.00231 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported 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.
source.android.com ↗cisa.gov ↗recordedfuture.com ↗loginsoft.com ↗Confirmed
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-12-02).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.00231 — 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, Framework. 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 exploit the Framework vulnerability to read sensitive data from the Android system or applications.
Business
User privacy is compromised through unauthorized access to personal information stored on affected devices.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I leverage the information disclosure to identify additional system weaknesses or credentials for privilege escalation.
Business
The vulnerability becomes a pivot point for deeper device compromise, increasing breach scope and remediation costs.
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)
  • 4 reported-exploitation source(s)
  • 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.