CVE-2026-37152 Hardcoded credentials in n/a
Critical 9.8
Published
Updated
Check this codebase for CVE-2026-37152 and fix it if it is affected.
What it is: CVE-2026-37152 is a critical vulnerability in n/a, published on 15 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-37152 exists.
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-37152/ (Markdown: https://insights.sbomify.com/CVE-2026-37152/index.md)
Attackers can gain root access to TOTOLINK X5000R routers using hardcoded credentials, leading to full device compromise.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-37152?
CVE-2026-37152 is a critical vulnerability in n/a, published on 15 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
TOTOLINK X5000R V9.1.0cu.2415_B20250515 was discovered to contain a hardcoded password for root access.
Weakness: CWE-798
Which versions are affected by CVE-2026-37152?
How do I fix CVE-2026-37152?
No fix has been published for CVE-2026-37152 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-37152 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-37152 exists.
Sources
Also known as GHSA-4m6v-x9gf-2c93.