CVE-2026-0047: High severity Google Android vulnerability

Published Mar 1, 2026
·
Updated

In dumpBitmapsProto of ActivityManagerService.java, there is a possible way for an app to access private information due to a missing permission check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

Affected Software

4 affected componentsFixes available
Google Android
android/platform/frameworks/base>=16-qpr2-next:0<16-qpr2-next:2026-03-01
16-qpr2-next:2026-03-01
android/platform/frameworks/base>=16-qpr2:0<16-qpr2:2026-03-01
16-qpr2:2026-03-01
Google Android=16.0-qpr2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade android/platform/frameworks/base to a version that resolves this vulnerability.

    Fixed in 16-qpr2-next:2026-03-01
  2. Upgrade

    Upgrade android/platform/frameworks/base to a version that resolves this vulnerability.

    Fixed in 16-qpr2:2026-03-01

Event History

Mar 1, 2026
Advisory Published
via OSV·12:00 AM
Data Sourced
via OSV·12:00 AM
DescriptionAffected Software
Mar 2, 2026
CVE Published
via Android·12:00 AM
Data Sourced
via Android·12:00 AM
SeverityWeaknessAffected Software
CVE Published
via MITRE·06:43 PM
Data Sourced
via MITRE·06:43 PM
DescriptionWeakness
Data Sourced
via NVD·07:16 PM
DescriptionSeverityWeaknessAffected Software
May 1, 2026
Exploit Published
via GitHub·08:19 AM

Frequently Asked Questions

1

What is the severity of CVE-2026-0047?

CVE-2026-0047 is classified as a critical vulnerability that allows local escalation of privilege.

2

How do I fix CVE-2026-0047?

To fix CVE-2026-0047, ensure that your affected Android version is updated to a secure release that addresses this vulnerability.

3

What versions of Android are affected by CVE-2026-0047?

CVE-2026-0047 affects Google Android versions 16.0-qpr2_beta_1, 16.0-qpr2_beta_2, and 16.0-qpr2_beta_3.

4

What kind of exploitation is possible with CVE-2026-0047?

CVE-2026-0047 allows an app to access private information without user interaction, due to a missing permission check.

5

Is user interaction required for exploiting CVE-2026-0047?

No, user interaction is not needed for the exploitation of CVE-2026-0047.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203