# CVE-2026-2017: IP-COM W30AP POST Request wx3auth R7WebsSecurityHandler stack-based overflow

> Remote attackers can trigger a stack-based buffer overflow in the IP-COM W30AP access point via a crafted POST request, potentially leading to code execution.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Feb 2026
- **Updated:** 23 Feb 2026
- **Also known as:** GHSA-qxp9-w6x3-f25v

## What is CVE-2026-2017?

CVE-2026-2017 is a critical memory corruption vulnerability in IP-COM W30AP, published on 6 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was detected in IP-COM W30AP up to 1.0.0.11(1340). Affected by this issue is the function R7WebsSecurityHandler of the file /goform/wx3auth of the component POST Request Handler. The manipulation of the argument data results in stack-based buffer overflow. The attack may be performed from remote. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

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

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

It affects 1 product.


Products: Ip-Com W30ap Firmware.

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

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

## Is CVE-2026-2017 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-2017 is a critical memory corruption vulnerability in IP-COM W30AP, published on 6 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-2017 exists.

Affected product: IP-COM W30AP. 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-2017/ (Markdown: https://insights.sbomify.com/CVE-2026-2017/index.md)
```

## Sources

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

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