# CVE-2026-120281: WAVLINK WN536AX6-A OpenVPN protocol.csp strcpy stack-based overflow


- **Severity:** Critical 10.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/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:** 2 Nov 2026
- **Updated:** 6 Nov 2026
- **Also known as:** GHSA-rg96-pw5p-hj64

## What is CVE-2026-120281?

CVE-2026-120281 is a critical vulnerability in WAVLINK WN536AX6-A, published on 2 Nov 2026. 

### Official description

A vulnerability was found in WAVLINK WN536AX6-A V260507. This affects the function strcpy of the file /protocol.csp of the component OpenVPN Handler. The manipulation of the argument openvpn_ip results in stack-based buffer overflow. The attack may be launched remotely. The exploit has been made public and could be used. The vendor was contacted early about this disclosure.

Weakness: CWE-121 (Stack-based Buffer Overflow), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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


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

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

## Is CVE-2026-120281 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120281 is a critical vulnerability in WAVLINK WN536AX6-A, published on 2 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120281 exists.

Affected product: WAVLINK WN536AX6-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-120281/ (Markdown: https://insights.sbomify.com/CVE-2026-120281/index.md)
```

## Sources

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

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