# CVE-2026-51617: Information disclosure in n/a

> Unauthenticated attackers can obtain sensitive router configuration and network details via a crafted POST request to the status configuration endpoint.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Aug 2026
- **Updated:** 1 Sep 2026
- **Also known as:** GHSA-4j9g-3r37-7pj6

## What is CVE-2026-51617?

CVE-2026-51617 is a high-severity vulnerability in n/a, published on 28 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Incorrect access control in the getSysStatusCfg function of TOTOLINK T6 4.1.5cu.748_B20211015 allows unauthenticated attackers to obtain sensitive information such as operation mode, firmware version, serial number, WAN/LAN IP addresses, WiFi SSID, encryption keys, and connected client statistics via sending a crafted POST request to /cgi-bin/cstecgi.cgi.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2026-51617 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-51617 is a high-severity vulnerability in n/a, published on 28 Aug 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-51617 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-51617/ (Markdown: https://insights.sbomify.com/CVE-2026-51617/index.md)
```

## Sources

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

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