Quick answers
- Is CVE-2026-30817 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-30817 being exploited in the wild.
- How severe is CVE-2026-30817?
- Medium severity, with a CVSS score of 5.7, published 8 April 2026.
- Which products and versions are affected?
- TP-Link Archer Ax53 before 1.7.1 Build 20260213.
- Is there a fix for CVE-2026-30817?
- A patch was published on 2026-02-13: Firmware build date for the fix Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-30817 attacked?
- It is attacked from the adjacent network, in a network appliance.
- Am I affected by CVE-2026-30817?
- Check whether you run TP-Link Archer Ax53 or TP-Link Archer Ax53 Firmware at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An external configuration control vulnerability (CWE-15/CWE-610) exists in the OpenVPN module of the TP-Link Archer AX53 v1.0 router. The flaw is triggered when the device processes a specially crafted malicious configuration file during a configuration restore or setup process. An authenticated attacker located on the adjacent network (local LAN) can exploit this to perform arbitrary file reads from the underlying filesystem. This could result in the disclosure of sensitive system files or credentials. The issue is resolved in firmware version 1.7.1 Build 20260213 and later.
Affected products
- TP-Link Archer AX53 v1.0 before 1.7.1 Build 20260213
Timeline
- 2026-04-08: advisory: Initial disclosure by TP-Link and NVD
- 2026-02-13: patched: Firmware build date for the fix