# CVE-2026-116508: TOTOLINK A950RG Device-Information CGI infostat.cgi sub_402340 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:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-5vj6-9qxv-4h93

## What is CVE-2026-116508?

CVE-2026-116508 is a critical vulnerability in TOTOLINK A950RG, published on 26 Oct 2026. 

### Official description

A security flaw has been discovered in TOTOLINK A950RG 4.1.2cu.5268_B20221104. Affected by this issue is the function sub_402340 of the file infostat.cgi of the component Device-Information CGI. Performing a manipulation of the argument CONTENT_LENGTH results in stack-based buffer overflow. Remote exploitation of the attack is possible. The exploit has been released to the public and may be used for attacks.

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


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

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

## Is CVE-2026-116508 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116508 is a critical vulnerability in TOTOLINK A950RG, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116508 in the wild and no public exploit code.

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

## Sources

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

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