dbcve.org
Archer Ax53 FirmwareOperating system · Tp Link

CVE-2026-0834

HIGH · 8.8 CVSS v3.1 Published 2026-01-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/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
Logic vulnerability in TP-Link Archer C20 v5, 6.0, Archer AX53 v1.0 and TL-WR841N v13 (TDDP module) allows unauthenticated adjacent attackers to execute administrative commands including factory reset and device reboot without credentials. Attackers on the adjacent network can remotely trigger factory resets and reboots without credentials, causing configuration loss and interruption of device availability. This issue affects Archer C20 v6.0 < V6_251031, Archer C20 v5 <EU_V5_260317 or < US_V5_260419 Archer AX53 v1.0 < V1_251215 TL-WR841N v13 < 0.9.1 Build 20231120 Rel.62366

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

Logic vulnerability in the TP-Link TDDP (Diagnostic Debug Protocol) module on Archer C20 v5/v6, Archer AX53 v1.0, and TL-WR841N v13 allows adjacent network attackers to bypass authentication and execute privileged administrative commands including factory reset and device reboot without any credentials.

MitigationIsolate affected devices in a secure network segment to limit adjacent attack surface, disable TDDP protocol if possible, and apply vendor firmware updates (C20 v6>=V6_251031, C20 v5>=EU_V5_260317/US_V5_260419, AX53 v1>=V1_251215, TL-WR841N v13>=0.9.1 Build 20231120) once available.

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
Archer Ax53 FirmwareOperating system
Affected:= 1.0
Archer C20 FirmwareOperating system
Affected:= 6.0

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

CVSS:3.1/AV:A/AC:L/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. Identify your router model
    Check the device label on the router chassis or access the web management interface (typically 192.168.0.1) and navigate to Status or System Tools > Device Info to confirm the exact model number
    Affected if Model is TP-Link Archer C20 (any version), Archer AX53, or TL-WR841N v13
  2. Check installed firmware version
    Access the router web interface > System Tools > Firmware Upgrade or Status page and note the firmware version shown
    Affected if Firmware version is 1.0 (Archer AX53) or 6.0 (Archer C20), or matches any version prior to the fixed releases (Archer C20 v6.0 < V6_251031, Archer C20 v5 < EU_V5_260317/US_V5_260419, Archer AX53 v1.0 < V1_251215, TL-WR841N v13 < 0.9.1 Build 20231120 Rel.62366)
  3. Verify TDDP service exposure
    From a device on the same local network, run a UDP port scan against the router IP address targeting port 2989 using: nmap -sU -p 2989 -sV <router_ip>
    Affected if UDP port 2989 is open and the TDDP service is responsive on the local network

You are affected if your device model matches one of the affected models (Archer C20, Archer AX53 v1.0, TL-WR841N v13) AND your firmware version falls within the vulnerable version range AND the TDDP service (UDP 2989) is accessible from your local 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

Isolate affected devices in a secure network segment to limit adjacent attack surface, disable TDDP protocol if possible, and apply vendor firmware updates (C20 v6>=V6_251031, C20 v5>=EU_V5_260317/US_V5_260419, AX53 v1>=V1_251215, TL-WR841N v13>=0.9.1 Build 20231120) once available.

Recommended fix High confidence

Upgrade to firmware V6_251031 (Archer C20 v6.0), EU_V5_260317 (Archer C20 v5 EU), US_V5_260419 (Archer C20 v5 US), V1_251215 (Archer AX53 v1.0), or 0.9.1 Build 20231120 Rel.62366 (TL-WR841N v13) or later as applicable

  1. 1. Identify your TP-Link device model and current firmware version from the device's web management interface or status page.
  2. 2. Visit the official TP-Link support website (www.tp-link.com) and navigate to the Downloads section for your specific device model.
  3. 3. Download the appropriate fixed firmware version: For Archer C20 v6.0, download version V6_251031 or later; For Archer C20 v5 (EU), download version EU_V5_260317 or later; For Archer C20 v5 (US), download version US_V5_260419 or later; For Archer AX53 v1.0, download version V1_251215 or later; For TL-WR841N v13, download version 0.9.1 Build 20231120 Rel.62366 or later.
  4. 4. Access the device's web management interface and navigate to the Firmware Upgrade or System Tools section.
  5. 5. Upload the downloaded firmware file and wait for the upgrade process to complete - do not power off the device during this process.
  6. 6. After the device reboots, verify the new firmware version is installed correctly.
  7. 7. After upgrading, consider changing the device administrator password and reviewing network access controls to limit exposure to adjacent network attackers.
Caveat Firmware upgrades on embedded devices may reset configuration to defaults; back up current settings before upgrading if possible

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

Fix this in Archer Ax53 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0834 — 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-0834 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