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.
Security readout for executives and security teams
Plain-English summary
Affected Tenda CH, CP, and TX3 cameras contain a hard-coded SSH password that could let a remote attacker gain powerful device access. Successful compromise could expose camera data, alter device operation, or make the device unavailable. Exploitation is rated difficult, but public exploit information increases risk.
Executive priority
Treat internet-reachable affected cameras as an immediate containment priority. Restrict SSH access, identify all affected assets, and seek vendor remediation guidance. Internally isolated devices warrant prompt review because public exploit information exists, but current sources do not confirm active exploitation or provide a fixed version.
Technical view
CVE-2026-19750 affects SSH functionality in Tenda CH, CP, and TX3 devices running listed V21, V22, V25, V26, or V27 releases. It is classified under hard-coded credentials weaknesses CWE-255 and CWE-259. CVSS 4.0 is 9.2, reflecting remote, unauthenticated access with high complexity and potentially high confidentiality, integrity, and availability impact.
Likely exposure
Highest exposure exists where an affected camera's SSH service is reachable from the internet or another untrusted network. Internally reachable devices remain exposed to attackers who already have network access. The sources do not identify exact model variants, default network configuration, SSH port, or whether every firmware build within each listed release family is vulnerable.
Exploitation context
A public exploit has been published, and the CVSS vector marks exploit maturity as proof-of-concept. However, the source bundle reports that exploitation is difficult and requires high attack complexity. The CVE is not listed in CISA KEV, and the supplied evidence does not establish active exploitation.
Researcher notes
The record describes unknown affected SSH functionality and does not disclose the credential, authentication path, firmware-level root cause, or vendor fix. Product naming is broad, with wildcard CPEs and release-family version ranges. Public exploit availability supports elevated concern, but claims of widespread or active exploitation would exceed the supplied evidence.
Mitigation direction
Inventory Tenda CH, CP, and TX3 devices and record their exact firmware versions.
Block untrusted network access to device SSH services using firewall rules or access controls.
Segment affected cameras from business-critical systems and restrict administrative access to trusted management networks.
Check Tenda guidance for fixed firmware or vendor-approved mitigation; no patch is identified in the supplied sources.
Do not assume changing normal administrator passwords removes the separate hard-coded SSH credential.
Validation and detection
Confirm each device model and firmware against the listed V21, V22, V25, V26, and V27 families.
Test from untrusted network segments whether the device's SSH service is reachable, without attempting authentication.
Review device and network logs for unexpected SSH connections, authentication events, or configuration changes.
After remediation, verify SSH is inaccessible from untrusted networks and confirm the installed firmware version.
Monitor Tenda and the CVE record for clarified affected builds and remediation guidance.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-255: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
4CVSS vectors
6Timeline events
1ADP providers
7Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
4 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.