dbcve.org
Archer Ax53 FirmwareOperating system · Tp Link

CVE-2026-30814

HIGH · 8.0 CVSS v3.1 Published 2026-04-08
Fix available
A fix is available. Upgrade to 1.7.1 or later.
See remediation →
82/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Stack-based buffer overflow in the tmpServer module of TP-Link Archer AX53 v1.0 allows an authenticated adjacent attacker to execute arbitrary code by uploading a specially crafted configuration file. The vulnerability stems from insufficient bounds checking when parsing configuration data, leading to stack memory corruption and potential code execution.

MitigationApply vendor firmware update 1.7.1 Build 20260213 or later. Until then, restrict adjacent network access and disable tmpServer functionality if possible.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Archer Ax53 FirmwareOperating system
Affected:< 1.7.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the router model
    Check the device label or web interface for the exact model number (Archer AX53) and hardware version (v1.0)
    Affected if Device is not TP-Link Archer AX53 v1.0
  2. Check the installed firmware version
    Log into the router web interface (typically at 192.168.0.1) and navigate to Status or System settings to view the firmware version, or use the TP-Link Tether app
    Affected if Firmware version is below 1.7.1 (any build prior to 20260213)
  3. Verify tmpServer module accessibility
    Attempt to access the tmpServer endpoint on the router (usually via HTTP/HTTPS on the local network) to determine if the service is exposed
    Affected if tmpServer is accessible from the local network without additional network segmentation
  4. Check for adjacent network access
    Confirm whether untrusted devices can connect to the same local network as the router
    Affected if The router is on a network where unauthorized adjacent attackers could reach it

You are affected if you have a TP-Link Archer AX53 v1.0 router running firmware version below 1.7.1 and the tmpServer module is accessible to authenticated adjacent attackers on your local network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.7.1 or later
Fixed in 1.7.1
Interim mitigation

Apply vendor firmware update 1.7.1 Build 20260213 or later. Until then, restrict adjacent network access and disable tmpServer functionality if possible.

Recommended fix High confidence

Firmware 1.7.1 Build 20260213

  1. Navigate to the official TP-Link support page at www.tp-link.com and locate the Archer AX53 v1.0 firmware download section
  2. Download firmware version 1.7.1 Build 20260213 (or the latest version at or after 1.7.1)
  3. Access the TP-Link Archer AX53 web management interface by entering the router's IP address in a browser
  4. Log in with administrator credentials
  5. Navigate to the 'System' or 'Firmware Upgrade' section in the web interface
  6. Select the option to upgrade firmware manually or via file upload
  7. Browse to the downloaded firmware file (1.7.1 Build 20260213) and initiate the upgrade
  8. Wait for the upgrade process to complete and the router to reboot automatically

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Archer Ax53 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-30814 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-30814 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data