CVE-2026-0011
Google Android vulnerability
- Published2 Mar 2026
Description
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HAffected products
Remediation
No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.
References
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-0011 being actively exploited?
CVE-2026-0011 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.14%.
How severe is CVE-2026-0011?
CVE-2026-0011 has a CVSS 3.1 base score of 8.4, rated high. EPSS estimates a 0.14% probability of exploitation.
Which products are affected by CVE-2026-0011?
Affected products include Google Android.
How do I fix CVE-2026-0011?
Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-0011 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.