# CVE-2026-0630: Command Injection Vulnerability on TP-Link Archer BE230 v1.2 and AXE75 v1.0

> An authenticated adjacent attacker can execute arbitrary code on TP-Link Archer routers, gaining full administrative control and compromising network security.

- **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:** 2 Feb 2026
- **Updated:** 19 Mar 2026
- **Also known as:** GHSA-cc62-3p5g-fr7j

## What is CVE-2026-0630?

CVE-2026-0630 is a high-severity command injection vulnerability in TP Link Systems Inc. AXE75 v1.0, published on 2 Feb 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 in TP-Link Archer BE230 v1.2(web modules) and Archer AXE75 v1.0 allows adjacent 

authenticated 

attacker to execute arbitrary code. Successful exploitation could allow an attacker to gain full administrative control of the device, resulting in severe compromise of configuration integrity, network security, and service availability.

This CVE covers one of multiple distinct OS command injection issues identified across separate code paths. Although similar in nature, each instance is tracked under a unique CVE ID.This issue affects Archer BE230 v1.2 < 1.2.4 Build 20251218 rel.70420 and Archer AXE v1.0 <
1.5.3 Build 20260209 rel. 71108.

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

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

It affects 1 product.


Products: Tp-Link Archer Be230 Firmware.

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

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

## Is CVE-2026-0630 being exploited?

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

## Other vulnerabilities in TP Link Systems Inc. AXE75 v1.0

- [CVE-2026-22229](https://insights.sbomify.com/CVE-2026-22229/): Command Injection Vulnerability on TP-Link Archer BE230 v1.2 and Deco BE25 v1.0 (high 8.6)
- [CVE-2026-0631](https://insights.sbomify.com/CVE-2026-0631/): Authenticated Command Injection Vulnerability in Surfshark VPN Login in multiple Archer products (high 8.5)
- [CVE-2026-22221](https://insights.sbomify.com/CVE-2026-22221/): Command Injection Vulnerability on TP-Link Archer BE230 v1.2 and BE3600 v1 (high 8.5)
- [CVE-2026-22222](https://insights.sbomify.com/CVE-2026-22222/): Command Injection Vulnerability on TP-Link Archer BE230 v1.2 and AXE75 v2 (high 8.5)
- [CVE-2026-22223](https://insights.sbomify.com/CVE-2026-22223/): Command Injection Vulnerability on TP-Link Archer BE230 v1.2 and BE3600 v1 (high 8.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-0630 is a high-severity command injection vulnerability in TP Link Systems Inc. AXE75 v1.0, published on 2 Feb 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-0630 in the wild and no public exploit code.

Affected product: TP Link Systems Inc. AXE75 v1.0. 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-0630/ (Markdown: https://insights.sbomify.com/CVE-2026-0630/index.md)
```

## Sources

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

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