# CVE-2026-114575: TOTOLINK A950RG product.so UploadCustomModule command injection


- **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:** 22 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-8wp9-f64g-53hq

## What is CVE-2026-114575?

CVE-2026-114575 is a critical vulnerability in TOTOLINK A950RG, published on 22 Oct 2026. 

### Official description

A flaw has been found in TOTOLINK A950RG 4.1.2cu.5268_B20221104. Affected by this issue is the function UploadCustomModule of the file lib/cste_modules/product.so. Executing a manipulation of the argument FileMd5 can lead to command injection. The attack can be launched remotely. The exploit has been published and may be used.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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


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

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

## Is CVE-2026-114575 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-114575 is a critical vulnerability in TOTOLINK A950RG, published on 22 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-114575 exists.

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

## Sources

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

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