dbcve.org
Archer Ax53 FirmwareOperating system · Tp Link

CVE-2026-30817

MEDIUM · 5.7 CVSS v3.1 Published 2026-04-08
Fix available
A fix is available. Upgrade to 1.7.1 or later.
See remediation →
59/100
Remediation priority · Elevated
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
An external configuration control vulnerability in the OpenVPN module of TP-Link AX53 v1.0 allows an authenticated adjacent attacker to read arbitrary files when a malicious configuration file is processed. Successful exploitation may allow unauthorized access to arbitrary files on the device, potentially exposing sensitive information.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

This is an external configuration control vulnerability in the OpenVPN module of TP-Link AX53 v1.0 that allows an authenticated adjacent attacker to read arbitrary files on the device by providing a malicious configuration file. The vulnerability suggests improper validation of file paths in the configuration processing, likely a path traversal issue.

MitigationUpgrade TP-Link AX53 v1.0 to firmware version 1.7.1 Build 20260213 or later. As an interim measure, restrict network access to the OpenVPN management interface to prevent adjacent attackers from exploiting this vulnerability.

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
None
Availability
None

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

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. Check the router's firmware version
    Access the TP-Link AX53 web management interface (typically at 192.168.0.1) and navigate to Status or System > Firmware Upgrade page to view the current firmware version. Alternatively, use the command line via SSH/Telnet and run 'fw_printenv' or check /etc/version file.
    Affected if The displayed firmware version is lower than 1.7.1 (e.g., 1.6.0, 1.5.0, etc.)
  2. Verify OpenVPN module is configured
    Log into the router's web interface and navigate to Advanced > VPN > OpenVPN. Check if any OpenVPN configuration profiles are created or the OpenVPN server/client feature is enabled.
    Affected if OpenVPN is enabled or any .ovpn configuration file is uploaded to the device
  3. Confirm file read access vulnerability context
    Since this is a file read vulnerability in the configuration file processing logic of the OpenVPN module, the vulnerability is present when both conditions are met: (1) firmware version is below 1.7.1, and (2) OpenVPN functionality is accessible to authenticated users.
    Affected if Firmware version is below 1.7.1 AND the device has OpenVPN module accessible to authenticated adjacent attackers

A user is affected if their TP-Link AX53 firmware version is below 1.7.1 and they have enabled or have access to the OpenVPN module, as an authenticated adjacent attacker could supply a malicious configuration file to read arbitrary files on the device.

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

Upgrade TP-Link AX53 v1.0 to firmware version 1.7.1 Build 20260213 or later. As an interim measure, restrict network access to the OpenVPN management interface to prevent adjacent attackers from exploiting this vulnerability.

Recommended fix High confidence

Archer AX53 v1.0 firmware 1.7.1 Build 20260213 or later

  1. 1. Download the Archer AX53 firmware version 1.7.1 Build 20260213 or later from the official TP-Link support website (https://www.tp-link.com)
  2. 2. Navigate to the router's web management interface
  3. 3. Go to System > Firmware Upgrade or similar path depending on UI layout
  4. 4. Click on the firmware upgrade option
  5. 5. Select the downloaded firmware file (.bin)
  6. 6. Click Upgrade and wait for the process to complete - do not power off the device
  7. 7. After reboot, verify the firmware version in the router's status page to confirm the upgrade was successful
  8. 8. Reconfigure any custom OpenVPN settings if needed after the upgrade

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

Fix this in Archer Ax53 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-30817 — 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-30817 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