In DeviceId of DeviceId.java, there is a possible desync in persistence due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
CVE-2025-48611
CRITICALNVD 7.810.0▲
EchelonGraph scoreMEDIUM confidence
Score 10.0 from GitHub Security Advisory (severity: CRITICAL) published 2026-03-10. NVD baseline CVSS 7.8; sources differ by 2.2.
Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, nvd
10.0EG
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.
- CVSS v3
- 7.8
- EG Score
- 10.0(medium)
- EG Risk
- 50(Track)EG Risk 50/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 computedSeverity100% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 9%
- KEV
- Not listed
Published
March 10, 2026
Last Modified
June 17, 2026
References (1)
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 2× in last 7d / 2× 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-27 13:44 UTCEG score recompute
- 2026-07-27 13:44 UTCGHSA enrichment
Related CVEs(same CWE)
Same CWE
10 shownCWE-120
- CVE-2010-10016EG 10.0CRITICAL
- CVE-2012-10035EG 10.0CRITICAL
- CVE-2011-4862EG 10.0EPSS p100HIGH
- CVE-2008-3496EG 10.0HIGH
- CVE-2007-1770EG 10.0EPSS p97HIGH
- CVE-2002-1337EG 10.0EPSS p99HIGH
- CVE-2001-0554EG 10.0EPSS p98HIGH
- CVE-2001-0191EG 10.0EPSS p92HIGH
- CVE-1999-1237EG 10.0EPSS p94HIGH
- CVE-1999-0385EG 10.0EPSS p97HIGH
Frequently asked(5)
What is CVE-2025-48611?
CVE-2025-48611 is a critical vulnerability published on March 10, 2026. In DeviceId of DeviceId.java, there is a possible desync in persistence due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
When was CVE-2025-48611 disclosed?
CVE-2025-48611 was first published in the National Vulnerability Database on March 10, 2026, with the most recent update 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-48611 actively exploited?
CVE-2025-48611 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 90.7% of all scored CVEs.
What is the CVSS score of CVE-2025-48611?
CVE-2025-48611 has a CVSS v3 base score of 7.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 10.0.
How do I remediate CVE-2025-48611?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-48611, 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-48611
Is Your Infrastructure Affected by CVE-2025-48611?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.