Service crash or code execution via probe overflow
Published Mar 20, 2026 · Updated Mar 20, 2026
Stack-based buffer overflow in tdpServer on TP-Link Archer AX53 v1 before 251029 allows remote attackers on an adjacent network to crash the service. The probe-handling logic copies unvalidated parameters into a fixed-size stack buffer without sufficient bounds enforcement. No authentication or user interaction is required, but code execution requires complex heap spraying; successful attacks repeatedly interrupt the service or take control of the device.
Summary
What happened
Stack-based buffer overflow in tdpServer on TP-Link Archer AX53 v1 before 251029 allows remote attackers on an adjacent network to crash the service. The probe-handling logic copies unvalidated parameters into a fixed-size stack buffer without sufficient bounds enforcement. No authentication or user interaction is required, but code execution requires complex heap spraying; successful attacks repeatedly interrupt the service or take control of the device.
The record
- CVE
- CVE-2025-15608
- Published
- Mar 20, 2026
- Updated
- Mar 20, 2026
- Vendor
- TP-Link Systems Inc.
- Product
- Archer AX53
- Classifications
- CWE-121, CAPEC-100, T1210
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 20, 2026CVE publishedPublication date reported by the CVE source.
- Mar 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <251029
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo