PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-0013 Google CVE debrief

AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-03-02T19:16:29.803Z and has not been modified since then. The NVD entry is currently Modified. This vulnerability exists in the setupLayout of PickActivity.java, allowing any activity to be started as a DocumentsUI app, which could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not required for exploitation. Affected versions include Android 14.0, 15.0, and 16.0. Security teams responsible for Google Android systems, administrators of Android devices, and individuals concerned with local privilege escalation vulnerabilities should be aware of this issue. They should assess their exposure, apply patches or mitigations, and monitor for potential exploitation attempts. Additionally, security teams should review and enforce secure configurations for DocumentsUI and related components to prevent potential misuse. This vulnerability may impact organizations using affected Android versions, and proactive measures are recommended to mitigate potential risks. It is also important for security teams to verify and enforce secure configurations for DocumentsUI and related components to prevent potential misuse. Security teams should conduct thorough inventory checks to identify and update vulnerable systems, and implement compensating controls to monitor and restrict potentially malicious activities. Individuals using affected Android versions should be cautious and ensure their devices are updated with the latest security patches. Furthermore, security teams should monitor for and respond to potential exploitation attempts, and track exceptions, retest remediated assets, and close the item only after evidence is documented. Security teams should also consider implementing additional security measures, such as monitoring and detection, to identify and respond to potential threats. Finally, security teams should review and apply patches provided by Google for affected Android versions, and conduct thorough inventory checks to identify and update vulnerable systems. The goal is to minimize potential risks and help

Vendor
Google
Product
Android
CVSS
HIGH 8.4
CISA KEV
Not listed in stored evidence
Original CVE published
2026-03-02
Original CVE updated
2026-08-22
Advisory published
2026-03-02
Advisory updated
2026-08-22

Who should care

Security teams responsible for Google Android systems, administrators of Android devices, and individuals concerned with local privilege escalation vulnerabilities should be aware of this issue. They should assess their exposure, apply patches or mitigations, and monitor for potential exploitation attempts. Additionally, security teams should review and enforce secure configurations for DocumentsUI and related components to prevent potential misuse. This vulnerability may impact organizations using affected Android versions, and proactive measures are recommended to mitigate potential risks. It is also important for security teams to verify and enforce secure configurations for DocumentsUI and related components to prevent potential misuse. Security teams should conduct thorough inventory checks to identify and update vulnerable systems, and implement compensating controls to monitor and restrict potentially malicious activities. Individuals using affected Android versions should be cautious and ensure their devices are updated with the latest security patches. Furthermore, security teams should monitor for and respond to potential exploitation attempts, and track exceptions, retest remediated assets, and close the item only after evidence is documented. Security teams should also consider implementing additional security measures, such as monitoring and detection, to identify and respond to potential threats. Finally, security teams should review and apply patches provided by Google for affected Android versions, and conduct thorough inventory checks to identify and update vulnerable systems. The goal is to minimize potential risks and prevent exploitation of this vulnerability. By taking proactive measures, security teams can help protect their organizations from potential threats. Security teams should also consider the potential operational impact of this vulnerability and take steps to mitigate it. This may involve implementing additional security controls, such as compensating controls, to monitor and restrict potentially malicious activities. By doing so, security teams can help prevent potential exploitation of this vulnerability and minimize its impact.

Technical summary

The setupLayout function in PickActivity.java contains a vulnerability that allows any activity to be started as a DocumentsUI app, leading to local escalation of privilege. This issue affects Google Android versions 14.0, 15.0, and 16.0. No user interaction is required for exploitation. The vulnerability is rated HIGH with a CVSS score of 8.4, indicating a significant elevation of privilege vulnerability in Google Android.

Defensive priority

CVE-2026-0013 is rated HIGH with a CVSS score of 8.4, indicating a significant elevation of privilege vulnerability in Google Android. Immediate attention is required to assess and mitigate potential risks.

Recommended defensive actions

  • Review and apply patches provided by Google for affected Android versions.
  • Conduct thorough inventory checks to identify and update vulnerable systems.
  • Implement compensating controls to monitor and restrict potentially malicious activities.
  • Verify and enforce secure configurations for DocumentsUI and related components.
  • Monitor for and respond to potential exploitation attempts.

Evidence notes

The vulnerability exists in the setupLayout of PickActivity.java, allowing any activity to be started as a DocumentsUI app, which could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not required for exploitation. Affected versions include Android 14.0, 15.0, and 16.0. The information provided is based on available data and may not cover all potential impacts or scenarios. Further verification and assessment are recommended to ensure comprehensive understanding and mitigation.

Official resources

AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-03-02T19:16:29.803Z and has not been modified since then.