TP-Link Archer AX53 v1.0 up to 1.3.1 tmpserver Modules heap-based overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.2 | $0-$5k | 0.00 |
Summary
A vulnerability described as critical has been identified in TP-Link Archer AX53 v1.0 up to 1.3.1. Affected is an unknown function of the component tmpserver Modules. Such manipulation leads to heap-based overflow. This vulnerability is referenced as CVE-2025-58077. The attack needs to be initiated within the local network. No exploit is available.
Details
A vulnerability, which was classified as critical, has been found in TP-Link Archer AX53 v1.0 up to 1.3.1. Affected by this issue is an unknown code block of the component tmpserver Modules. The manipulation with an unknown input leads to a heap-based overflow vulnerability. Using CWE to declare the problem leads to 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(). Impacted is confidentiality, integrity, and availability. CVE summarizes:
Heap-based Buffer Overflow vulnerability in TP-Link Archer AX53 v1.0 (tmpserver modules) allows authenticated adjacent attackers to cause a segmentation fault or potentially execute arbitrary code via a specially crafted set of network packets containing an excessive number of host entries This issue affects Archer AX53 v1.0: through 1.3.1 Build 20241120.
The weakness was published by Lilith >_>. The advisory is available at talosintelligence.com. This vulnerability is handled as CVE-2025-58077 since 11/06/2025. The exploitation is known to be difficult. Access to the local network is required for this attack. The exploitation requires an enhanced level of successful authentication. The technical details are unknown and an exploit is not available. The structure of the vulnerability defines a possible price range of 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.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
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: 7.2VulDB Meta Temp Score: 7.2
VulDB Base Score: 6.4
VulDB Temp Score: 6.4
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
11/06/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-58077 (🔒)
GCVE (CVE): GCVE-0-2025-58077
GCVE (VulDB): GCVE-100-344090
Entry
Created: 02/03/2026 21:12Updated: 03/16/2026 19:44
Changes: 02/03/2026 21:12 (66), 02/12/2026 05:00 (11), 03/16/2026 19:44 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.