# CVE-2026-36798: Memory corruption in n/a

> Attackers can cause a Denial of Service on Tenda G0 routers by sending crafted HTTP requests that trigger stack overflows in the debug configuration function.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Jun 2026
- **Updated:** 10 Jun 2026
- **Also known as:** GHSA-4m54-7749-qjj8

## What is CVE-2026-36798?

CVE-2026-36798 is a medium-severity memory corruption vulnerability in n/a, published on 9 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Shenzhen Tenda Technology Co., Ltd Tenda G0 v15.11.0.5 was discovered to contain multiple stack overflows in the formSetDebugCfgr function via the enable, level, and module parameters. These vulnerabilities allow attackers to cause a Denial of Service (DoS) via a crafted HTTP request.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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


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

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

## Is CVE-2026-36798 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-36798 is a medium-severity memory corruption vulnerability in n/a, published on 9 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-36798 in the wild and no public exploit code.

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

## Sources

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

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