CVE-2026-0075: SQL Injection

Published Jun 1, 2026
·
Updated

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.

Affected Software

6 affected components
Google Android=14.0
Google Android=15.0
Google Android=16.0
Google Android=16.0-qpr2_beta_1
Google Android=16.0-qpr2_beta_2
Google Android=16.0-qpr2_beta_3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Compensating control

    Restrict access to the contacts database and the vulnerable application until code is fixed: tighten file and database permissions, limit local user accounts that can access the database, remove unnecessary privileges from local accounts, and disable or block interfaces to the contacts data for untrusted users.

  2. Compensating control

    Enable and monitor detailed logging and alerting for the contacts database and the application: log database queries and access attempts, audit for anomalous or privileged queries that could indicate exploitation, and configure alerts for suspicious activity to support rapid detection and response.

  3. Operational

    Identify and remediate the SQL injection in the code paths that access the contacts database: locate the vulnerable functions, replace dynamic/concatenated SQL with parameterized queries or prepared statements, add proper input validation and sanitization, and ensure database queries run with least-privilege accounts.

  4. Operational

    If exploitation is suspected or confirmed, perform incident response: investigate affected hosts for indicators of compromise, contain and remediate impacted systems (rebuild or restore from trusted backups as needed), and rotate any credentials or secrets that may have been exposed.

Event History

Jun 1, 2026
CVE Published
via MITRE·09:14 PM
Data Sourced
via MITRE·09:14 PM
DescriptionWeakness
Data Sourced
via NVD·10:16 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-0075?

CVE-2026-0075 has a severity rating of high with a CVSS score of 7.8.

2

How do I fix CVE-2026-0075?

To fix CVE-2026-0075, update your Google Android software to the latest version as provided in the security bulletin.

3

What does CVE-2026-0075 affect?

CVE-2026-0075 affects multiple functions within the Google Android operating system.

4

Can CVE-2026-0075 be exploited without user interaction?

Yes, CVE-2026-0075 can be exploited without any user interaction required.

5

What kind of vulnerability is CVE-2026-0075?

CVE-2026-0075 is a SQL injection vulnerability that may allow local escalation of privilege.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203