Which versions of Ax53 V1 0 are affected by CVE-2026-30814?

TP-Link Archer AX53 wireless routers running firmware before version 1.7.1 Build 20260213 contain a stack-based buffer overflow in the tmpServer module that allows authenticated adjacent network…. A patch is available.

How to fix or mitigate CVE-2026-30814?

Within 24 hours: Inventory all TP-Link Archer AX53 devices and document current firmware versions via device web interface or management platform. Within 7 days: Test firmware version 1.7.1 Build 20260213 or later in non-production environment; validate functionality against organizational network requirements. Within 30 days: Deploy patched firmware to all affected devices following TP-Link's documented update procedure; verify successful deployment and confirm absence of regressions.

Ax53 V1 0 CVE-2026-30814

Q: What is the CVSS score of CVE-2026-30814?

CVE-2026-30814 has a CVSS 4.0 base score of 7.3 (High). CVSS vector: CVSS:4.0/AV:A/AC:H/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.0%.

EUVD-2026-20542 HIGH

Stack-based Buffer Overflow (CWE-121)

2026-04-08 TPLink

GHSA-w4qp-mpq3-cw45

Information Disclosure Stack Overflow RCE Buffer Overflow TP-Link Ax53 V1 0

7.3

CVSS 4.0 · Vendor: TPLink

Severity by source

Vendor (TPLink) PRIMARY

7.3 HIGH

CVSS:4.0/AV:A/AC:H/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Primary rating from Vendor (TPLink) · only source for this CVE.

CVSS VectorVendor: TPLink

Attack Vector

Adjacent

Attack Complexity

High

Privileges Required

High

User Interaction

None

Scope

Lifecycle Timeline

EUVD ID Assigned

Apr 08, 2026 - 19:31 euvd

EUVD-2026-20542

Analysis Generated

Apr 08, 2026 - 19:31 vuln.today

Patch released

Apr 08, 2026 - 19:31 nvd

Patch available

CVE Published

Apr 08, 2026 - 17:52 nvd

HIGH 7.3

DescriptionCVE.org

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.

AnalysisAI

Stack-based buffer overflow in TP-Link Archer AX53 v1.0 tmpServer module enables authenticated adjacent attackers to execute arbitrary code via malicious configuration file. Exploitation triggers segmentation fault, permits device state modification, sensitive data exposure, and integrity compromise. Affects firmware versions before 1.7.1 Build 20260213. Requires high privileges and adjacent network access. No public exploit identified at time of analysis.

Technical ContextAI

CWE-121 stack buffer overflow in tmpServer configuration parsing logic. Authenticated adjacent attacker (CVSS AV:A/PR:H) crafts malformed configuration file exceeding stack buffer boundaries. Overflow corrupts stack frame, enabling instruction pointer control for arbitrary code execution within device firmware context. High attack complexity (AC:H) suggests exploitation requires precise memory layout knowledge or timing conditions.

RemediationAI

Vendor-released patch: firmware version 1.7.1 Build 20260213 or later. Immediately upgrade via official TP-Link firmware downloads at https://www.tp-link.com/en/support/download/archer-ax53/v1/#Firmware or https://www.tp-link.com/my/support/download/archer-ax53/v1/#Firmware. Verify firmware integrity using vendor-provided checksums before installation. Interim mitigations: restrict administrative access to trusted adjacent networks only, enforce strong authentication credentials, disable remote management interfaces. Monitor device logs for unexpected crashes or configuration anomalies. Consult TP-Link security advisory at https://www.tp-link.com/us/support/faq/5055/ for additional vendor guidance. No workaround eliminates vulnerability; patching is mandatory for production environments.