CyberSecBulletin
CVE-2025-15608NVD status: Modified

AX53 v1: Stack-based Buffer Overflow

Published Updated By the CyberSecBulletin desk

CVE-2025-15608 is a critical-severity stack-based buffer overflow vulnerability in AX53 v1 from TP-Link, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 251029 as the first without the flaw, so updating AX53 v1 to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.64% chance of exploitation within 30 days, higher than 51% of scored CVEs.

Patch this week

Critical severity: a successful attack would have severe impact.

What to do

  1. Update AX53 v1 to 251029 or a later version.
  2. Update AX55 v4 to (US)_1.2.1 Build 20260527 or a later version.
  3. Update AX55 v4.6 to (US)_1.2.1 Build 20260527 or a later version.
  4. Read the advisory on tp-link.com for workarounds and exact fixed builds.
  5. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
TP-LinkAX53 v1before 251029251029
TP-LinkAX55 v4before (US)_1.2.1 Build 20260527(US)_1.2.1 Build 20260527
TP-LinkAX55 v4.6before (US)_1.2.1 Build 20260527(US)_1.2.1 Build 20260527
TP-LinkArcher Ax53 Firmware1.0Not stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 4.07.7HighCNA
CVSS 3.19.8CriticalNVD

Official description

This vulnerability in AX53 v1, AX55 v4 and AX55 v4.6 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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Stack-based Buffer Overflow

The product writes past the end of a buffer that was allocated on the stack.

How developers prevent this class of flaw

  • Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.
  • Use an abstraction library to abstract away risky APIs. Not a complete solution.
  • Implement and perform bounds checking on input.

More Stack-based Buffer Overflow vulnerabilities (CWE-121)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in AX53 v1

All AX53 v1 vulnerabilities

Recent Stack-based Buffer Overflow vulnerabilities

Spotted an error? Tell us.