# CVE-2026-9151: Command Injection Vulnerability in OpenVPN on Multiple TP-Link Archer Routers

> An authenticated adjacent attacker can execute arbitrary commands on TP-Link Archer routers by importing a malicious VPN configuration file.

- **Severity:** High 8.5 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jun 2026
- **Updated:** 11 Jun 2026
- **Also known as:** GHSA-x4j3-73c9-wq9c

## What is CVE-2026-9151?

CVE-2026-9151 is a high-severity command injection vulnerability in TP Link Systems Inc. Archer AX12 V1, published on 10 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An OS
command injection vulnerability exists in the VPN module of TP-Link Archer AX12
v1, AX17 v1. AX18 v1, and AX1300 v1.6 routers. This vulnerability allows an
adjacent, authenticated attacker to execute arbitrary commands on the device by
importing a specially crafted VPN client configuration file. The issue stems
from improper filtering of special characters. 

Successful
exploitation of this vulnerability may enable an attacker to gain full control
of the affected device, potentially compromising configuration integrity,
network security, and service availability.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-9151?


## How do I fix CVE-2026-9151?

No fix has been published for CVE-2026-9151 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-9151 being exploited?

There is no known exploitation of CVE-2026-9151 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-9151 and fix it if it is affected.

What it is: CVE-2026-9151 is a high-severity command injection vulnerability in TP Link Systems Inc. Archer AX12 V1, published on 10 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-9151 in the wild and no public exploit code.

Affected product: TP Link Systems Inc. Archer AX12 V1. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-9151/ (Markdown: https://insights.sbomify.com/CVE-2026-9151/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-9151
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-9151
- OSV: https://osv.dev/vulnerability/CVE-2026-9151

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-9151/
Summaries are generated and may contain mistakes; the official description above is the record.
