In overrideConfig of CarrierConfigLoader.java, there is a possible way to bypass UID check due to a permissions bypass. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
CVE-2025-48617
Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-17. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.8
- EG Score
- 7.8(medium)
- EG Risk
- 40(Track)EG Risk 40/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 computedSeverity78% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 0%
- KEV
- Not listed
Published
June 17, 2026
Last Modified
June 18, 2026
Advisory Details (1)
Auto-updated Jun 18, 2026Android 17 Security Release Notes | Android Open Source Project
https://source.android.com/docs/security/bulletin/android-17Vendor Advisories for CVE-2025-48617(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 14× in last 7d / 60× 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.
- 2026-07-30 16:27 UTCEPSS rescore
- 2026-07-30 03:58 UTCGHSA enrichment
- 2026-07-29 14:35 UTCGHSA enrichment
- 2026-07-29 02:37 UTCEG score recompute
- 2026-07-29 02:36 UTCGHSA enrichment
- 2026-07-28 15:35 UTCEPSS rescore
- 2026-07-28 01:24 UTCGHSA enrichment
- 2026-07-27 07:34 UTCGHSA enrichment
- 2026-07-26 19:30 UTCEG score recompute
- 2026-07-26 19:30 UTCGHSA enrichment
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-25 14:17 UTCEPSS rescore
- 2026-07-25 14:17 UTCEPSS rescore
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-23 02:57 UTCEG score recompute
- 2026-07-22 14:07 UTCEPSS rescore
- 2026-07-22 14:07 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-16 21:57 UTCGHSA enrichment
- 2026-07-16 17:02 UTCEPSS rescore
- 2026-07-16 17:02 UTCEPSS rescore
- 2026-07-16 09:20 UTCGHSA enrichment
- 2026-07-15 21:21 UTCGHSA enrichment
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
Show 70 moreShow fewer
- 2026-07-15 09:14 UTCGHSA enrichment
- 2026-07-14 21:14 UTCGHSA enrichment
- 2026-07-14 09:15 UTCGHSA enrichment
- 2026-07-13 20:26 UTCGHSA enrichment
- 2026-07-13 08:28 UTCGHSA enrichment
- 2026-07-12 20:19 UTCGHSA enrichment
- 2026-07-12 08:20 UTCGHSA enrichment
- 2026-07-11 20:22 UTCGHSA enrichment
- 2026-07-11 08:24 UTCGHSA enrichment
- 2026-07-10 20:26 UTCGHSA enrichment
- 2026-07-10 08:28 UTCGHSA enrichment
- 2026-07-09 20:27 UTCGHSA enrichment
- 2026-07-09 19:09 UTCEPSS rescore
- 2026-07-09 19:09 UTCEPSS rescore
- 2026-07-09 08:28 UTCGHSA enrichment
- 2026-07-08 20:28 UTCGHSA enrichment
- 2026-07-08 15:15 UTCEPSS rescore
- 2026-07-08 08:30 UTCGHSA enrichment
- 2026-07-07 20:32 UTCGHSA enrichment
- 2026-07-07 13:45 UTCEPSS rescore
- 2026-07-07 02:35 UTCGHSA enrichment
- 2026-07-06 14:21 UTCGHSA enrichment
- 2026-07-05 20:13 UTCGHSA enrichment
- 2026-07-05 08:15 UTCGHSA enrichment
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 20:12 UTCGHSA enrichment
- 2026-07-04 08:13 UTCGHSA enrichment
- 2026-07-03 16:56 UTCGHSA enrichment
- 2026-07-03 04:56 UTCGHSA enrichment
- 2026-07-02 17:01 UTCEPSS rescore
- 2026-07-02 16:52 UTCGHSA enrichment
- 2026-07-02 04:54 UTCGHSA enrichment
- 2026-07-01 16:56 UTCGHSA enrichment
- 2026-07-01 15:06 UTCEPSS rescore
- 2026-07-01 04:57 UTCGHSA enrichment
- 2026-06-30 16:57 UTCGHSA enrichment
- 2026-06-30 04:57 UTCGHSA enrichment
- 2026-06-29 16:50 UTCGHSA enrichment
- 2026-06-29 04:48 UTCGHSA enrichment
- 2026-06-28 16:47 UTCGHSA enrichment
- 2026-06-28 04:55 UTCEPSS rescore
- 2026-06-28 04:55 UTCEPSS rescore
- 2026-06-28 04:49 UTCGHSA enrichment
- 2026-06-27 16:51 UTCGHSA enrichment
- 2026-06-27 04:52 UTCGHSA enrichment
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-26 16:47 UTCGHSA enrichment
- 2026-06-26 04:50 UTCGHSA enrichment
- 2026-06-25 16:52 UTCGHSA enrichment
- 2026-06-25 04:52 UTCGHSA enrichment
- 2026-06-24 16:49 UTCGHSA enrichment
- 2026-06-24 04:51 UTCGHSA enrichment
- 2026-06-23 16:51 UTCGHSA enrichment
- 2026-06-23 04:50 UTCGHSA enrichment
- 2026-06-22 16:51 UTCGHSA enrichment
- 2026-06-22 04:45 UTCGHSA enrichment
- 2026-06-21 16:38 UTCGHSA enrichment
- 2026-06-21 04:29 UTCGHSA enrichment
- 2026-06-20 16:19 UTCGHSA enrichment
- 2026-06-20 04:21 UTCGHSA enrichment
- 2026-06-19 16:19 UTCGHSA enrichment
- 2026-06-19 04:18 UTCGHSA enrichment
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-18 16:19 UTCGHSA enrichment
- 2026-06-18 04:21 UTCGHSA enrichment
- 2026-06-17 17:52 UTCEPSS rescore
- 2026-06-17 17:52 UTCEPSS rescore
- 2026-06-17 16:24 UTCEG score recompute
- 2026-06-17 15:50 UTCNVD updatefirst tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-862
- CVE-2013-3960EG 9.9CRITICAL
- CVE-2015-10143EG 9.8CRITICAL
- CVE-2016-11036EG 9.8CRITICAL
- CVE-2018-11541EG 9.8CRITICAL
- CVE-2011-4183NVD 6.5EG 9.8CRITICAL
- CVE-2018-10251EG 9.8EPSS p91CRITICAL
- CVE-2018-1217EG 9.8EPSS p99CRITICAL
- CVE-2018-0015EG 9.8CRITICAL
- CVE-2017-12582EG 9.8CRITICAL
- CVE-2017-1000056EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2025-48617?
When was CVE-2025-48617 disclosed?
Is CVE-2025-48617 actively exploited?
What is the CVSS score of CVE-2025-48617?
How do I remediate CVE-2025-48617?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2025-48617
Is Your Infrastructure Affected by CVE-2025-48617?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.