WAVLINK WN536AX6-A WireGuard CLI Group ioos sub_41a1d8 os command injection
Affects WAVLINK WN536AX6-A devices running firmware M36AX6_V260507_2.0.0, through the WireGuard client group handler of the ioos back-end.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 37/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Default setups
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The WAVLINK WN536AX6-A wireless router's WireGuard CLI group handler is affected. A remote attacker can supply a crafted group name to inject operating system commands, potentially allowing them to run arbitrary commands on the device.
Read the original description
A security vulnerability has been detected in WAVLINK WN536AX6-A V260507_2.0.0. This issue affects the function sub_41a1d8 of the file /bin/ioos of the component WireGuard CLI Group Handler. Such manipulation of the argument group_name leads to os command injection. It is possible to launch the attack remotely. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure.
What to do
Check every install: default setups are affected.
Workaround: The checked sources give no workaround. Until a fix is released, limit who can reach the device's admin interface and port 81, and do not expose the device's management interface to untrusted networks.
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- WAVLINK WN536AX6-A
V260507_2.0.0
Evidence 5
- Advisory
- Advisory
- Advisory
- Advisory
- Exploit
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-120277
What does this mean?
The WireGuard client group handler in the device's ioos back-end can be abused to run operating system commands as root on the device, which the advisory describes as full remote code execution and total device compromise, including theft of credentials and configuration.Source: github.com
Am I affected, and how do I check?
The affected firmware is M36AX6_V260507_2.0.0 on the WN536AX6-A. You can check the firmware version in the device's admin interface or in the firmware file name. The request must reach the ioos service on port 81, either through loopback/SSRF or with a valid session token.Source: github.com
What should I do about it?
The checked sources do not name a fixed firmware version. Check WAVLINK's support pages for an updated firmware for the WN536AX6-A and install it when it becomes available.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What if there's no patch?
The checked sources give no workaround. Until a fix is released, limit who can reach the device's admin interface and port 81, and do not expose the device's management interface to untrusted networks.Source: github.com