CVE-2025-48571

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreMEDIUM confidence

Score 4.3 from GitHub Security Advisory published 2026-06-17. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 4.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this week
4.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In multiple functions of btm_sec.cc, there is a possible way for an attacker to intercept SMS messages due to a logic error in the code. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is needed for exploitation.

CVSS v3
4.3
EG Score
4.3(medium)
EG Risk
24(Track)
EG Risk 24/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity43% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
9.0%
KEV
Not listed

Published

June 17, 2026

Last Modified

June 17, 2026

Advisory Details (1)

Auto-updated Jun 19, 2026
No patch confirmed yet.
generic

Android 17 Security Release Notes  |  Android Open Source Project

https://source.android.com/docs/security/bulletin/android-17

Vendor Advisories for CVE-2025-48571(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 73× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 02:57 UTCEG score recompute
  2. 2026-07-22 14:07 UTCEPSS rescore
  3. 2026-07-22 14:07 UTCEPSS rescore
  4. 2026-07-21 15:24 UTCEPSS rescore
  5. 2026-07-20 17:07 UTCEPSS rescore
  6. 2026-07-19 14:30 UTCEPSS rescore
  7. 2026-07-19 14:30 UTCEPSS rescore
  8. 2026-07-19 02:28 UTCEPSS rescore
  9. 2026-07-19 02:28 UTCEPSS rescore
  10. 2026-07-18 10:04 UTCEPSS rescore
  11. 2026-07-16 17:02 UTCEPSS rescore
  12. 2026-07-16 17:02 UTCEPSS rescore
  13. 2026-07-16 14:38 UTCGHSA enrichment
  14. 2026-07-15 16:57 UTCEPSS rescore
  15. 2026-07-15 16:57 UTCEPSS rescore
  16. 2026-07-15 14:57 UTCGHSA enrichment
  17. 2026-07-15 01:59 UTCEPSS rescore
  18. 2026-07-15 01:59 UTCEPSS rescore
  19. 2026-07-14 12:05 UTCGHSA enrichment
  20. 2026-07-13 22:29 UTCEPSS rescore
  21. 2026-07-13 22:29 UTCEPSS rescore
  22. 2026-07-13 12:27 UTCGHSA enrichment
  23. 2026-07-13 06:12 UTCEPSS rescore
  24. 2026-07-12 12:46 UTCGHSA enrichment
  25. 2026-07-12 05:46 UTCEPSS rescore
Show 67 more
  1. 2026-07-11 13:07 UTCGHSA enrichment
  2. 2026-07-11 08:27 UTCEPSS rescore
  3. 2026-07-11 08:27 UTCEPSS rescore
  4. 2026-07-10 13:28 UTCGHSA enrichment
  5. 2026-07-09 19:09 UTCEPSS rescore
  6. 2026-07-09 19:09 UTCEPSS rescore
  7. 2026-07-09 13:43 UTCGHSA enrichment
  8. 2026-07-08 15:15 UTCEPSS rescore
  9. 2026-07-08 14:05 UTCGHSA enrichment
  10. 2026-07-07 14:02 UTCGHSA enrichment
  11. 2026-07-07 13:45 UTCEPSS rescore
  12. 2026-07-06 16:27 UTCEPSS rescore
  13. 2026-07-06 16:27 UTCEPSS rescore
  14. 2026-07-06 14:23 UTCGHSA enrichment
  15. 2026-07-06 02:23 UTCEPSS rescore
  16. 2026-07-06 02:23 UTCEPSS rescore
  17. 2026-07-05 12:44 UTCGHSA enrichment
  18. 2026-07-05 02:30 UTCEPSS rescore
  19. 2026-07-04 13:02 UTCGHSA enrichment
  20. 2026-07-04 06:30 UTCEPSS rescore
  21. 2026-07-03 13:22 UTCGHSA enrichment
  22. 2026-07-02 17:01 UTCEPSS rescore
  23. 2026-07-02 11:16 UTCGHSA enrichment
  24. 2026-07-01 15:06 UTCEPSS rescore
  25. 2026-07-01 11:37 UTCGHSA enrichment
  26. 2026-06-30 23:22 UTCEPSS rescore
  27. 2026-06-30 23:22 UTCEPSS rescore
  28. 2026-06-30 11:59 UTCGHSA enrichment
  29. 2026-06-29 14:06 UTCEPSS rescore
  30. 2026-06-29 14:06 UTCEPSS rescore
  31. 2026-06-29 12:21 UTCGHSA enrichment
  32. 2026-06-28 14:07 UTCEPSS rescore
  33. 2026-06-28 14:07 UTCEPSS rescore
  34. 2026-06-28 12:42 UTCGHSA enrichment
  35. 2026-06-28 04:55 UTCEPSS rescore
  36. 2026-06-28 04:55 UTCEPSS rescore
  37. 2026-06-27 13:03 UTCGHSA enrichment
  38. 2026-06-27 03:08 UTCEPSS rescore
  39. 2026-06-26 13:23 UTCGHSA enrichment
  40. 2026-06-25 13:49 UTCEPSS rescore
  41. 2026-06-25 13:49 UTCEPSS rescore
  42. 2026-06-25 13:42 UTCGHSA enrichment
  43. 2026-06-24 14:04 UTCEPSS rescore
  44. 2026-06-24 14:04 UTCEPSS rescore
  45. 2026-06-24 14:04 UTCGHSA enrichment
  46. 2026-06-23 21:32 UTCEPSS rescore
  47. 2026-06-23 21:32 UTCEPSS rescore
  48. 2026-06-23 14:22 UTCGHSA enrichment
  49. 2026-06-22 14:42 UTCGHSA enrichment
  50. 2026-06-22 14:25 UTCEPSS rescore
  51. 2026-06-22 14:25 UTCEPSS rescore
  52. 2026-06-21 15:02 UTCGHSA enrichment
  53. 2026-06-21 14:56 UTCEPSS rescore
  54. 2026-06-21 14:56 UTCEPSS rescore
  55. 2026-06-21 01:59 UTCEPSS rescore
  56. 2026-06-21 01:59 UTCEPSS rescore
  57. 2026-06-20 15:22 UTCGHSA enrichment
  58. 2026-06-19 19:25 UTCEPSS rescore
  59. 2026-06-19 19:25 UTCEPSS rescore
  60. 2026-06-19 15:42 UTCGHSA enrichment
  61. 2026-06-18 17:52 UTCEPSS rescore
  62. 2026-06-18 17:52 UTCEPSS rescore
  63. 2026-06-18 16:03 UTCGHSA enrichment
  64. 2026-06-17 17:52 UTCEPSS rescore
  65. 2026-06-17 17:52 UTCEPSS rescore
  66. 2026-06-17 16:23 UTCEG score recompute
  67. 2026-06-17 15:50 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2025-48571?
CVE-2025-48571 is a medium vulnerability published on June 17, 2026. In multiple functions of btm_sec.cc, there is a possible way for an attacker to intercept SMS messages due to a logic error in the code. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is needed for exploitation.
When was CVE-2025-48571 disclosed?
CVE-2025-48571 was first published in the National Vulnerability Database on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-48571 actively exploited?
CVE-2025-48571 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 9.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-48571?
CVE-2025-48571 has a CVSS v3.1 base score of 4.3 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2025-48571?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-48571, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-48571

Explore →

Is Your Infrastructure Affected by CVE-2025-48571?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs