CVE-2026-0013
Google Android 14.0 … 16.0
Raw vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2026-0013 is a high-severity Confused Deputy (CWE-441) vulnerability in Google Android. Its CVSS base score is 8.4 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Proxy (T1090); ranked at the 0.6th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-16 (Security and Privacy Attributes) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-0013 is a vulnerability in the setupLayout method of PickActivity.java within Android's DocumentsUI component. It stems from a confused deputy issue (CWE-441) that allows an attacker to start any activity as the DocumentsUI app, enabling local escalation of privilege without additional execution privileges or user interaction. The vulnerability carries a CVSS v3.1 base score of 8.4 (AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) and was published on 2026-03-02.
A local attacker requires only local access to the Android device with no privileges (PR:N) and can exploit the issue with low complexity (AC:L) and no user interaction (UI:N). Exploitation allows the attacker to escalate privileges, resulting in high impacts to confidentiality, integrity, and availability (C:H/I:H/A:H).
For mitigation details, refer to the Android security bulletin at https://source.android.com/docs/security/bulletin/2026/2026-03-01.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-9231
Vulnerability Data
In setupLayout of PickActivity.java, there is a possible way to start any activity as a DocumentsUI app due to a confused deputy. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not…
more
needed for exploitation.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V3.2.1V3.5.1V3.5.3V3.5.8
Mitigating Controls (NIST 800-53 r5) AI
Associating and preserving security attributes such as original source identity prevents the loss of provenance that creates the confused deputy.
Information flow enforcement requires preserving and checking source attributes before forwarding requests outside the trust boundary.
Access enforcement directly stops a component from acting on forwarded requests without verifying original source authorizations.
Boundary protection limits and inspects external forwarding, reducing the ability of an intermediary to act as an unintended proxy.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Proper conveyance and verification of original identity assertions directly prevents loss of request source when forwarding.
Enforcing least-privilege authorizations on forwarded requests reduces confused-deputy abuse even if source identity is lost.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Access-control rules can limit which upstream identities may cause the product to act on their behalf, reducing confused-deputy risk.
Proper identity management ensures the original requester identity is preserved and validated before the product forwards requests.
Explicit access-rights assignment can restrict the product’s ability to act as an unintended proxy for external actors.
Privileged-access controls limit the rights the product may exercise on behalf of upstream callers, mitigating confused-deputy abuse.
Network-security controls can enforce source validation and prevent the product from blindly proxying traffic to external actors.
Secure-SDLC practices include design reviews that detect and eliminate confused-deputy proxy patterns before deployment.