Local contact disclosure via SQL injection
Published Jun 17, 2026 · Updated Jun 17, 2026
SQL injection in Google Android 17 Contacts Provider allows local users to read the contacts database without user interaction. Google identifies the component and flaw class but has not disclosed the affected query path, attacker-controlled field, or missing neutralization operation. Exploitation requires local access but no additional execution privileges, and the documented consequence is disclosure of contacts data.
Summary
What happened
SQL injection in Google Android 17 Contacts Provider allows local users to read the contacts database without user interaction. Google identifies the component and flaw class but has not disclosed the affected query path, attacker-controlled field, or missing neutralization operation. Exploitation requires local access but no additional execution privileges, and the documented consequence is disclosure of contacts data.
The record
- CVE
- CVE-2026-28576
- Published
- Jun 17, 2026
- Updated
- Jun 17, 2026
- Vendor
- Go standard library
- Product
- Android
- Classifications
- CWE-89, T1533
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 17, 2026CVE publishedPublication date reported by the CVE source.
- Jun 17, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=17
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo