PoC Exploit Released for Android CVE-2026-0075 Allowing Contact Theft Without READ_CONTACTS Permission

A researcher has published a proof-of-concept exploit for CVE-2026-0075 affecting Android 14, 15, 16 and 16 QPR2. The flaw resided in the ContactsProvider2 component and enabled local applications to extract contact database entries through SQL injection and verbose SQLite error responses, bypassing the need for any user-granted permissions. Google rated the issue high severity and addressed it in the June 2026 security bulletin by stripping detailed JSON error information from responses to unprivileged apps. The publicly available PoC on GitHub deliberately avoids requesting READ_CONTACTS or WRITE_CONTACTS and is intended strictly for lab comparison of patched versus vulnerable builds. No confirmed in-the-wild exploitation has been observed yet, but the release of working code increases risk for devices running older firmware. Users are advised to verify that their devices have received the security patch dated 5 June 2026 or later.

AntiMalwareTranslated from Russian

Read at source

A researcher has published a proof-of-concept exploit for vulnerability CVE-2026-0075 in Android. The flaw resided in the system component ContactsProvider2 and allowed a local application to reach the contacts database via SQL injection even when the user had never granted the READ_CONTACTS permission.

No additional user interaction or confirmation dialogs were required. The vulnerability stemmed from overly verbose SQLite error messages returned by ContactsProvider2 when specially crafted queries triggered database errors. By analyzing these responses, an application without any contact permissions could gradually reconstruct entries from the contacts database.

Google assigned the issue a high severity rating. It affects Android 14, Android 15, Android 16 and Android 16 QPR2, according to the June 2026 Android security bulletin. The official patch removes detailed JSON error information from responses sent to applications lacking contact access rights, replacing it with a generic message.

The PoC exploit published on GitHub intentionally does not request READ_CONTACTS or WRITE_CONTACTS permissions. Its author designed it for controlled laboratory testing to compare the behavior of patched and vulnerable builds. The researcher notes that a successful test on one device does not prove the vulnerability exists on every smartphone running the same Android version.

No confirmed cases of real-world exploitation of CVE-2026-0075 have been observed so far. However, the availability of public exploit code makes it unrealistic to expect older, unpatched firmware to remain safe. Users should check their device security update level in settings and ensure installation of the patch dated 5 June 2026 or newer.

Meridian digestThe week's most consequential security stories, distilled into one briefing.See the digest

More in Vulnerabilities & Exploits

CISA Adds Cisco Secure Firewall and GitLab Flaws to Known Exploited Vulnerabilities Catalog
Telegram for Android Patches Voice Call Vulnerability Enabling Code Execution
Yandex Patches Millions of Stations After eMudhra Certificate Keys Compromised