dbcve.org
AndroidOperating system · Google

CVE-2026-0075

MEDIUM · 5.9 CVSS v3.1 Published 2026-06-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
64/100
Remediation priority · Elevated
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

SQL injection vulnerability in multiple functions accessing the contacts database allows local privilege escalation without requiring additional execution privileges or user interaction.

MitigationReplace dynamic SQL queries with parameterized queries or prepared statements for all database operations on the contacts database, and implement input validation for any user-controlled data.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AndroidOperating system
Affected:= 14.0= 15.0= 16.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Android version number
    Go to Settings > About Phone > Android version (or Settings > System > About Phone > Android version) and note the exact version displayed
    Affected if The version shown is exactly 14.0, 15.0, or 16.0
  2. Verify contacts database access
    Check if any application on the device has been granted contacts permissions. Go to Settings > Apps > Permissions > Contacts (or Settings > Privacy > Permission Manager > Contacts) and review which apps have access
    Affected if Any third-party or system app has contacts permission granted, as the vulnerable code executes when contacts database is accessed
  3. Identify contacts database usage
    Review installed applications that interact with the contacts provider. Check Settings > Apps for any contacts-related apps, dialers, or communication apps that may query the contacts database
    Affected if Applications that read/write contacts are installed and active on the device
  4. Check for suspicious contact queries
    Use adb logcat to monitor database queries involving the contacts provider (content://com.android.contacts/). Run: adb logcat | grep -i "contacts" to observe query patterns
    Affected if Unusual or unsanitized SQL-like patterns appear in contacts database queries in the log output

A device is affected if it runs Android version 14.0, 15.0, or 16.0 and has applications with contacts database access, since the vulnerability resides in contacts database query handling functions in those specific versions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries with parameterized queries or prepared statements for all database operations on the contacts database, and implement input validation for any user-controlled data.

Recommended fix Moderate confidence

Latest Android Security Bulletin (monthly update containing fix for CVE-2026-0075)

  1. 1. Check current Android security patch level: Go to Settings > About Phone > Security Patch Level
  2. 2. Ensure Android system is updated to the latest available security update
  3. 3. For Android 14.0, 15.0, and 16.0 devices, apply the latest monthly security bulletin update that addresses this vulnerability
  4. 4. Verify the security patch level reflects the fix date (typically the latest available security update)
Caveat Standard security update - minimal risk; verify apps function normally after update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory
  • Consultation5.0 h
  • Implementation10.0 h
  • Testing5.0 h
  • Review / QA3.0 h
23.0 hours of engineering $4,090
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0075 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-0075 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data