# CVE-2026-10190: Tenda W12 Web Management httpd cgiSysWebTimeoutSet denial of service

> Remote attackers can cause a denial of service in Tenda W12 routers by manipulating the web_over_time argument in the web management interface.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 May 2026
- **Updated:** 1 Jun 2026
- **Also known as:** GHSA-hgcw-qw4m-rwrh

## What is CVE-2026-10190?

CVE-2026-10190 is a high-severity denial of service vulnerability in Tenda W12, published on 31 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was found in Tenda W12 3.0.0.7(4763). This issue affects the function cgiSysWebTimeoutSet of the file /bin/httpd of the component Web Management Interface. The manipulation of the argument web_over_time results in denial of service. It is possible to launch the attack remotely. The exploit has been made public and could be used.

Weakness: CWE-404 (Improper Resource Shutdown or Release)

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


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

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

## Is CVE-2026-10190 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-10190 is a high-severity denial of service vulnerability in Tenda W12, published on 31 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-10190 exists.

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

## Sources

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

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