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

Android Framework vulnerability

Android Framework integer overflow vulnerability enabling local privilege escalation and code execution.

Verdict

Today item — known-exploited.

Integer overflow in Android Framework permits local attackers to execute arbitrary code with elevated privileges. Active exploitation in the wild demonstrates practical threat. Mitigation requires framework patching.

CISA KEV Yes · 2026-06-023EPSS 0.00401 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2026-06-02).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.00401 — 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
Weakness (CWE)
Mapped to CWE-190 Integer Overflow — weakness family: Memory safety.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-190 · Integer OverflowMemory safety
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No threat-actor attribution is established from the public feed 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 an integer overflow condition in Android Framework processing to trigger unexpected memory behavior.
Business
Compromised device integrity and user data confidentiality at risk from local privilege escalation.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I craft malicious input that causes integer wraparound, bypassing bounds checks in framework code.
Business
Attacker gains system-level access, enabling installation of persistent malware or data exfiltration.
3

Lateral reach — past segmentation narrative 3

Attacker
I execute arbitrary code with elevated privileges after integer overflow allows me to escape application sandbox.
Business
Complete device compromise possible, affecting all user applications and sensitive information stored on device.
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)
  • CWE weakness mapping (NVD)
  • 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.