CVE-2026-22226 — Command Injection Vulnerability on TP-Link Archer BE230 and AX73
A command injection vulnerability may be exploited after the admin's authentication in the VPN server configuration module on TP-Link Archer BE230 v1.2 and Archer AX73 v2. 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 AX73 v2 < 1.3.1 Build 20260430.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 2.5% (30-day exploitation probability)+13
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — www.tp-link.com (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (TP-Link Systems Inc. Archer AX73 v2, TP-Link Systems Inc. Archer Be230 Firmware, TP-Link Systems Inc. Archer BE230 v1.2).
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| TP-Link Systems Inc. | Archer AX73 v2 | < 1.3.1 Build 20260430 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| TP-Link Systems Inc. | Archer Be230 Firmware | < 1.2.4 | Vulnerable | NIST National Vulnerability Database |
| TP-Link Systems Inc. | Archer BE230 v1.2 | < 1.2.4 Build 20251218 rel.70420 | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 8.5 | CVSS 4.0 | High | — | — | f23511db-6c3e-4e32-a477-6aa17d310630 via NIST National Vulnerability Database |
| 8.5 | CVSS 4.0 | High | — | — | TPLink via CVE Program (cve.org) e CISA ADP |
| 7.2 | CVSS 3.1 | High | 1.2 | 5.9 | nvd@nist.gov via NIST National Vulnerability Database |
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 2.50%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Look for parameters with command/query metacharacters and unexpected child processes of the service.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · tp-link systems inc./archer be230 v1.2, tp link systems inc./archer ax73 v2
- SSVC assessment updated
- Record published
- Fix documented
- CVSS changed · 7.2
- Source status changed · → Modified
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
6 on the record
- www.tp-link.com/us/support/download/archer-ax73/v2/
- www.tp-link.com/en/support/download/archer-ax73/v2/
- www.tp-link.com/sg/support/download/archer-be230/v1.20/
- www.tp-link.com/us/support/download/archer-be230/v1.20/
- www.tp-link.com/us/support/faq/4935/
- www.tp-link.com/en/support/download/archer-be230/v1.20/
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-22220 Improper Input Validation Leading to DoS on TP-Link Archer BE230 Feb 3, 2026
- Medium CVE-2026-22228 Improper Input Validation Leading to DoS on TP-Link Archer BE230 Feb 3, 2026
- High CVE-2026-22223 Command Injection Vulnerability on TP-Link Archer BE230 v1.2 and BE3600 v1 Feb 2, 2026
- High CVE-2026-22224 Command Injection Vulnerability on TP-Link Archer BE230 v1.2 Feb 2, 2026
- High CVE-2026-22225 Command Injection Vulnerability on TP-Link Archer BE230 v1.2 and AXE75 v1.0 Feb 2, 2026
- High CVE-2026-22227 Command Injection Vulnerability on TP-Link Archer BE230 v1.2 Feb 2, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-22226 is "Command Injection Vulnerability on TP-Link Archer BE230 and AX73", rated High. It affects Archer AX73 v2 (TP-Link Systems Inc.); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.2 describes technical severity. EPSS 2.50% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.