Skip to main content
No exploitation reportedFix available

CVE-2025-48609

No exploitation reported by the sources we read.

  • Published2026-03-02
  • WeaknessCWE-400

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

In multiple functions of MmsProvider.java, there is a possible way to arbitrarily delete files which affect telephony, SMS, and MMS functionalities due to a path traversal error. This could lead to local denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.

Timeline

dates in UTC
  1. 2026-03-0219:16CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-11-03 15:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2025-48609?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2025-48609?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD
Google android
BranchAffectedFixed in
14.0= 14.0no fix published
15.0= 15.0no fix published
16.0= 16.0no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As google_android, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • Google Androidother versions: not affected
    Affected
    • = 16no fix stated
    • = 15no fix stated
    • = 14no fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-03-06

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • platform/packages/providers/TelephonyProviderAndroidfrom 14:0 · fixed in 14:2026-03-01
  • platform/packages/providers/TelephonyProviderAndroidfrom 15:0 · fixed in 15:2026-03-01
  • platform/packages/providers/TelephonyProviderAndroidfrom 16-qpr2-next:0 · fixed in 16-qpr2-next:2026-03-01
  • platform/packages/providers/TelephonyProviderAndroidfrom 16:0 · fixed in 16:2026-03-01

Full record on NVD

Fix

No fix published by the sources we read yet. NVD record

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
Published
2026-03-02
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-5m88-975h-rg6f

Frequently asked questions

What is CVE-2025-48609?

In multiple functions of MmsProvider.java, there is a possible way to arbitrarily delete files which affect telephony, SMS, and MMS functionalities due to a path traversal error. This could lead to local denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.

Is CVE-2025-48609 actively exploited?

Active exploitation of CVE-2025-48609 has not been confirmed. Its EPSS score was 0.3% on 2026-11-03, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2025-48609?

CVE-2025-48609 has a CVSS v3 base score of 9.1 (CRITICAL severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H.

Running platform/packages/providers/Tele? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, October 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record