PatchSiren cyber security CVE debrief
CVE-2026-120229 WAVLINK CVE debrief
A vulnerability was found in WAVLINK WN553X1-B 260403_2.0.0, affecting the function sub_416B50 of the file /bin/ioos, which is vulnerable to OS command injection via the file_id argument. This issue can be exploited remotely. The exploit has been publicly disclosed. WAVLINK WN553X1-B devices with publicly accessible interfaces are at risk. Defenders should assess their exposure and prioritize verification and potential remediation. The vulnerability has a CVSS score of 8.5, indicating high severity.
- Vendor
- WAVLINK
- Product
- WN553X1-B
- CVSS
- HIGH 8.5
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-11-01
- Original CVE updated
- 2026-11-01
- Advisory published
- 2026-11-01
- Advisory updated
- 2026-11-01
Who should care
Defenders responsible for WAVLINK WN553X1-B devices, especially those with publicly accessible interfaces, should assess their exposure and prioritize verification and potential remediation.
Why it matters
CVE-2026-120229 is a high-severity OS command injection vulnerability in WAVLINK WN553X1-B devices. Defenders should prioritize verifying exposure, especially for publicly accessible devices, and assess the feasibility of remote exploitation. The public disclosure of exploits increases the urgency for remediation.
- Remote exploitation could lead to unauthorized command execution
- Potential for lateral movement within networks
- Need for verification of device exposure and vulnerability
- Prioritization of remediation efforts based on business criticality
Technical summary
The WAVLINK WN553X1-B device, with firmware version 260403_2.0.0, contains a vulnerability in the sub_416B50 function of the /bin/ioos file, which is susceptible to OS command injection attacks via the file_id argument. This vulnerability, tracked as CVE-2026-120229, has a CVSS score of 8.5, indicating a high severity level. The vulnerability can be exploited remotely, and a public exploit has been disclosed.
Defensive priority
Defenders should prioritize verifying exposure of WAVLINK WN553X1-B devices, especially those with publicly accessible interfaces, and assess the feasibility of remote exploitation.
Recommended defensive actions
- Verify exposure of WAVLINK WN553X1-B devices, especially those with publicly accessible interfaces
- Assess the feasibility of remote exploitation
- Monitor for publicly disclosed exploits
- Consider compensating controls, such as network access restrictions
- Review vendor patch guidance for WN553X1-B devices
- Perform asset inventory of WN553X1-B devices in managed environments
- Track exceptions and retest remediated assets
Evidence notes
The CVE record and NVD entry provide details on the vulnerability, including its CVSS score of 8.5 and the CWE-77 and CWE-78 weaknesses. However, the vendor's response and specific affected versions are not detailed in the provided sources.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-120229 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-120229
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-120229 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-120229
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/senxitoyshuyi-ui/IOT-CVE/blob/main/vulns/WAVLINK_WN553X1-B_check_pwd_command_injection.md
-
Source reference
Unverified legacy reference
URL: https://vuldb.com/cve/CVE-2026-120229
-
Source reference
Unverified legacy reference
URL: https://vuldb.com/submit/919153
-
Source reference
Unverified legacy reference
URL: https://vuldb.com/vuln/429588
-
Source reference
Unverified legacy reference
URL: https://vuldb.com/vuln/429588/cti
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.