Loading vulnerability…
OS Command Injection in TP-Link Archer AX53 v1.0 OpenVPN Module
CVE-2026-30815 is an OS command injection vulnerability in the OpenVPN module of TP-Link Archer AX53 v1.0 routers. The flaw is caused by insufficient input validation when the device processes a specially crafted OpenVPN configuration file. An authenticated attacker on an adjacent network can exploit this condition to inject and execute arbitrary system commands on the device. The issue affects TP-Link Archer AX53 v1.0 firmware versions prior to 1.7.1 Build 20260213.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation allows execution of system commands in the router context. This can enable an attacker to modify configuration files, disclose sensitive information present on or accessible to the device, and further compromise device integrity. Given the stated high confidentiality, integrity, and availability impacts in the referenced CVSS data, exploitation may also result in broader operational disruption of the affected router.
If you can’t patch tonight, do this now.
If immediate patching is not possible, restrict access to the OpenVPN configuration/import functionality to trusted administrators only, minimize adjacent-network exposure, and limit administrative access paths to trusted management networks. Monitor for unexpected configuration changes and signs of command execution via the OpenVPN module. Because exploitation requires authenticated access and processing of a crafted configuration file, reducing who can authenticate and import or apply VPN configurations will reduce exposure until the firmware update is installed.
Patch, then assume compromise.
Upgrade TP-Link Archer AX53 v1.0 to firmware version 1.7.1 Build 20260213 or later, as versions before this build are affected. Apply the vendor-provided firmware update referenced in TP-Link support materials.
No public exploits tracked yet. Mallory keeps watching.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.