# CVE-2026-49007: Information leakage vulnerability in ZTE F689 product

> Attackers can extract hardcoded initial login credentials from the firmware to gain unauthorized access to the web interface.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Aug 2026
- **Updated:** 7 Aug 2026
- **Also known as:** GHSA-8798-3pf8-6h9q

## What is CVE-2026-49007?

CVE-2026-49007 is a high-severity vulnerability in ZTE F689, published on 7 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

By accessing unencrypted information in the device firmware, an attacker can obtain the initial login credentials for the device's web interface.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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


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

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

## Is CVE-2026-49007 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-49007 is a high-severity vulnerability in ZTE F689, published on 7 Aug 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-49007 in the wild and no public exploit code.

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

## Sources

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

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