CVE-2026-116507 TOTOLINK A950RG global.so getLanguageCfg information disclosure
Medium 6.9
Published
Updated
Check this codebase for CVE-2026-116507 and fix it if it is affected.
What it is: CVE-2026-116507 is a medium-severity vulnerability in TOTOLINK A950RG, published on 26 Oct 2026.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-116507 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-116507/ (Markdown: https://insights.sbomify.com/CVE-2026-116507/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-116507?
CVE-2026-116507 is a medium-severity vulnerability in TOTOLINK A950RG, published on 26 Oct 2026.
Official description
A vulnerability was identified in TOTOLINK A950RG 4.1.2cu.5268_B20221104. Affected by this vulnerability is the function getLanguageCfg of the file global.so. Such manipulation of the argument token leads to information disclosure. The attack may be launched remotely. The exploit is publicly available and might be used.
Which versions are affected by CVE-2026-116507?
How do I fix CVE-2026-116507?
No fix has been published for CVE-2026-116507 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-116507 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-116507 exists.
Sources
Also known as GHSA-xgfw-m8mq-fq8p.