# CVE-2026-0056: Google Android Framework out-of-bounds read in ResourceTypes.cpp

Source: https://junglewise.ai/threats/cve-2026-0056-google-android-framework-out-of-bounds-read-in-resourcetypes-cpp  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-06-01. Updated: 2026-06-01  
License: CC BY 4.0 with a link back

CVE-2026-0056 · Severity: info · CVSS 5.5 · Published 2026-06-01

A vulnerability in the Android Framework could allow a malicious application installed on a device to access sensitive information it should not be able to see. This occurs due to a technical error in how the system handles certain resource files. An attacker could exploit this without any special permissions or user interaction, potentially compromising user privacy.

Technologies: [Google Android Framework](https://junglewise.ai/threats/technologies/android-framework). Vendors: [Google](https://junglewise.ai/threats/vendors/google).

## Quick answers

**Is CVE-2026-0056 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-0056 being exploited in the wild.

**How severe is CVE-2026-0056?** Informational severity, with a CVSS score of 5.5, published 1 June 2026.

**Which products and versions are affected?** Google Android Framework 14, 15, 16, 16-qpr2.

**Is there a fix for CVE-2026-0056?** A patch was published on 2026-06-05: Security patch level 2026-06-05 or later addresses this issue. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-0056 attacked?** It is attacked with local access, in an operating system.

**Am I affected by CVE-2026-0056?** Check whether you run Google Android Framework at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

An out-of-bounds read vulnerability exists in the 'setTo' function within 'ResourceTypes.cpp' of the Android Framework. The flaw is caused by an incorrect bounds check when processing resources. A local attacker can exploit this to read memory contents, leading to information disclosure. No additional execution privileges or user interaction are required for exploitation. The issue is addressed in the June 2026 Android Security Bulletin for Android versions 14, 15, 16, and 16-qpr2.

## Affected products

- Google Android Framework 14, 15, 16, 16-qpr2

## Timeline

- 2026-06-01: disclosed
- 2026-06-01: advisory
- 2026-06-05: patched: Security patch level 2026-06-05 or later addresses this issue.

## References

- [https://source.android.com/docs/security/bulletin/2026/2026-06-01](https://source.android.com/docs/security/bulletin/2026/2026-06-01)

## Related threats

- [Android Framework out-of-bounds exception in SipAddress telephony](https://junglewise.ai/threats/cve-2026-59623-in-compareteluris-of-sipaddress-cpp-there-is-a-possible-way-to)
- [Google Android Framework privilege escalation via incorrect bounds check](https://junglewise.ai/threats/cve-2026-28580-google-android-framework-privilege-escalation-via-incorrect)
- [Google Android Framework tapjacking in WindowManagerService](https://junglewise.ai/threats/cve-2026-28577-google-android-framework-tapjacking-in-windowmanagerservice)
- [Google Android Framework heap buffer overflow in LoadedArsc.cpp](https://junglewise.ai/threats/cve-2026-0100-google-android-framework-heap-buffer-overflow-in-loadedarsc-cpp)
- [Google Android Framework privilege escalation in launcher process](https://junglewise.ai/threats/cve-2026-0091-google-android-framework-privilege-escalation-in-launcher-process)