# CVE-2026-8029: SQL Injection Vulnerability in ZTE SmartLife App

> Attackers can exploit SQL injection in the ZTE SmartLife app to steal sensitive local privacy data from the feedback database.

- **Severity:** Low 3.9 (`CVSS:3.1/AV:P/AC:H/PR:L/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Aug 2026
- **Updated:** 5 Aug 2026
- **Also known as:** GHSA-4pf2-5j8p-ghjv

## What is CVE-2026-8029?

CVE-2026-8029 is a low-severity SQL injection vulnerability in ZTE SmartLife, published on 5 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The ZTE Smart Life app contains an SQL injection vulnerability that allows attackers to execute UNION SELECT statements to query sensitive data in the feedback.db database across tables, including user accounts, phone numbers, feedback content, and local debug log paths, thereby enabling the theft of local privacy data.

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

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


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

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

## Is CVE-2026-8029 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-8029 is a low-severity SQL injection vulnerability in ZTE SmartLife, published on 5 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-8029 in the wild and no public exploit code.

Affected product: ZTE SmartLife. 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-8029/ (Markdown: https://insights.sbomify.com/CVE-2026-8029/index.md)
```

## Sources

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

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