CVE-2026-30814
Received Received - Intake
Stack-Based Buffer Overflow in TP-Link Archer AX53 tmpServer Module

Publication date: 2026-04-08

Last updated on: 2026-04-14

Assigner: TPLink

Description
A stack-based buffer overflow in the tmpServer module of TP-Link Archer AX53 v1.0Β allows an authenticated adjacent attacker to trigger a segmentation fault and potentially execute arbitrary code via a specially crafted configuration file. Successful exploitation may cause a crash and could allow arbitrary code execution, enabling modification of device state, exposure of sensitive data, or further compromise of device integrity. This issue affects AX53 v1.0: before 1.7.1 Build 20260213.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-04-08
Last Modified
2026-04-14
Generated
2026-05-07
AI Q&A
2026-04-08
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
tp-link archer_ax53_firmware to 1.7.1 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-787 The product writes data past the end, or before the beginning, of the intended buffer.
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).
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability is a stack-based buffer overflow found in the tmpServer module of the TP-Link Archer AX53 version 1.0. It allows an authenticated attacker who is adjacent (on the same network segment) to cause a segmentation fault by using a specially crafted configuration file. This fault can potentially lead to arbitrary code execution on the device.


How can this vulnerability impact me? :

Exploitation of this vulnerability can cause the device to crash and may allow an attacker to execute arbitrary code. This could enable the attacker to modify the device's state, expose sensitive data, or further compromise the integrity of the device.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The vulnerability allows an authenticated adjacent attacker to potentially execute arbitrary code, which could lead to modification of device state, exposure of sensitive data, or further compromise of device integrity.

Such exposure or compromise of sensitive data may negatively impact compliance with data protection standards and regulations like GDPR or HIPAA, which require safeguarding sensitive information and maintaining device integrity.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart