In enableSystemPackageLPw of Settings.java, there is a possible way to prevent location access from working due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
CVE-2026-0011
HIGHNVD 8.48.4—Trending — 3 sources updated this week
EchelonGraph scoreMEDIUM confidence
Score 8.4 from GitHub Security Advisory (severity: HIGH) published 2026-03-02. NVD baseline CVSS 8.4; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, nvd
8.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.4Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.4
- EG Score
- 8.4(medium)
- EG Risk
- 42(Track)EG Risk 42/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 computedSeverity84% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 2%
- KEV
- Not listed
Published
March 2, 2026
Last Modified
June 17, 2026
References (1)
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 3× in last 7d / 3× 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 14:13 UTCEPSS rescore
- 2026-07-27 13:56 UTCEG score recompute
- 2026-07-27 13:56 UTCGHSA enrichment
Frequently asked(5)
What is CVE-2026-0011?
CVE-2026-0011 is a high vulnerability published on March 2, 2026. In enableSystemPackageLPw of Settings.java, there is a possible way to prevent location access from working due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
When was CVE-2026-0011 disclosed?
CVE-2026-0011 was first published in the National Vulnerability Database on March 2, 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-2026-0011 actively exploited?
CVE-2026-0011 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 98.4% of all scored CVEs.
What is the CVSS score of CVE-2026-0011?
CVE-2026-0011 has a CVSS v3 base score of 8.4 (NVD).
How do I remediate CVE-2026-0011?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-0011, 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-2026-0011
Is Your Infrastructure Affected by CVE-2026-0011?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.