# CVE-2026-9668: SQL injection vulnerability in ZTE SCP product

> Authenticated attackers can inject SQL to bypass authentication and execute arbitrary database queries in ZTE SCP products.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Aug 2026
- **Updated:** 26 Aug 2026
- **Also known as:** GHSA-xhr9-v6fq-9x9p

## What is CVE-2026-9668?

CVE-2026-9668 is a medium-severity SQL injection vulnerability in ZTE SCP, published on 26 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

With legitimate user credentials in hand, attackers can construct malicious SQL statements to bypass authentication logic and execute arbitrary database queries directly. This will consequently lead to slow database queries and expanded query coverage. This vulnerability features a low exploitation threshold, wide scope of impact, requires no external privilege escalation, and is classified as a high-priority fix.

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

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


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

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

## Is CVE-2026-9668 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-9668 is a medium-severity SQL injection vulnerability in ZTE SCP, published on 26 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-9668 in the wild and no public exploit code.

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

## Sources

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

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