Answer in brief
CVE-2026-19683 records a Unknown severity vulnerability in Unencrypted Credential Transmission in Omada Gateway Dynamic DNS Authentication in Omada Gateways. The current sources do not mark it as known exploited. The current feed maps TP-Link Systems Inc./DR3150 v1 (generic), TP-Link Systems Inc./DR3220v-4G v1 (generic), TP-Link Systems Inc./DR3650v-4G v1 (generic), TP-Link Systems Inc./DR3650v v1 (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps TP-Link Systems Inc./DR3150 v1 (generic), TP-Link Systems Inc./DR3220v-4G v1 (generic), TP-Link Systems Inc./DR3650v-4G v1 (generic), TP-Link Systems Inc./DR3650v v1 (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| TP-Link Systems Inc./DR3150 v1generic | >=0 <1.0.1 Build 20260722 Rel.16854 | 1.0.1 Build 20260722 Rel.16854 |
| TP-Link Systems Inc./DR3220v-4G v1generic | >=0 <1.2.0 Build 20260630 Rel.82652 | 1.2.0 Build 20260630 Rel.82652 |
| TP-Link Systems Inc./DR3650v-4G v1generic | >=0 <1.2.0 Build 20260630 Rel.83347 | 1.2.0 Build 20260630 Rel.83347 |
| TP-Link Systems Inc./DR3650v v1generic | >=0 <1.2.0 Build 20260630 Rel.83311 | 1.2.0 Build 20260630 Rel.83311 |
| TP-Link Systems Inc./ER603WP-4G-Outdoor v1generic | >=0 <1.0.2 Build 20260723 Rel.43271 | 1.0.2 Build 20260723 Rel.43271 |
| TP-Link Systems Inc./ER605 v2generic | >=0 <2.4.4 Build 20260630 Rel.14398 | 2.4.4 Build 20260630 Rel.14398 |
| TP-Link Systems Inc./ER605W v2generic | >=0 <2.0.4 Build 20260723 Rel.43763 | 2.0.4 Build 20260723 Rel.43763 |
| TP-Link Systems Inc./ER701-5G-Outdoor v1generic | >=0 <1.0.3 Build 20260723 Rel.40931 | 1.0.3 Build 20260723 Rel.40931 |
| TP-Link Systems Inc./ER703WP-4G-Outdoor v1generic | >=0 <1.1.7 Build 20260723 Rel.41712 | 1.1.7 Build 20260723 Rel.41712 |
| TP-Link Systems Inc./ER706W-4G v2generic | >=0 <2.1.11 Build 20260723 Rel.41624 | 2.1.11 Build 20260723 Rel.41624 |
| TP-Link Systems Inc./ER706WP-4G v1generic | >=0 <1.1.11 Build 20260723 Rel.41624 | 1.1.11 Build 20260723 Rel.41624 |
| TP-Link Systems Inc./ER706W v1generic | >=0 <1.2.11 Build 20260723 Rel.41567 | 1.2.11 Build 20260723 Rel.41567 |
| TP-Link Systems Inc./ER707-M2 v1generic | >=0 <1.4.4 Build 20260625 Rel.43063 | 1.4.4 Build 20260625 Rel.43063 |
| TP-Link Systems Inc./ER7206 v2generic | >=0 <2.3.5 Build 20260625 Rel.43136 | 2.3.5 Build 20260625 Rel.43136 |
| TP-Link Systems Inc./ER7212PC v2generic | >=0 <2.4.3 Build 20260722 Rel.40250 | 2.4.3 Build 20260722 Rel.40250 |
| TP-Link Systems Inc/ER7406 v1generic | >=0 <1.3.4 Build 20260625 Rel.43136 | 1.3.4 Build 20260625 Rel.43136 |
| TP-Link Systems Inc/ER7412-M2 v1generic | >=0 <1.2.0 Build 20260630 Rel.82947 | 1.2.0 Build 20260630 Rel.82947 |
| TP-Link Systems Inc./ER8411 v1generic | >=0 <1.4.1 Build 20260708 Rel.64832 | 1.4.1 Build 20260708 Rel.64832 |
| TP-Link Systems Inc./v1generic | >=0 <1.2.6 Build 20260723 Rel.41321 | 1.2.6 Build 20260723 Rel.41321 |
Published upstream
Aug 20, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 20, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 20, 2026
A vulnerability exists in the Dynamic DNS (DDNS) functionality of TP-Link Omada Gateways. During communication with a third-party DDNS service, authentication credentials are transmitted over an unencrypted channel. An attacker who can observe or manipulate traffic between an affected device and the DDNS service may obtain sensitive authentication information or interfere with DDNS update operations. Exploitation requires DDNS to be configured, communication with an external DDNS service, and attacker visibility or control of the relevant network path. Successful exploitation may result in disclosure of DDNS account credentials, unauthorized access to DDNS management functionality, or modification of DNS records associated with the affected deployment.
Quoted source text, attributed separately from HOL analysis.