CVE-2026-120196 WAVLINK WN579X3-D wapi.cgi port_forward os command injection
Critical 9.4
Published
Updated
Check this codebase for CVE-2026-120196 and fix it if it is affected.
What it is: CVE-2026-120196 is a critical vulnerability in WAVLINK WN579X3-D, published on 1 Nov 2026.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120196 exists.
Affected product: WAVLINK WN579X3-D. 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-120196/ (Markdown: https://insights.sbomify.com/CVE-2026-120196/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-120196?
CVE-2026-120196 is a critical vulnerability in WAVLINK WN579X3-D, published on 1 Nov 2026.
Official description
A vulnerability was detected in WAVLINK WN579X3-D V250402. This affects the function port_forward of the file /cgi-bin/wapi.cgi. The manipulation of the argument Name results in os command injection. The attack may be performed from remote. The exploit is now public and may be used. The vendor was contacted early about this disclosure.
Which versions are affected by CVE-2026-120196?
How do I fix CVE-2026-120196?
No fix has been published for CVE-2026-120196 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-120196 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120196 exists.
Sources
Also known as GHSA-fmc2-w58f-qqpv.