# CVE-2026-28576: SQL injection in Android

> Local attackers can access the contacts database via SQL injection in Android Contacts Provider without user interaction or extra privileges.

- **Severity:** Critical 10.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jun 2026
- **Updated:** 17 Jun 2026
- **Also known as:** GHSA-ph86-9mcx-3p6r

## What is CVE-2026-28576?

CVE-2026-28576 is a critical SQL injection vulnerability in Google Android, published on 17 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Contacts Provider, there is a possible way to access the contacts database due to SQL injection. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-28576?

It affects 1 product.


Products: Google Android.

## How do I fix CVE-2026-28576?

No fix has been published for CVE-2026-28576 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-28576 being exploited?

There is no known exploitation of CVE-2026-28576 in the wild and no public exploit code.

Public exploit code:

- SQL injection vulnerability in Android 17 (AOSP) (github_poc): https://github.com/mobilehackinglab/CVE-2026-28576-poc
- CVE-2026-28576 (GHSA-ph86-9mcx-3p6r) — Android Contacts Provider SQL Injection via targetSdk-gated ENFORCE_STRICT_SQL_CHECKS. Zero-permission boolean-oracle PoC + Red Team app with consent-gated dashboard exfiltration. (github_poc): https://github.com/Aayushbankar/cve-2026-28576

## Other vulnerabilities in Google Android

- [CVE-2026-58704](https://insights.sbomify.com/CVE-2026-58704/): Google Pixel Improper Authorization (high 8.8, exploited in the wild)
- [CVE-2025-48543](https://insights.sbomify.com/CVE-2025-48543/): Android Runtime Use-After-Free (high 8.8, exploited in the wild)
- [CVE-2023-35674](https://insights.sbomify.com/CVE-2023-35674/): Android Framework Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2025-48595](https://insights.sbomify.com/CVE-2025-48595/): Android Framework Integer Overflow (high 8.4, exploited in the wild)
- [CVE-2024-32896](https://insights.sbomify.com/CVE-2024-32896/): Android Pixel Privilege Escalation (high 8.1, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-28576 and fix it if it is affected.

What it is: CVE-2026-28576 is a critical SQL injection vulnerability in Google Android, published on 17 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-28576 in the wild and no public exploit code.

Affected product: Google Android. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-28576/ (Markdown: https://insights.sbomify.com/CVE-2026-28576/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-28576
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-28576
- OSV: https://osv.dev/vulnerability/CVE-2026-28576

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-28576/
Summaries are generated and may contain mistakes; the official description above is the record.