dbcve.org
Ax12 Pro FirmwareOperating system · Tenda

CVE-2026-1610

HIGH · 8.1 CVSS v3.1 Published 2026-01-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable 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
A vulnerability was found in Tenda AX12 Pro V2 16.03.49.24_cn. Affected by this issue is some unknown functionality of the component Telnet Service. Performing a manipulation results in hard-coded credentials. The attack is possible to be carried out remotely. A high degree of complexity is needed for the attack. The exploitation is known to be difficult. The exploit has been made public and could be used.

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

The Tenda AX12 Pro V2 router firmware 16.03.49.24_cn contains hard-coded credentials embedded in the Telnet service component. These credentials allow unauthorized remote authentication to the device's Telnet service.

MitigationUpdate the router firmware to a version that removes the hard-coded credentials, or if unsupported, disable the Telnet service and use more secure remote management alternatives.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Ax12 Pro FirmwareOperating system
Affected:= 16.03.49.24_cn

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
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

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 device model
    Log into the Tenda router web interface or check the device label to verify the exact model is Tenda AX12 Pro V2
    Affected if Device is not a Tenda AX12 Pro V2, then not affected by this specific CVE
  2. Check firmware version
    Navigate to the router's web interface (usually at 192.168.0.1), go to System Settings or Firmware Upgrade section, and record the firmware version displayed
    Affected if Firmware version is not exactly 16.03.49.24_cn, then not affected by this CVE
  3. Verify Telnet service status
    Access the router via SSH or telnet to the router IP and run the command 'netstat -tuln | grep 23' or check the router's web interface under Port Forwarding or System Services to see if Telnet service (port 23) is enabled
    Affected if Telnet service is disabled on the device, then the hardcoded credentials cannot be exploited remotely
  4. Check Telnet network exposure
    From an external network host, run 'telnet <router_public_ip> 23' or use nmap 'nmap -p 23 <router_ip>' to determine if port 23 is accessible from the network
    Affected if Port 23 is blocked by firewall rules and not accessible from untrusted networks, exploitation is not possible even with hardcoded credentials

The environment is affected only if you have a Tenda AX12 Pro V2 running exactly firmware version 16.03.49.24_cn with Telnet service enabled and exposed to the network.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the router firmware to a version that removes the hard-coded credentials, or if unsupported, disable the Telnet service and use more secure remote management alternatives.

Recommended fix Moderate confidence

Latest AX12 Pro firmware version available from Tenda (check www.tenda.com.cn for version newer than 16.03.49.24_cn)

  1. 1. Visit Tenda's official support page at www.tenda.com.cn and navigate to the Downloads/Support section for the AX12 Pro model
  2. 2. Check for available firmware updates newer than version 16.03.49.24_cn
  3. 3. Download the latest stable firmware release provided by Tenda
  4. 4. Access the router web management interface (typically at 192.168.0.1 or 192.168.1.1)
  5. 5. Navigate to the firmware upgrade section (usually under System Tools or Administration)
  6. 6. Upload and apply the new firmware version
  7. 7. After upgrade, verify Telnet service settings and disable Telnet if not required for network administration
  8. 8. If Telnet is required, ensure default credentials have been changed to strong, unique passwords
Caveat Firmware upgrades on consumer routers may reset configuration to defaults; backup current settings before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ax12 Pro Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-1610 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