CVE-2025-48595

Android Framework Integer Overflow Vulnerability

Actively exploited (CISA KEV) High 8.4 CVSS 3.1

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.

Description as published by the source, in English.

Key facts

Published: 2026-06-01
Last modified: 2026-07-22
Assigned by: security@android.com
CVSS vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Scored by: 134c704f-9b21-4f2e-91b3-4a467353bcc0
Probability of exploitation: 1.7 % higher than 75 % of all known vulnerabilities
EPSS, next 30 days, model v2026.06.15
Fix available: Not registered in the sources

Actively exploited

CISA added this vulnerability to the Known Exploited Vulnerabilities catalogue on 2026-06-02, with a remediation deadline of 2026-06-05 for US federal agencies.

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

Affected products

Vendor	Product	Versions	Status
Google	Android	14.0	Affected
Google	Android	15.0	Affected
Google	Android	16.0	Affected

Weakness type

CWE-190: Integer Overflow or Wraparound
The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is i…

References

https://source.android.com/docs/security/bulletin/2026/2026-06-01 Vendor Advisory
https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-48595 US Government Resource

Related at Berigo

Articles

Russian clusters bypass two step verification by asking for app passwords Same product 2026-08-24
Google Threat Intelligence Group described three clusters linked to Russian intelligence on 20 August 2026, targeting academics, the defence industry…
A traveller gave a duress password at the border and was charged Same product 2026-08-19
A United States citizen is charged with wiping the contents of his phone during a border search in January 2025. He pleaded not guilty, and the case …
Shared Claude conversations turned up in Google search Same product 2026-08-18
On 27 July 2026 404 Media reported that shared Claude conversations and artifacts appeared in Google search results. The findings included medical re…
Approved partners get access to a model that finds unknown vulnerabilities Same product 2026-08-12
OpenAI is expanding Daybreak with two access levels and releasing GPT-5.6-Cyber, a model trained for tasks such as finding zero-day vulnerabilities a…

Does this affect you?

A vulnerability matters only if you run the product, in an affected version, somewhere an attacker can reach.

Check your asset list Browse all vulnerabilities

Sources and freshness

CVE

What it is: A reference number naming one specific vulnerability, for example CVE-2024-9474.
What it tells you: Which vulnerability we are talking about, and in which product.
What it does NOT tell you: Nothing about how serious it is, whether anyone is exploiting it, or whether it concerns you.
Why it matters: Without a shared number, vendor, authority and tooling cannot discuss the same flaw.
Used with the others: The number is the key. NVD, KEV and EPSS all describe the same CVE.

NVD CWE CISA KEV EPSS

How to read this together

No single value should be used on its own. A high CVSS score does not mean a vulnerability is being exploited, and a low one does not mean it is harmless. The four sources answer four different questions.

CVE names the specific vulnerability.
NVD adds severity and technical detail about it.
CWE describes the type of mistake behind it.
CISA KEV shows that it is already being exploited.
EPSS estimates how likely exploitation is soon.

The order that decides what is urgent

Do you actually have the product?
Is the version you run affected?
Is it listed in CISA KEV?
Does it have a high EPSS score?
Is the system reachable from the internet or from others?
How important is the system to the business?
Are there compensating controls already in place?

The first two questions are not about the vulnerability at all. They are about you, and they remove most of the list before you start.

A short example

Fix this week

CVSS 6,5 (medium)

In CISA KEV: yes
EPSS: 94 per cent
A firewall facing the internet

Can be scheduled

CVSS 9,8 (critical)

In CISA KEV: no
EPSS: 0,04 per cent
A test server with no internet access

Sorted by CVSS alone, the one on the right comes first. It is the more serious flaw in theory. But the one on the left is being used against real organisations right now, and it sits where an attacker can reach it. That is the one to fix first.

The critical one still has to be fixed. It just does not have to be fixed today.

This product uses the NVD API but is not endorsed or certified by the NVD. CVE and the CVE logo are registered trademarks of The MITRE Corporation; CVE records are used under the CVE Terms of Use. CWE is a trademark of The MITRE Corporation, used per the CWE Terms of Use. KEV data from CISA (CC0). Exploitation probability from EPSS, a FIRST.org project. Open-source package data from OSV and the GitHub Advisory Database (CC-BY 4.0).

Scores and vectors are shown as published by the sources. The ordering of results is Berigo's own editorial assessment, described on the search page, and is not NVD data. An empty result never means a system is safe.