How severe is CVE-2026-0047?

CVE-2026-0047 has a CVSS 3.x base score of 8.4, rated high severity. It is exploitable over local access with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2026-0047 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (4th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-0047?

CVE-2026-0047 primarily affects Google Android. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2026-0047?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2026-0047 have an EU (EUVD) identifier?

Yes. CVE-2026-0047 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-9251.

When was CVE-2026-0047 published?

CVE-2026-0047 was published on 2026-03-02 and last updated on 2026-06-17.

CVE-2026-0047

CVE-2026-0047 is a high-severity vulnerability in Google Android with a CVSS 3.x base score of 8.4. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-280.

Key facts

Severity: High (CVSS 3.x base score 8.4)
EPSS exploit prediction: 0% (4th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-9251
Weakness: CWE-280
Affected product: Google Android
Published: 2026-03-02
Last modified: 2026-06-17

Description

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.

Frequently asked questions

What is CVE-2026-0047?: 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.
How severe is CVE-2026-0047?: CVE-2026-0047 has a CVSS 3.x base score of 8.4, rated high severity. It is exploitable over local access with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2026-0047 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (4th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-0047?: CVE-2026-0047 primarily affects Google Android. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2026-0047?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2026-0047 have an EU (EUVD) identifier?: Yes. CVE-2026-0047 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-9251.
When was CVE-2026-0047 published?: CVE-2026-0047 was published on 2026-03-02 and last updated on 2026-06-17.

References

https://source.android.com/docs/security/bulletin/2026/2026-03-01

Affected products (3)

cpe:2.3:o:google:android:16.0:qpr2_beta_1:*:*:*:*:*:*
cpe:2.3:o:google:android:16.0:qpr2_beta_2:*:*:*:*:*:*
cpe:2.3:o:google:android:16.0:qpr2_beta_3:*:*:*:*:*:*

More vulnerabilities in Google Android

CVE-2026-0092 — Critical (CVSS 10.0): In Package Manager, there is a possible device lock controller bypass due to a missing permission check. This could…
CVE-2025-48611 — Critical (CVSS 10.0): In DeviceId of DeviceId.java, there is a possible desync in persistence due to a missing bounds check. This could lead…
CVE-2015-8073 — Critical (CVSS 10.0): mediaserver in Android 4.4 and 5.1 before 5.1.1 LMY48X allows remote attackers to execute arbitrary code or cause a…
CVE-2015-8072 — Critical (CVSS 10.0): mediaserver in Android 4.4 through 5.x before 5.1.1 LMY48X and 6.0 before 2015-11-01 allows remote attackers to execute…
CVE-2015-6610 — Critical (CVSS 10.0): libstagefright in Android before 5.1.1 LMY48X and 6.0 before 2015-11-01 allows attackers to gain privileges or cause a…
CVE-2015-6609 — Critical (CVSS 10.0): libutils in Android before 5.1.1 LMY48X and 6.0 before 2015-11-01 allows remote attackers to execute arbitrary code or…

All CVEs affecting Google Android →

Other CWE-280 vulnerabilities

CVE-2025-46066 — Critical (CVSS 9.9): An issue in Automai Director v.25.2.0 allows a remote attacker to escalate privileges
CVE-2025-6573 — Critical (CVSS 9.8): Kernel software installed and running inside an untrusted/rich execution environment (REE) could leak information from…
CVE-2024-24116 — Critical (CVSS 9.8): An issue in Ruijie RG-NBS2009G-P RGOS v.10.4(1)P2 Release(9736) allows a remote attacker to gain privileges via the…
CVE-2026-41566 — Critical (CVSS 9.4): Improper Handling of Insufficient Permissions or Privileges vulnerability in Apache Kvrocks. This issue affects Apache…
CVE-2024-1608 — Critical (CVSS 9.1): In OPPO Usercenter Credit SDK, there's a possible escalation of privilege due to loose permission check, This could…
CVE-2026-24096 — High (CVSS 8.8): Insufficient permission validation on multiple REST API Quick Setup endpoints in Checkmk 2.5.0 (beta) before version…

Browse all CWE-280 vulnerabilities →