How severe is CVE-2025-48595?

No CVSS score has been assigned to CVE-2025-48595 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-48595?

CVE-2025-48595 affects the following packages: platform/external/sqlite (Android), platform/build/release (Android), platform/external/sqlite (Android), platform/vendor/google_shared/build/release (Android), platform/build/release (Android), platform/external/sqlite (Android), platform/build/release (Android), platform/external/sqlite (Android), and 1 more. Ecosystems affected: Android.

How do I fix CVE-2025-48595?

Update platform/external/sqlite to 17-next:2026-06-01 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-48595 is resolved across your whole dependency graph.

How do I detect CVE-2025-48595 in my Android dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for platform/external/sqlite, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-48595 if there is no patch (or I can't update yet)?

Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Is CVE-2025-48595 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-48595 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-48595?

CVE-2025-48595 has an EPSS (Exploit Prediction Scoring System) score of 1.7%, placing it in the 77th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

Is CVE-2025-48595 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2025-48595 (Android Framework Integer Overflow Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2026-06-02. CISA required all US federal civilian agencies to remediate this vulnerability by 2026-06-05. The required action was: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2025-48595?

CVE-2025-48595 is classified as CWE-190 (CWE-190). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-48595 published, and has it been updated?

CVE-2025-48595 was published on June 1, 2026 and was last updated on October 23, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 Android

CISA KEV · ACTIVELY EXPLOITED

CVE-2025-48595 — sqlite

CVE-2025-48595 is a CWE-190 vulnerability in platform/external/sqlite. It is in CISA's Known Exploited Vulnerabilities catalog (added 2026-06-02) — treat it as actively exploited and patch now. A fix is available for platform/external/sqlite — see the affected versions and patch details below.

Also known asA-430889718

Published

Jun 1, 2026

Updated

Oct 23, 2026

Affected

9 pkgs

Patched

9 / 9

Exploits

None indexed

Exploitation data as of Oct 24, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2026-06-02. Federal agencies were required to remediate by 2026-06-05.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2025-48595.

EPSS Exploitation Probability

via FIRST.org ↗

1.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs77th percentile — riskier than 77% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

9 pkgs affected

📦platform/external/sqlite📦platform/build/release📦platform/external/sqlite📦platform/vendor/google_shared/build/release📦platform/build/release📦platform/external/sqlite📦platform/build/release📦platform/external/sqlite+1 more

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Android packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

9 total 9 fixed

Ecosystem	Package	Vulnerable range	Fix
📦Android	`platform/external/sqlite`	≥ 17-next:0&&< 17-next:2026-06-01	17-next:2026-06-01
📦Android	`platform/build/release`	≥ 15:0&&< 15:2026-06-01	15:2026-06-01
📦Android	`platform/external/sqlite`	≥ 15:0&&< 15:2026-06-01	15:2026-06-01
📦Android	`platform/vendor/google_shared/build/release`	≥ 15:0&&< 15:2026-06-01	15:2026-06-01
📦Android	`platform/build/release`	≥ 16:0&&< 16:2026-06-01	16:2026-06-01
📦Android	`platform/external/sqlite`	≥ 16:0&&< 16:2026-06-01	16:2026-06-01

Affected Products

1 product · 6 configurations

androidgoogle

3 versions

14.015.016.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for platform/external/sqlite, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update platform/external/sqlite to 17-next:2026-06-01 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-48595 is resolved across your whole dependency graph.
Workarounds
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2025-48595 in your dependencies?

Find it across Android, including transitive dependencies.

Scan my dependencies How O3 SCA works