Skip to main content
← Vulnerabilities

WAVLINK WN536AX6-A VPN Client List ioos sub_41a7c0 missing authentication

Affects WAVLINK WN536AX6-A running firmware M36AX6_V260507_2.0.0-WO-d173724. CVSS scores it 6.9 (medium), and no vendor rating or fix is listed.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Published
Last modified
Published
Not listed in CISA KEV
19/100 · provisional
Unclear
None on Exploit-DB, Metasploit or GitHub

Summary

The WAVLINK WN536AX6-A router firmware, specifically its VPN Client List handler component (/bin/ioos), is affected. A remote attacker could exploit missing authentication checks to access or manipulate VPN client list functions without proper credentials.

Read the original description

A vulnerability was detected in WAVLINK WN536AX6-A V260507_2.0.0. Impacted is the function sub_416d48/sub_41a7c0 of the file /bin/ioos of the component VPN Client List Handler. Performing a manipulation of the argument opt results in missing authentication. The attack can be initiated remotely. The exploit is now public and may be used. The vendor was contacted early about this disclosure.

What to do

  • Workaround: The available facts list no workaround or interim fix. Check the vendor advisory for any mitigation steps while an update is pending.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • WAVLINK WN536AX6-A

    V260507_2.0.0

Evidence 5

  1. Advisory
  2. Advisory
  3. Advisory
  4. Advisory
  5. Exploit

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

FAQ

Questions about CVE-2026-120278

What does this mean?

An unauthenticated attacker on the same network can list the router's VPN client configuration. This includes OpenVPN and WireGuard peer and server addresses, group or file identifiers, and config paths.Source: github.com

Am I affected, and how do I check?

The listed affected firmware is M36AX6_V260507_2.0.0-WO-d173724 on the WAVLINK WN536AX6-A. The available facts give no version ranges, so compare the firmware build on the device with that string.Source: github.com

What should I do about it?

No fixed version is named in the available facts, so check the WAVLINK vendor channels for an update before relying on any particular release.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 available facts list no workaround or interim fix. Check the vendor advisory for any mitigation steps while an update is pending.Source: github.com