# CVE-2026-10187: Totolink N300RH Web Management wireless.so setWiFiBasicConfig stack-based overflow

> Remote attackers can trigger a stack-based buffer overflow in the Totolink N300RH web interface to execute arbitrary code.

- **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:** 31 May 2026
- **Updated:** 2 Jun 2026
- **Also known as:** GHSA-f783-rqc9-65mx

## What is CVE-2026-10187?

CVE-2026-10187 is a critical memory corruption vulnerability in Totolink N300RH, published on 31 May 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 Totolink N300RH 6.1c.1353_B20190305. Affected by this issue is the function setWiFiBasicConfig of the file wireless.so of the component Web Management Interface. Performing a manipulation of the argument KeyStr results in stack-based buffer overflow. The attack is possible to be carried out remotely. The exploit is now public and may be used.

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-10187?


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

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

## Is CVE-2026-10187 being exploited?

There is no known exploitation of CVE-2026-10187 in the wild and no public exploit code.

Public exploit code:

- A vulnerability was detected in Totolink N300RH 6.1c.1353_B20190305. (github_poc): https://github.com/passwa11/CVE-2026-10187

## Fix prompt for AI coding agents

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

What it is: CVE-2026-10187 is a critical memory corruption vulnerability in Totolink N300RH, published on 31 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-10187 in the wild and no public exploit code.

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

## Sources

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

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