CVE-2026-123958 TOTOLINK CA300-PoE cstecgi.cgi setLanConfig buffer overflow
Critical 9.4
Published
Updated
Check this codebase for CVE-2026-123958 and fix it if it is affected.
What it is: CVE-2026-123958 is a critical vulnerability in TOTOLINK CA300-PoE, published on 7 Nov 2026.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-123958 exists.
Affected product: TOTOLINK CA300-PoE. 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-123958/ (Markdown: https://insights.sbomify.com/CVE-2026-123958/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-123958?
CVE-2026-123958 is a critical vulnerability in TOTOLINK CA300-PoE, published on 7 Nov 2026.
Official description
A vulnerability was identified in TOTOLINK CA300-PoE 6.2c.884. The affected element is the function setLanConfig of the file /cgi-bin/cstecgi.cgi. Such manipulation of the argument lanDns/lanSecDns/langType leads to buffer overflow. It is possible to launch the attack remotely. The exploit is publicly available and might be used.
Which versions are affected by CVE-2026-123958?
How do I fix CVE-2026-123958?
No fix has been published for CVE-2026-123958 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-123958 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-123958 exists.
Sources
Also known as GHSA-c4px-fcrj-5258.