/

CVE-2026-19750

Severity:

HIGH RISK

(8.1)

Hard-Coded Password (CWE-259) in Tenda Routers SSH

CVE-2026-19750

Deferred

Vulnerability type

Category:

Hard-Coded Credentials

CWE:

CWE-255, CWE-259

Impact:

Unauthorized Remote Access

Severity:

HIGH RISK

(8.1)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A high-severity credential-management flaw in the SSH component of affected Tenda CH, CP, and TX3 router releases may expose a hard-coded password. Because the SSH service can be reached remotely, an attacker who satisfies the difficult exploitation conditions could gain unauthorized access to the device.

Affected context

The issue occurs in certain Tenda CH, CP, and TX3 devices running V21.x, V22.x, V25.x, V26.x, or V27.x software where SSH functionality relies on a hard-coded password. Risk is higher when SSH is reachable from an untrusted network and the embedded credential is accepted by the affected service.

Exploit preconditions

  • Attack surface: SSH service exposed over a network
  • Required access: Network reachability to the affected device; exploitation may also depend on discovering or using the embedded credential
  • Trigger point: Authentication handling within the SSH component
  • Why exploitation is possible: A credential embedded in software or device logic can provide an authentication path that is not unique, easily rotated, or adequately controlled
  • Complexity: The reported attack is remotely launchable but considered difficult and complex

Why this happens

The underlying issue is the use of a password embedded in firmware, application logic, or another device-controlled location. Hard-coded credentials can be recovered, reused across devices, or remain unchanged throughout the product lifecycle, mapping directly to CWE-259: Use of Hard-coded Password and relating to CWE-255: Improper Management of Credentials.

Potential impact

  • An attacker may obtain unauthorized SSH access to the router
  • Device configuration and network settings could be modified
  • Network traffic could be monitored, redirected, or disrupted
  • The device could be used as a foothold for attacks against connected systems
  • Persistent compromise or service interruption could occur

General mitigation guidance

Mitigation generally focuses on removing shared or embedded credentials from authentication paths and ensuring every device has independently managed credentials.

Common defensive patterns include:

  • Replacing hard-coded passwords with unique, securely provisioned credentials
  • Requiring password changes or secure enrollment during initial setup
  • Disabling SSH by default unless it is explicitly needed
  • Restricting SSH exposure through network segmentation, access controls, and management-only interfaces
  • Applying least privilege to SSH accounts and administrative services
  • Using secure credential storage, rotation, and revocation mechanisms
  • Monitoring and limiting administrative access from untrusted networks

How teams detect issues like this

Organizations can look for this class of issue through:

  • Firmware and binary analysis for embedded passwords, credential strings, and authentication constants
  • Static analysis rules identifying credential literals in source code or configuration
  • Code review checks for shared default credentials and non-rotatable administrative accounts
  • Network scans that identify unexpectedly exposed SSH services
  • Authentication-log monitoring for repeated or unusual administrative access
  • Policy enforcement requiring unique device credentials and restricted management-plane exposure
  • Automated security review tools that flag hard-coded secrets and insecure credential handling

Sources

SourceLink
github.comgithub.com/howitouchyou/Tenda-Smart-Camera-Vulnerability/blob/main/Tenda%20Camera%20SSH%20Hard-coded%20Password/Tenda%20Camera%20SSH%20Hard-coded%20Password.md
vuldb.comvuldb.com/cve/CVE-2026-19750
vuldb.comvuldb.com/submit/868524
vuldb.comvuldb.com/vuln/389501
vuldb.comvuldb.com/vuln/389501/cti
tenda.com.cntenda.com.cn/

Frequently asked

questions

Yes. The affected SSH functionality is reachable remotely, although the reported exploitation conditions are considered complex and difficult.

An attacker generally needs network reachability to the device's SSH service and must be able to satisfy the service's authentication and exploitation conditions.

Remove hard-coded credentials from authentication flows, provision unique credentials per device, and restrict or disable SSH when it is not required.

Use secure credential provisioning and storage, require credential rotation, scan firmware and source code for embedded secrets, and enforce network policies that limit administrative service exposure.

Find out what's already
exploitable in your codebase.