+44 1865 950 828 Secure Your Business
Actively exploited

CVE-2025-48595 Android Framework Integer Overflow Vulnerability

Android Framework contains an integer overflow vulnerability that allows for code execution that could allow for local privilege escalation.

From the CISA KEV catalogue version 2026.11.06, with Cybergen analysis. Updated 6 Nov 2026.

Our Assessment

Should You Worry?

Patch urgentlyCybergen assessment
  • CISA confirmed exploitation in the wild and added it to the Known Exploited Vulnerabilities catalogue on 2 Jun 2026.
  • Rated High severity (CVSS 8.4, scored by CISA).
  • It has been in the catalogue for 157 days. Systems still unpatched now have almost certainly been scanned for it.
The Vulnerability

What It Is

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.

Affected Versions

ProductVersions
Google Android16-qpr2
16
15
14

From the public CVE record, as supplied by the vendor. Always confirm against the vendor advisory.

From Watch to Action

What To Do Now

  1. 1

    Find it

    Search your asset inventory and external attack surface for Android Framework. Include cloud images, appliances and anything a supplier runs for you.

    Attack Surface Management
  2. 2

    Fix it

    Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

    Vulnerability Management
  3. 3

    Hunt for compromise

    If an affected system was reachable before you patched, assume it may have been hit. Check logs, new accounts, web shells and outbound connections from the date of exposure.

    Incident Response
  4. 4

    Prove it is fixed

    Rescan or test the system after patching. Upgrades that fail silently and forgotten secondary instances are common.

    Penetration Testing

Vendor Advisories

Regulation

The Compliance Clock

Cyber EssentialsRated high, so if it affects devices in your Cyber Essentials scope, the update must be installed within 14 days of the vendor releasing it.NIS2If exploitation causes a significant incident, essential and important entities owe their CSIRT an early warning within 24 hours and a notification within 72 hours.DORAFinancial entities must classify ICT incidents and send an initial notification for a major incident within strict deadlines, with exploited flaws a common cause.US federal (BOD 22-01)Federal civilian agencies had until 5 Jun 2026 to remediate. A sensible benchmark for everyone else.

General guidance, not legal advice. Your obligations depend on your sector, scope and jurisdiction.

Stay Ahead

More Exploited Android Flaws

Get alerts for AndroidWe email you when a new Android vulnerability is confirmed as exploited. Add more vendors on Threat Watch.

By signing up you agree to receive Threat Watch alerts. Unsubscribe at any time. See our Privacy Policy.

CVE-2025-48633Android Framework Information Disclosure VulnerabilityAdded 2 Dec 2025CVE-2025-48572Android Framework Privilege Escalation VulnerabilityAdded 2 Dec 2025CVE-2025-48543Android Runtime Use-After-Free VulnerabilityAdded 4 Sep 2025CVE-2024-43093Android Framework Privilege Escalation VulnerabilityAdded 7 Nov 2024CVE-2024-36971Android Kernel Remote Code Execution VulnerabilityAdded 7 Aug 2024CVE-2024-32896Android Pixel Privilege Escalation VulnerabilityAdded 13 Jun 2024

All 17 exploited Android vulnerabilities

Not Sure If You Are Exposed?

Our attack surface and vulnerability teams can check your internet-facing estate for CVE-2025-48595 and every other exploited flaw on the list.

Check My Exposure
Evidence

Sources

  1. CISA Known Exploited Vulnerabilities catalogue
  2. NVD: CVE-2025-48595
  3. CVE record: CVE-2025-48595
  4. FIRST EPSS
  5. source.android.com/docs/security/bulletin/2026/2026-06-01