Cleartext TransmissionWeakness · CWE-319

CVE-2026-22079

HIGH · 8.7 CVSS v4.0 Published 2026-01-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
92/100
Remediation priority · Urgent
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
This vulnerability exists in Tenda wireless routers (300Mbps Wireless Router F3 and N300 Easy Setup Router) due to the plaintext transmission of login credentials during the initial login or post-factory reset setup through the web-based administrative interface. An attacker on the same network could exploit this vulnerability by intercepting network traffic and capturing the credentials transmitted in plaintext. Successful exploitation of this vulnerability could allow the attacker to obtain sensitive information and gain unauthorized access to the targeted device.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This vulnerability exists in Tenda F3 and N300 wireless routers where login credentials are transmitted in plaintext during initial login or post-factory reset setup through the web-based administrative interface. An attacker on the same local network can intercept traffic and capture authentication credentials in cleartext.

MitigationEnable HTTPS on the router's administrative interface if supported, or replace affected devices with models that support encrypted management. Network segmentation can limit exposure to local attackers.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm router model is affected
    Access the router's web administrative interface (typically at 192.168.0.1 or 192.168.1.1) and check the device model information, or look for 'Tenda F3' or 'Tenda N300' labeling on the physical device
    Affected if The device is a Tenda F3 or N300 wireless router
  2. Determine if router is in initial setup state
    After a factory reset or fresh power-on, attempt to access the login page; if the router presents a first-time setup wizard or prompts for initial admin password creation rather than an existing login prompt, the device is in the vulnerable state
    Affected if The router is in factory default state or has not completed initial configuration
  3. Verify login page uses unencrypted HTTP
    Check the browser address bar when accessing the admin interface; if the URL shows http:// rather than https://, the login page is accessible over plaintext HTTP
    Affected if The administrative interface login page loads over HTTP (not HTTPS)
  4. Confirm credential submission method
    Use browser developer tools (Network tab) to observe the login form submission; if the POST request goes to an http:// URL without TLS encryption, credentials are transmitted in plaintext
    Affected if Login credentials are submitted over an unencrypted HTTP connection

You are affected if you own a Tenda F3 or N300 router and perform initial setup or post-factory-reset login while the administrative interface communicates over unencrypted HTTP rather than HTTPS.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Enable HTTPS on the router's administrative interface if supported, or replace affected devices with models that support encrypted management. Network segmentation can limit exposure to local attackers.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22079 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-22079 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data