# CVE-2026-19750: Tenda CH/CP/TX3 SSH hard-coded password

> Attackers can remotely access Tenda CH, CP, and TX3 devices using hard-coded SSH credentials, leading to potential account takeover.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Aug 2026
- **Updated:** 14 Aug 2026
- **Also known as:** GHSA-2vh2-4q7p-6vxp

## What is CVE-2026-19750?

CVE-2026-19750 is a critical vulnerability in Tenda CH, published on 13 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw has been found in Tenda CH, CP and TX3 V21.x/V22.x/V25.x/V26.x/V27.x. Affected by this issue is some unknown functionality of the component SSH. Executing a manipulation can lead to use of hard-coded password. It is possible to launch the attack remotely. The attack requires a high level of complexity. The exploitation is known to be difficult. The exploit has been published and may be used.

Weakness: CWE-259 (Use of Hard-coded Password), CWE-255

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


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

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

## Is CVE-2026-19750 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-19750 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19750 is a critical vulnerability in Tenda CH, published on 13 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-19750 exists.

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

## Sources

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

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