SQL Injection in Google Android
CVE-2026-0075
- CVSS v3
- 7.8 High
- Public exploits
- 1 repository
- EPSS
- 0.001 · 2.9th percentile
- Published
- 2026-06-01
In multiple functions, there is a possible way to access the contacts database due to a SQL injection. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
Vulnerability class: SQL Injection
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.8 (High). Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
- Attack Vector
- Local
AV:L - Attack Complexity
- Low
AC:L - Privileges Required
- Low
PR:L - User Interaction
- None
UI:N - Scope
- Unchanged
S:U - Confidentiality
- High
C:H - Integrity
- High
I:H - Availability
- High
A:H
EPSS exploit prediction
EPSS 0.001, 2.9th percentile (last changed ); unchanged over 30 days. About EPSS.
Affected products
- Google Android — versions 15.0, 14.0, 15
Weakness classification (CWE)
Public exploits and proof-of-concept code
1 public repository with exploit or proof-of-concept code for this CVE:
- QM4RS/CVE-2026-0075 (14 stars, last pushed 2026-08-12): CVE-2026-0075 — Android ContactsProvider information disclosure via JSON error side-channel, including PoC, root-cause analysis, and patch details.
References
- source.android.com/docs/security/bulletin/2026/2026-06-01 (Vendor Advisory)
This CVE has public exploit evidence. See the latest CVEs with public exploits.