CVE-2026-120198 WAVLINK WL-WN530BE1-A protocol.csp con_check_read_finish command injection
Critical 10.0
Published
Updated
Check this codebase for CVE-2026-120198 and fix it if it is affected.
What it is: CVE-2026-120198 is a critical vulnerability in WAVLINK WL-WN530BE1-A, published on 1 Nov 2026.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120198 exists.
Affected product: WAVLINK WL-WN530BE1-A. 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-120198/ (Markdown: https://insights.sbomify.com/CVE-2026-120198/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-120198?
CVE-2026-120198 is a critical vulnerability in WAVLINK WL-WN530BE1-A, published on 1 Nov 2026.
Official description
A vulnerability has been found in WAVLINK WL-WN530BE1-A V251117. Affected is the function con_check_read_finish of the file /protocol.csp. Such manipulation of the argument group_name/IP-FROM leads to command injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure.
Which versions are affected by CVE-2026-120198?
How do I fix CVE-2026-120198?
No fix has been published for CVE-2026-120198 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-120198 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120198 exists.
Sources
Also known as GHSA-cq8m-m2p5-jxxm.