CVE-2026-120227: WAVLINK WN701AE OS command injection in static route setting

CVE-2026-120227 · Severity: critical · CVSS 9.9 · Published 2026-11-01

WAVLINK WN701AE is a wireless router used in home and office networks. An authenticated attacker can inject arbitrary system commands through the static route deletion function, gaining full control of the device with root-level privileges. This could allow an attacker to intercept traffic, install persistent backdoors, or use the router for botnet participation and lateral network attacks.

Vendors: Wavlink.

Quick answers

Is CVE-2026-120227 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-120227 being exploited in the wild.
How severe is CVE-2026-120227?
Critical severity, with a CVSS score of 9.9, published 1 November 2026.
Which products and versions are affected?
Wavlink WN701AE M01AE_V260105 and possibly others.
Is there a fix for CVE-2026-120227?
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-120227 attacked?
It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-120227?
Check whether you run Wavlink WN701AE 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

The vulnerability is an OS command injection in the del_staticrule function of the ioos web backend, where the rule_name parameter is concatenated unsanitized into a system() call without filtering shell metacharacters. The attack requires prior authentication and network access to the router's web interface. Exploitation grants arbitrary command execution with root privileges, leading to full device compromise.

Affected products

  • WAVLINK WN701AE M01AE_V260105 and possibly others

Timeline

  • 2026-11-01: disclosed: Advisory published; exploit now public
  • 2026-11-01: other: Vendor contacted early about disclosure

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.