dbcve.org
Archer Ax53 FirmwareOperating system · Tp Link

CVE-2025-62673

HIGH · 8.0 CVSS v3.1 Published 2026-02-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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
Heap-based Buffer Overflow vulnerability in TP-Link Archer AX53 v1.0 (tdpserver modules) allows adjacent attackers to cause a segmentation fault or potentially execute arbitrary code via a specially crafted network packet containing a maliciously formed field.This issue affects Archer AX53 v1.0: through 1.3.1 Build 20241120.

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

Heap-based buffer overflow in the tdpserver module of TP-Link Archer AX53 v1.0 allows adjacent network attackers to send a specially crafted packet with a maliciously formed field, triggering overflow and potentially achieving code execution or causing a segmentation fault (DoS).

MitigationApply vendor-supplied firmware update from TP-Link for Archer AX53 v1.0 when available. Until patch is released, restrict network access to the device to trusted adjacent networks only.

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

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

CVSS:3.1/AV:A/AC:L/PR:L/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 device model
    Access the router web interface or check the device label to confirm the model is TP-Link Archer AX53
    Affected if Device is not an Archer AX53 model
  2. Check firmware version
    Navigate to the router's web interface (typically at 192.168.0.1), go to Administration > Firmware Upgrade or System > Router Status, and record the firmware version number
    Affected if Firmware version is 1.0 or falls within the affected version range for this model
  3. Verify tdpserver module status
    Access router via SSH (if enabled) or telnet and run 'ps | grep tdpserver' or check /proc/processes for the tdpserver process to determine if the module is running
    Affected if tdpserver process is running and exposed to network
  4. Check network exposure
    Review router firewall settings and network configuration to determine if the device is accessible from untrusted adjacent networks. Check if WAN/LAN interfaces permit unsolicited incoming traffic to the tdpserver port (typically port 2000 for TP-Link Discovery Protocol)
    Affected if Device is reachable from untrusted adjacent networks without proper access controls

You are affected if you own a TP-Link Archer AX53 running firmware version 1.0 with the tdpserver module enabled and the device is accessible from adjacent networks.

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

Apply vendor-supplied firmware update from TP-Link for Archer AX53 v1.0 when available. Until patch is released, restrict network access to the device to trusted adjacent networks only.

Recommended fix Moderate confidence

Firmware newer than 1.3.1 Build 20241120 (contact TP-Link support for exact fixed version)

  1. 1. Visit the official TP-Link support website at https://www.tp-link.com/support/
  2. 2. Search for "Archer AX53" firmware downloads
  3. 3. Download the latest available firmware version (must be newer than 1.3.1 Build 20241120)
  4. 4. Access the router web management interface (typically http://tplinkwifi.net or http://192.168.0.1)
  5. 5. Navigate to System > Firmware Upgrade or Advanced > System > Firmware Upgrade
  6. 6. Click "Browse" or "Choose File" and select the downloaded firmware file
  7. 7. Click "Upgrade" and wait for the process to complete - do not power off the router
  8. 8. After reboot, verify the new firmware version in the router interface
Caveat Standard firmware upgrade risk - ensure stable power during upgrade to avoid brick

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

Fix this in Archer Ax53 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,730
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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