Security readout for executives and security teams
Plain-English summary
CVE-2026-0013 is a high-severity Android privilege-escalation flaw affecting listed Android 14, 15, and 16 versions. A local attacker could abuse the DocumentsUI component to start another activity with unintended authority, potentially compromising data, system integrity, and availability. Exploitation requires no user interaction or existing privileges, but the supplied sources do not establish active exploitation.
Executive priority
Treat this as a high-priority endpoint patching issue because successful exploitation could provide broad local compromise without user interaction. First establish fleet exposure, then accelerate supported updates. Escalate unsupported or unpatchable devices for risk-based replacement or isolation, while recognizing that the supplied evidence does not show active exploitation.
Technical view
A confused-deputy weakness (CWE-441) in setupLayout within PickActivity.java may allow arbitrary activities to be started as a DocumentsUI application. The CVSS 3.1 score is 8.4, with local access, low complexity, no privileges, and no user interaction. The reported impact is high across confidentiality, integrity, and availability.
Likely exposure
Devices running the listed Android 14, 15, or 16 versions may be exposed if they contain the vulnerable DocumentsUI implementation. The bundle does not identify affected builds, manufacturers, security patch levels, or fixed versions, so organizations must compare device details with Google and device-vendor guidance.
Exploitation context
The attack vector is local rather than remotely network-accessible. Exploitation reportedly needs neither user interaction nor prior privileges. However, CVE-2026-0013 is not identified as a KEV entry in the supplied bundle, and no cited evidence confirms exploitation in the wild or public exploit availability.
Researcher notes
The core security-boundary failure is a confused deputy involving DocumentsUI's PickActivity setupLayout path. The record describes arbitrary activity launching under DocumentsUI context but provides no detailed prerequisites, vulnerable code range, affected build matrix, fix commit, or detection indicators. Avoid assuming all devices on the listed major versions are vulnerable without build-level vendor confirmation.
Mitigation direction
- Review Google's March 2026 Android bulletin and applicable device-manufacturer advisories.
- Deploy the relevant Android security update after confirming affected builds and fixed patch levels.
- Prioritize managed Android 14, 15, and 16 devices handling sensitive or privileged data.
- Track devices lacking available updates and apply vendor-recommended interim protections.
Validation and detection
- Inventory Android versions, builds, manufacturers, and security patch levels across managed devices.
- Compare each device's patch level with Google and manufacturer guidance for CVE-2026-0013.
- Verify update installation through device-management records and representative device checks.
- Reassess devices after vendor guidance changes or later CVE record updates.
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-441: 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-0013 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.
Unintended Proxy or Intermediary ('Confused Deputy')
Unintended Proxy or Intermediary ('Confused Deputy') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.