CVE-2025-48595
HighExploitedPublic exploitIn multiple locations, there is a possible way to achieve code execution due to an integer overflow.
Published Jun 1, 2026 · Updated Oct 14, 2026 · Also known as A-430889718, ASB-A-430889718, EUVD-2025-210013, GHSA-2mvq-m5m5-v7m7
Key Facts
Patch immediately- CVE-2025-48595 is a high-severity vulnerability (CVSS 8.4 v3.1) affecting Android (Google), platform/build/release (android), platform/external/sqlite (android) and 1 more product.
- It is exploited in the wild, listed in CISA KEV, Industry KEV feed, CIRCL KEV, ENISA EUVD since Jun 1, 2026. Public exploit code is available.
- EPSS estimates a 1.7% probability of exploitation in the next 30 days.
- Fixed versions are available, including platform/build/release 15:2026-06-01, platform/build/release 16-qpr2:2026-06-01, platform/build/release 16:2026-06-01.
- Brandefense priority: patch immediately, because it is listed as exploited in the wild.
CVSS v3.1
8.4
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (30-day exploit likelihood)
1.7%
Higher than 77.0% of all scored CVEs
Exploited in the wild
Yes
4 catalog listings
Public exploit code
Available
Proof-of-concept or weaponized module
Get the full CVE-2025-48595 brief as a PDF
Every affected product and fixed release, exploitation status and a first 24 hours response checklist, emailed within minutes.
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.
Known-Exploited Catalog Listings
| Catalog | Added | Remediation due | Ransomware use |
|---|---|---|---|
| CISA KEV | Jun 2, 2026 | Jun 5, 2026 | Not reported |
| Industry KEV feed | Jun 1, 2026 | Jun 5, 2026 | Not reported |
| CIRCL KEV | Jun 2, 2026 | Jun 5, 2026 | Not reported |
| ENISA EUVD | Jun 2, 2026 | n/a | Not reported |
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
11 affected entries in total| Product | Affected versions | Fixed in |
|---|---|---|
| AndroidGoogle | 14.0, 15.0, 16.0, 16.0-qpr2_beta_1, 16.0-qpr2_beta_2, 16.0-qpr2_beta_3, >= 16-qpr2 | n/a |
| platform/build/releaseandroid | >= 15:0 | 15:2026-06-01 |
| platform/external/sqliteandroid | >= 17-next:0 | 17-next:2026-06-01 |
| platform/vendor/google_shared/build/releaseandroid | >= 15:0 | 15:2026-06-01 |
Patched Releases
platform/build/release
15:2026-06-01, 16-qpr2:2026-06-01, 16:2026-06-01
platform/external/sqlite
14:2026-06-01, 15:2026-06-01, 16-qpr2:2026-06-01, 16:2026-06-01, 17-next:2026-06-01
platform/vendor/google_shared/build/release
15:2026-06-01
Timeline
Publicly disclosed
Jun 1, 2026
Added to Industry KEV feed
Jun 1, 2026
Added to CISA KEV
Jun 2, 2026
Added to CIRCL KEV
Jun 2, 2026
Added to ENISA EUVD
Jun 2, 2026
Last updated
Oct 14, 2026
Weakness Type
- CWE-190 Integer Overflow or Wraparound
References
- advisoryhttps://nvd.nist.gov/vuln/detail/CVE-2025-48595
- advisoryhttps://source.android.com/security/bulletin/2026-06-01
- patchhttps://android.googlesource.com/platform/build/release/+/9484064212935962adbd8b6f4e028f2d5179433e
- patchhttps://android.googlesource.com/platform/build/release/+/b11607ea3ec7ab3183b558392850c842c582d2cc
- patchhttps://android.googlesource.com/platform/external/sqlite/+/1612b56a5b4092f8256dfaa2096e9680d3f47f98
FAQ
Common Questions.
In multiple locations, there is a possible way to achieve code execution due to an integer overflow.
Affected: Android (Google) versions 14.0, 15.0, 16.0, 16.0-qpr2_beta_1, 16.0-qpr2_beta_2, 16.0-qpr2_beta_3, >= 16-qpr2; platform/build/release (android) versions >= 15:0; platform/external/sqlite (android) versions >= 17-next:0, among others. The full list is in the CVE brief.
It is exploited in the wild, listed in CISA KEV, Industry KEV feed, CIRCL KEV, ENISA EUVD since Jun 1, 2026.
Yes. It was added on Jun 2, 2026 with a federal remediation due date of Jun 5, 2026.
Public exploit code is available.
Fixed versions are available, including platform/build/release 15:2026-06-01, platform/build/release 16-qpr2:2026-06-01, platform/build/release 16:2026-06-01.
Brandefense priority: patch immediately, because it is listed as exploited in the wild.
Is CVE-2025-48595 Running On Your Attack Surface?
Brandefense maps vulnerabilities like this one to your internet-facing assets and tells you exactly where to patch.
Request A Demo