# CVE-2025-48595: Android Framework Integer Overflow

> An integer overflow in Android allows local attackers to achieve code execution and escalate privileges without user interaction.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 2 Jun 2026 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Jun 2026
- **Updated:** 3 Jun 2026
- **Also known as:** A-430889718, ASB-A-430889718, GHSA-2mvq-m5m5-v7m7

## What is CVE-2025-48595?

CVE-2025-48595 is a high-severity vulnerability in Google Android, published on 1 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In multiple locations, there is a possible way to achieve code execution due to an integer overflow. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2025-48595?

It affects 1 product.


Products: Google Android.

## How do I fix CVE-2025-48595?

Apply the vendor's patch. US federal agencies must fix it by 5 Jun 2026.

## Is CVE-2025-48595 being exploited?

Yes. Attackers have exploited CVE-2025-48595 in the wild since at least 2 Jun 2026.

Public exploit code:

- CVE-2025-48595 - Draft (github_poc): https://github.com/HORKimhab/CVE-2025-48595
- PoC de CVE-2025-48595: desbordamiento de entero en multiples ubicaciones del Framework de Android. (github_poc): https://github.com/fevar54/CVE-2025-48595-Android-Framework-Integer-Overflow-
- CVE-2025-48595 Android Framework Integer Overflow PoC - 优化版 (github_poc): https://github.com/XiaoBaiLovesStirring/CVE-2025-48595-Exploit

## Other vulnerabilities in Google Android

- [CVE-2026-58704](https://insights.sbomify.com/CVE-2026-58704/): Google Pixel Improper Authorization (high 8.8, exploited in the wild)
- [CVE-2025-48543](https://insights.sbomify.com/CVE-2025-48543/): Android Runtime Use-After-Free (high 8.8, exploited in the wild)
- [CVE-2023-35674](https://insights.sbomify.com/CVE-2023-35674/): Android Framework Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2024-32896](https://insights.sbomify.com/CVE-2024-32896/): Android Pixel Privilege Escalation (high 8.1, exploited in the wild)
- [CVE-2025-48572](https://insights.sbomify.com/CVE-2025-48572/): Android Framework Privilege Escalation (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-48595 and fix it if it is affected.

What it is: CVE-2025-48595 is a high-severity vulnerability in Google Android, published on 1 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2025-48595 in the wild since at least 2 Jun 2026.

Affected product: Google Android. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-48595/ (Markdown: https://insights.sbomify.com/CVE-2025-48595/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-48595
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-48595
- OSV: https://osv.dev/vulnerability/CVE-2025-48595

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-48595/
Summaries are generated and may contain mistakes; the official description above is the record.