Security readout for executives and security teams
Plain-English summary
A logic error in Android can let a local attacker disrupt location access and gain elevated privileges without user interaction. Successful exploitation could seriously affect device confidentiality, integrity, and availability. The affected branches listed are Android 14, 15, 16, and 16-qpr2.
Executive priority
Treat this as a high-priority mobile-platform update because exploitation requires neither user interaction nor pre-existing privileges and may compromise all three security-impact categories. First identify affected Android branches, then accelerate applicable vendor remediation. Emergency incident response is not justified solely by the supplied evidence because active exploitation is not established.
Technical view
CVE-2026-0011 affects enableSystemPackageLPw in Settings.java. The logic error can prevent location access from working and enable local privilege escalation. CVSS 3.1 rates it 8.4 with local, low-complexity, no-privilege, no-interaction conditions and high confidentiality, integrity, and availability impact. It maps to CWE-693 and CWE-703.
Likely exposure
Organizations may be exposed where devices run Android 14, 15, 16, or 16-qpr2 without the applicable vendor remediation. The record marks unlisted versions unaffected by default. Actual exposure depends on device build and security-update status, which the supplied bundle does not detail.
Exploitation context
Exploitation requires a local attack path but needs no existing privileges or user interaction. The supplied record is not in KEV and provides no evidence of active exploitation. No exploit maturity, public proof of concept, or observed campaign information is included.
Researcher notes
The disclosed fault is a logic error in Android package settings handling, specifically enableSystemPackageLPw. The bundle does not provide patch commits, root-cause detail, exploit primitives, affected device-build mappings, or test indicators. Researchers should use the vendor bulletin and CVE record for authoritative applicability and remediation details.
Mitigation direction
- Review the March 2026 Android bulletin for the applicable vendor remediation and security-update requirements.
- Obtain device-specific update guidance from manufacturers or enterprise mobility providers.
- Prioritize remediation for affected-version devices handling sensitive data or privileged business applications.
- Restrict untrusted application installation while remediation status remains unresolved.
Validation and detection
- Inventory Android versions, builds, and security patch levels across managed devices.
- Compare each device against the vendor bulletin's affected and remediated configurations.
- Confirm applicable vendor updates installed successfully through endpoint or mobility-management reporting.
- After remediation, verify location services and privilege controls operate normally.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-693: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-703: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-0011 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H2.55.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
8.4HighVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://source.android.com/docs/security/bulletin/2026/2026-03-01CVE reference, google_android · vendor-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Protection Mechanism Failure
Protection Mechanism Failure represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Check or Handling of Exceptional Conditions
Improper Check or Handling of Exceptional Conditions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.