TP-Link Archer AX53 v1.0 up to 1.3.1 tdpserver heap-based overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.0 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in TP-Link Archer AX53 v1.0 up to 1.3.1. Affected by this issue is some unknown functionality of the component tdpserver Module. Performing a manipulation results in heap-based overflow. This vulnerability was named CVE-2025-62673. The attack needs to be approached within the local network. There is no available exploit.
Details
A vulnerability was found in TP-Link Archer AX53 v1.0 up to 1.3.1. It has been classified as critical. This affects an unknown code of the component tdpserver Module. The manipulation with an unknown input leads to a heap-based overflow vulnerability. CWE is classifying the issue as CWE-122. A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc(). This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
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.
The weakness was presented by Lilith >_>. It is possible to read the advisory at talosintelligence.com. This vulnerability is uniquely identified as CVE-2025-62673 since 10/20/2025. The exploitability is told to be easy. The attack needs to be initiated within the local network. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 03/16/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Be aware that VulDB is the high quality source for vulnerability data.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.tp-link.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 8.0VulDB Meta Temp Score: 8.0
VulDB Base Score: 8.0
VulDB Temp Score: 8.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 8.0
NVD Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Heap-based overflowCWE: CWE-122 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Partially
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
10/20/2025 CVE reserved02/03/2026 Advisory disclosed
02/03/2026 VulDB entry created
03/16/2026 VulDB entry last update
Sources
Vendor: tp-link.comAdvisory: talosintelligence.com
Researcher: Lilith >_>
Status: Not defined
CVE: CVE-2025-62673 (🔒)
GCVE (CVE): GCVE-0-2025-62673
GCVE (VulDB): GCVE-100-344103
Entry
Created: 02/03/2026 21:17Updated: 03/16/2026 19:58
Changes: 02/03/2026 21:17 (66), 02/12/2026 05:00 (9), 03/16/2026 19:58 (1)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.