# CVE-2026-120231: WAVLINK WN553X1-B OpenVPN CLI ioos sub_416568 os command injection


- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 1 Nov 2026
- **Updated:** 2 Nov 2026
- **Also known as:** GHSA-5268-gj55-x6jx

## What is CVE-2026-120231?

CVE-2026-120231 is a critical vulnerability in WAVLINK WN553X1-B, published on 1 Nov 2026. 

### Official description

A vulnerability was determined in WAVLINK WN553X1-B V260403_2.0.0. The affected element is the function sub_416568 of the file /bin/ioos of the component OpenVPN CLI Handler. This manipulation of the argument file_id causes os command injection. It is possible to initiate the attack remotely. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2026-120231?


## How do I fix CVE-2026-120231?

No fix has been published for CVE-2026-120231 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-120231 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120231 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-120231 and fix it if it is affected.

What it is: CVE-2026-120231 is a critical vulnerability in WAVLINK WN553X1-B, published on 1 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120231 exists.

Affected product: WAVLINK WN553X1-B. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-120231/ (Markdown: https://insights.sbomify.com/CVE-2026-120231/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-120231
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-120231
- OSV: https://osv.dev/vulnerability/CVE-2026-120231

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-120231/
Summaries are generated and may contain mistakes; the official description above is the record.
