CVE-2025-26418

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.8 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 100% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

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

In setUserDisclaimerAcknowledged of CarDevicePolicyService.java, there is a possible way to bypass the user dialog when adding an account to a managed device due to a missing permission check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/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
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
0%
KEV
Not listed

Published

June 1, 2026

Last Modified

July 22, 2026

Advisory Details (1)

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

Android Security Bulletin—June 2026  |  Android Open Source Project

https://source.android.com/docs/security/bulletin/2026/2026-06-01

Vendor Advisories for CVE-2025-26418(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 6× in last 7d / 19× 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-29 11:05 UTCGHSA enrichment
  2. 2026-07-28 03:49 UTCGHSA enrichment
  3. 2026-07-27 11:40 UTCGHSA enrichment
  4. 2026-07-26 23:11 UTCEG score recompute
  5. 2026-07-26 23:11 UTCGHSA enrichment
  6. 2026-07-26 14:53 UTCEPSS rescore
  7. 2026-07-23 02:52 UTCEG score recompute▲ 1.90
  8. 2026-07-22 14:07 UTCEPSS rescore
  9. 2026-07-22 14:07 UTCEPSS rescore
  10. 2026-07-21 15:24 UTCEPSS rescore
  11. 2026-07-18 10:03 UTCEPSS rescore
  12. 2026-07-16 01:26 UTCGHSA enrichment
  13. 2026-07-14 05:21 UTCGHSA enrichment
  14. 2026-07-11 13:22 UTCGHSA enrichment
  15. 2026-07-08 16:51 UTCGHSA enrichment
  16. 2026-07-08 15:14 UTCEPSS rescore
  17. 2026-07-07 13:45 UTCEPSS rescore
  18. 2026-07-02 00:14 UTCGHSA enrichment
  19. 2026-06-30 23:16 UTCGHSA enrichment
  20. 2026-06-29 11:28 UTCGHSA enrichment
  21. 2026-06-28 04:55 UTCEPSS rescore
  22. 2026-06-28 04:55 UTCEPSS rescore
  23. 2026-06-28 03:28 UTCGHSA enrichment
  24. 2026-06-27 03:07 UTCGHSA enrichment
  25. 2026-06-26 02:21 UTCGHSA enrichment
Show 45 more
  1. 2026-06-25 01:59 UTCGHSA enrichment
  2. 2026-06-24 01:39 UTCGHSA enrichment
  3. 2026-06-23 21:32 UTCEPSS rescore
  4. 2026-06-23 21:32 UTCEPSS rescore
  5. 2026-06-20 13:45 UTCGHSA enrichment
  6. 2026-06-18 17:52 UTCEPSS rescore
  7. 2026-06-18 17:52 UTCEPSS rescore
  8. 2026-06-18 07:58 UTCGHSA enrichment
  9. 2026-06-17 17:52 UTCEPSS rescore
  10. 2026-06-17 07:38 UTCGHSA enrichment
  11. 2026-06-16 07:17 UTCGHSA enrichment
  12. 2026-06-15 17:48 UTCEPSS rescore
  13. 2026-06-15 06:56 UTCGHSA enrichment
  14. 2026-06-14 23:17 UTCEPSS rescore
  15. 2026-06-14 06:36 UTCGHSA enrichment
  16. 2026-06-13 22:59 UTCEPSS rescore
  17. 2026-06-13 06:15 UTCGHSA enrichment
  18. 2026-06-12 23:11 UTCEPSS rescore
  19. 2026-06-12 05:51 UTCGHSA enrichment
  20. 2026-06-11 13:59 UTCEPSS rescore
  21. 2026-06-11 05:31 UTCGHSA enrichment
  22. 2026-06-10 22:18 UTCEPSS rescore
  23. 2026-06-10 13:22 UTCEPSS rescore
  24. 2026-06-10 05:11 UTCGHSA enrichment
  25. 2026-06-09 04:51 UTCGHSA enrichment
  26. 2026-06-08 14:16 UTCEPSS rescore
  27. 2026-06-08 14:16 UTCEPSS rescore
  28. 2026-06-08 04:26 UTCGHSA enrichment
  29. 2026-06-07 15:24 UTCEPSS rescore
  30. 2026-06-07 15:24 UTCEPSS rescore
  31. 2026-06-07 04:06 UTCGHSA enrichment
  32. 2026-06-06 13:47 UTCEPSS rescore
  33. 2026-06-06 13:47 UTCEPSS rescore
  34. 2026-06-06 03:46 UTCGHSA enrichment
  35. 2026-06-05 22:46 UTCEPSS rescore
  36. 2026-06-05 22:46 UTCEPSS rescore
  37. 2026-06-05 06:10 UTCEPSS rescore
  38. 2026-06-05 06:10 UTCEPSS rescore
  39. 2026-06-05 03:26 UTCEG score recompute▲ 5.90
  40. 2026-06-05 03:26 UTCGHSA enrichment
  41. 2026-06-04 13:11 UTCEPSS rescore
  42. 2026-06-04 13:11 UTCEPSS rescore
  43. 2026-06-02 20:12 UTCEPSS rescore
  44. 2026-06-02 20:12 UTCEPSS rescore
  45. 2026-06-01 21:40 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-26418?
CVE-2025-26418 is a high vulnerability published on June 1, 2026. In setUserDisclaimerAcknowledged of CarDevicePolicyService.java, there is a possible way to bypass the user dialog when adding an account to a managed device due to a missing permission check. This could lead to local escalation of privilege with no additional execution privileges needed. User…
When was CVE-2025-26418 disclosed?
CVE-2025-26418 was first published in the National Vulnerability Database on June 1, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-26418 actively exploited?
CVE-2025-26418 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 100.0% of all scored CVEs.
What is the CVSS score of CVE-2025-26418?
CVE-2025-26418 has a CVSS v3.1 base score of 7.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2025-26418?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-26418, 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-26418

Explore →

Is Your Infrastructure Affected by CVE-2025-26418?

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

Start Free Scan →Browse All CVEs