Skip to content
statance
MenuClose
Log inStart for free ↗
high · CVSS 8.5

CVE-2026-8913

Command Injection in Archer MR600 WireGuard Client Configuration

Published 8 Jun 2026 · Source updated 5 Nov 2026 · Retrieved 2026-11-06 12:59 UTC

Monitor this CVE ↗Full CVE monitoring on Pro and Business

What happened?

A command Injection vulnerability exists in the WireGuard client configuration of Archer MR600 v2, v3, and v5 due to improper neutralization of user-controlled input within the web management interface. An authenticated attacker with administrative privileges may be able to execute arbitrary commands when applying configuration changes.Successful exploitation may result in a full compromise of confidentiality, integrity, and availability of the affected device.

Description supplied by CVE Program. Formatting is simplified; follow the original advisory for full details.

Affected software and versions

Source-provided software and version information
SoftwareVersion informationFixed version
Archer MR600 v5TP-Link Systems Inc.affected: 0 to < EU_V5_1.7.0 0.9.1 260518 rel67803; affected: 0 to < JP_V5_1.2.0 0.9.1 260519 rel52362See vendor advisory
Archer MR600 v2TP-Link Systems Inc.affected: 0 to < 1.12.0 Build 260826See vendor advisory
Archer MR600 v3TP-Link Systems Inc.affected: 0 to < 1.4.0 Build 260827See vendor advisory

Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.

Is it being exploited?

This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.

CISA data retrieved 2026-11-06 16:38 UTC. Check CISA ↗

How to respond

  1. Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
  2. Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
  3. Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.

Sources and remediation references

This public advisory does not determine whether a particular server is affected. Records are refreshed as sources change; verify urgent decisions against the original advisory.

← Browse the public CVE feed