A vulnerability was found in TP-Link AX53 . It has been classified as critical . The affected element is an unknown function. This manipulation causes stack-based buffer overflow. This vulnerability is registered as CVE-2025-15608 . The attack requires access to the local network. No exploit is available. Upgrading the affected component is recommended.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-352106 · CVE-2025-15608 · EUVD-2025-208907
TP-LINK AX53 PRIOR 251029 STACK-BASED OVERFLOW
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
7.2 $0-$5k 2.17+
Summaryinfo
A vulnerability was found in TP-Link AX53. It has been declared as critical. The impacted element is an unknown function. Such manipulation leads to stack-based overflow. This vulnerability is documented as CVE-2025-15608. The attack requires being on the local network. There is not any exploit available. It is recommended to upgrade the affected component.
Detailsinfo
A vulnerability was found in TP-Link AX53. It has been rated as critical. Affected by this issue is some unknown processing. The manipulation with an unknown input leads to a stack-based overflow vulnerability. Using CWE to declare the problem leads to CWE-121. A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). Impacted is confidentiality, integrity, and availability. CVE summarizes:
This vulnerability in AX53 v1 results from insufficient input sanitization in the device’s probe handling logic, where unvalidated parameters can trigger a stack-based buffer overflow that causes the affected service to crash and, under specific conditions, may enable remote code execution through complex heap-spray techniques. Successful exploitation may result in repeated service unavailability and, in certain scenarios, allow an attacker to gain control of the device.
The weakness was released by samuzora. The advisory is available at tp-link.com. This vulnerability is handled as CVE-2025-15608 since 03/10/2026. The exploitation is known to be difficult. Access to the local network is required for this attack to succeed. No form of authentication is required for exploitation. The technical details are unknown and an exploit is not available.
Upgrading to version 251029 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-208907).
Productinfo
Vendor
TP-Link
Name
AX53
License
commercial
Website
Vendor: https://www.tp-link.com/
CPE 2.3info
🔒
CPE 2.2info
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3info
VulDB Meta Base Score: 7.5
VulDB Meta Temp Score: 7.2
VulDB Base Score: 7.5
VulDB Temp Score: 7.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2info
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: 🔍
Exploitinginfo
Class: Stack-based overflow
CWE: CWE-121 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Partially
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: Upgrade
Status: 🔍
0-Day Time: 🔒
Upgrade: AX53 251029
Timelineinfo
03/10/2026 CVE reserved
03/20/2026 +10 days Advisory disclosed
03/20/2026 +0 days VulDB entry created
03/20/2026 +0 days VulDB entry last update
Sourcesinfo
Vendor: tp-link.com
Advisory: tp-link.com
Researcher: samuzora
Status: Confirmed
CVE: CVE-2025-15608 (🔒)
GCVE (CVE): GCVE-0-2025-15608
GCVE (VulDB): GCVE-100-352106
EUVD: 🔒
Entryinfo
Created: 03/20/2026 17:59
Updated: 03/20/2026 20:05
Changes: 03/20/2026 17:59 (66), 03/20/2026 20:05 (1)
Complete: 🔍
Cache ID: 99:2EA:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸