Quick answers
- Is CVE-2026-120276 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-120276 being exploited in the wild.
- How severe is CVE-2026-120276?
- Critical severity, with a CVSS score of 10, published 2 November 2026.
- Which products and versions are affected?
- Wavlink WN536AX6-A V260507_2.0.0.
- Is there a fix for CVE-2026-120276?
- 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-120276 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-120276?
- Check whether you run Wavlink WN536AX6-A 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 /bin/ioos web backend (running as root) improperly sanitizes the group_name parameter in the openvpn_cli_group handler, passing it unsanitized into a system() call within single quotes. An attacker can break out of the quoted context with a payload like a';CMD;' to inject arbitrary shell commands. The ioos daemon trusts requests from 127.0.0.1 without token validation, and factory-default devices accept empty passwords, enabling unauthenticated remote exploitation.
Affected products
- WAVLINK WN536AX6-A V260507_2.0.0
Timeline
- 2026-11-02: disclosed
- exploited: Proof of concept publicly available on GitHub