Quick answers
- Is CVE-2026-22223 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-22223 being exploited in the wild.
- How severe is CVE-2026-22223?
- High severity, with a CVSS score of 8, published 2 February 2026.
- Which products and versions are affected?
- TP-Link Archer BE3600 v1; TP-Link Archer Be230 v1.2 < 1.2.4 Build 20251218 rel.70420.
- Is there a fix for CVE-2026-22223?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-22223 attacked?
- It is attacked from the adjacent network or over the network.
- Am I affected by CVE-2026-22223?
- Check whether you run TP-Link Archer BE3600, TP-Link Archer Be230 or TP-Link Archer Be230 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 OS command injection vulnerability exists in the VPN module of affected TP-Link router firmware versions. The vulnerability is triggered through improper input validation in code that processes VPN configuration parameters. An authenticated attacker with network access to the router's management interface (adjacent network access) can inject arbitrary shell commands that are executed with root/administrative privileges. Exploitation results in remote code execution and complete device compromise. Patches are available: Archer BE230 v1.2 should be updated to 1.2.4 Build 20251218 rel.70420 or later; the advisory indicates similar vulnerabilities in other models are tracked separately under distinct CVE identifiers.
Affected products
- TP-Link Archer BE230 v1.2 < 1.2.4 Build 20251218 rel.70420
- TP-Link Archer BE3600 v1
Timeline
- 2026-02-02: disclosed
- 2026-02-02: advisory