/

CVE-2026-89010

Severity:

CRITICAL RISK

(9.8)

OS Command Injection (CWE-78) in WAVLINK WN535M1/M3

CVE-2026-89010

Deferred

Vulnerability type

Category:

OS Command Injection

CWE:

CWE-78

Impact:

Unauthenticated Root-Level Remote Code Execution

Severity:

CRITICAL RISK

(9.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A critical unauthenticated OS command injection vulnerability in WAVLINK WN535M1 and WN535M3 routers allows remote attackers to execute arbitrary operating-system commands as root. The issue becomes risky when the sync_server daemon processes attacker-controlled filenames on TCP port 13136 without neutralizing shell metacharacters.

Affected context

The vulnerability affects WAVLINK WN535M1 and WN535M3 routers running firmware versions before the referenced remediation level, when the sync_server daemon is reachable on TCP port 13136. Risk is highest when this service is exposed to untrusted networks because it processes filename input as part of a shell command with device-level privileges.

Exploit preconditions

  • Attack surface: The sync_server daemon listening on TCP port 13136
  • Required access: Network connectivity to the daemon; authentication is not required
  • Trigger point: Processing of a crafted filename by the synchronization service
  • Why exploitation is possible: Attacker-controlled input is interpolated into a shell command and executed through a system command interface without adequate sanitization

Why this happens

The underlying bug is a command construction pattern in which external filename data is inserted into a shell command string using formatted output and then passed to a shell-executing API. Shell metacharacters in the input can alter command interpretation, mapping to CWE-78: Improper Neutralization of Special Elements used in an OS Command. Executing this command with root privileges amplifies the impact of the injection.

Potential impact

  • An unauthenticated attacker may execute arbitrary commands as root
  • The router could be fully compromised
  • Network traffic may be intercepted, redirected, or disrupted
  • Device credentials and configuration data could be exposed
  • The compromised router could be used for persistence, lateral movement, or attacks against connected systems

General mitigation guidance

Mitigation generally focuses on removing shell interpretation from filename-processing workflows and reducing the privileges available to network-facing services.

Common defensive patterns include:

  • Using direct system-call or library APIs that accept structured arguments instead of shell command strings
  • Applying strict allowlist validation to filenames and rejecting unexpected characters or path components
  • Treating all network-provided filenames as untrusted data
  • Running synchronization services with the minimum privileges needed for their function
  • Restricting access to TCP port 13136 through network segmentation and firewall policy
  • Disabling or isolating unnecessary network-facing services
  • Applying vendor-provided security maintenance through controlled device-management processes

How teams detect issues like this

Organizations can look for this vulnerability class through:

  • Static analysis rules identifying user-controlled data passed to sprintf(), system(), shell wrappers, or equivalent command interpreters
  • Code review checks for string concatenation or formatting involving filenames and shell commands
  • Security policies prohibiting shell execution for network-derived input
  • Network monitoring for unexpected access to TCP port 13136
  • Device telemetry and logging for unusual process execution, configuration changes, or outbound connections from routers
  • Automated code-scanning and firmware review tools that flag command-injection patterns

Sources

SourceLink
docs.wavlink.xyzdocs.wavlink.xyz/Security_Advisory/WAVLINK-SA-2026-091302/
github.comgithub.com/camdsmith/wavlink-sync_server-rce/blob/main/README.md
vulncheck.comvulncheck.com/advisories/wavlink-wn535m1-wn535m3-unauthenticated-os-command-injection-via-sync-server

Frequently asked

questions

Yes. A remote attacker may exploit the issue over the network when TCP port 13136 is reachable, and the vulnerable service does not require authentication.

The attacker generally needs network connectivity to the sync_server daemon. Local access or valid router credentials are not inherently required.

The safest pattern is to avoid shell interpretation entirely, validate filenames using strict allowlists, and execute the required operation with minimal service privileges.

Treat network-supplied filenames as untrusted, prohibit unsafe command construction, restrict exposure of administrative services, and use static analysis and review policies to detect shell-execution paths.

Find out what's already
exploitable in your codebase.